[dolphin] [Bug 412565] Mount options
https://bugs.kde.org/show_bug.cgi?id=412565 --- Comment #5 from Recesvintvs --- I don't know the reason, but seems that old files hadn't been written using any compression. It seems that the small compression shown by Compsize corresponds with recently writen files, which are, effectively, being well compressed, reaching ratios up to 74% size reduction in folders with text only files. Perhaps ancient versions of Dolphin didn't work very well, perhaps I had some bad installation issue. Who knows. But I have tested mounting both automatically in Dolphin and manually in Konsole, in 2 different disks, and the compression now is always done in the same amount, 37% in average. So Dolphin is working as expected and I'll have to defrag my BTRFS disk to recover some nice GBs. You can mark this bug as invalid or what you consider adequate. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412454] New: Adding a Manually added launchers for a script or application is placed in the tasks area
https://bugs.kde.org/show_bug.cgi?id=412454 Bug ID: 412454 Summary: Adding a Manually added launchers for a script or application is placed in the tasks area Product: lattedock Version: 0.9.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: colabor...@pseudoname.io Target Milestone: --- SUMMARY If I try to add an icon for a .desktop file, to have a handy launcher for a script or aplication, said icon is always placed in the central area of Latte, not in the place I want, normally beside the system tray. STEPS TO REPRODUCE 1. Drag & drop a script from Dolphin to Latte, just close to the clock and system tray area. OBSERVED RESULT Said icon is placed in the middle of Latte's panel, together with the icons of the running apps, so is easy you run unwillingly the corresponding script or program if you make a mistake and click just half centimeter more to the right/left than you really want. EXPECTED RESULT The icon should sit in the very same place that I drop it on. I'd swear than in older versions it worked that way, or maybe it's the Plasma panel which works like that. Anyway, I think that manually added icons should sit in the position the user wants because we normally have a reason to try placing them right there. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412454] Adding a Manually added launchers for a script or application is placed in the tasks area
https://bugs.kde.org/show_bug.cgi?id=412454 Recesvintvs changed: What|Removed |Added Resolution|NOT A BUG |FIXED --- Comment #2 from Recesvintvs --- (In reply to Michail Vourlakos from comment #1) > This is default behavior in order to protect the user. If you prefer to add > it as an applet you can disable that behavior through: Dock Settings -> > advanced -> Tasks -> Interaction -> (disable) "Add launchers only in the > Tasks Area" Didn't know about that. Cool! Thanks. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412558] New: Use all the computer's resources
https://bugs.kde.org/show_bug.cgi?id=412558 Bug ID: 412558 Summary: Use all the computer's resources Product: marble Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: colabor...@pseudoname.io Target Milestone: --- SUMMARY Use both GPU and all the CPU's cores to speed up the functioning of Marble, especially the vectorial maps' rendering. I'm using Marble 19.08.1 (sorry, it isnt among the options in the form), the latest stable version as of today (3/Oct/19) STEPS TO REPRODUCE 1. Search for a location 2. Move aroud the area, zoom in/out, etc. OBSERVED RESULT The map is moved slowly and you have to wait up to 7 - 8 seconds for it to be completely drawn on screen. The system monitor shows one CPU thread working at the 100% and the resting cores doing nothing. Also, the GPU fan doesn't immute, so I guess Marble isn't taking advantage of the GPU either. EXPECTED RESULT An espectacular boost due to a smart use of multi core CPU and modern graphics cards. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Latest stable (3/8/19) (available in About System) KDE Plasma Version: Latest stable (3/8/19) KDE Frameworks Version: Latest stable (3/8/19) Qt Version: Latest stable (3/8/19) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412558] Use all the computer's resources
https://bugs.kde.org/show_bug.cgi?id=412558 Recesvintvs changed: What|Removed |Added CC||colabor...@pseudoname.io -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412558] Use all the computer's resources
https://bugs.kde.org/show_bug.cgi?id=412558 --- Comment #1 from Recesvintvs --- Sorry, I meant latest versions as of 3/10/19, October, not 3 of august. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412562] New: Toponyms in the user's language
https://bugs.kde.org/show_bug.cgi?id=412562 Bug ID: 412562 Summary: Toponyms in the user's language Product: marble Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: colabor...@pseudoname.io Target Milestone: --- SUMMARY Use user's selected language for toponyms. Not English nor vernacular languages. For example: Warsaw is the english name for the capital of Poland, which vernacular name is Warszawa, and the name that appears in Marble even if your desktop is in other language. But for the rest of the world both names don't mean much: in italian is "Varsavia", in spanish "Varsovia", in russian "Варшава", in german "Warschau", and in non latinized areas most of us can't even read it because it's written like "ਵਾਰਸਾ", "وارسو" or any of the many alphabets that people use in their respective countries. If you know Android's app Osmand, it has an option for this, so it's not a problem with Openstreetmap but a Marble issue. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412562] Toponyms in the user's language
https://bugs.kde.org/show_bug.cgi?id=412562 --- Comment #1 from Recesvintvs --- Agh! These comments should be editable for soem minutes after posting... When I wrote about not having the texts in MArble in english" I obviousle was thinking of the majority of people, which language is other than english; didn't mean that north americans, etc, should not have their texts in Marble in english, of course. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412562] Toponyms in the user's language
https://bugs.kde.org/show_bug.cgi?id=412562 --- Comment #2 from Recesvintvs --- BTW, the link for the mobile versión in https://marble.kde.org/ points to the same than the desktop version. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412562] Toponyms in the user's language
https://bugs.kde.org/show_bug.cgi?id=412562 Recesvintvs changed: What|Removed |Added CC||colabor...@pseudoname.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412564] New: Group tags for efficacious searches
https://bugs.kde.org/show_bug.cgi?id=412564 Bug ID: 412564 Summary: Group tags for efficacious searches Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: colabor...@pseudoname.io CC: kfm-de...@kde.org Target Milestone: --- SUMMARY As far as I know, one can only search by tags selecting one tag. Your tags are shown in a folder tree structure so you can only select one tag and see the files that have that tag and ignoring if they have any other else. Tag filtering should be groupable so searches would be much more precise in case of files that have various tags. For example, you can have hundreds of files tagged "travel", and hundreds tagged "Cuba" and a thousand, "friends". If a document, photo, whatever, from your vacation in Cuba with your friends 5 years ago is tagged with "travel" "Cuba" and "friends" is fast and easy to find it, but if you only can include a tag in your search, you will have to dive among hundreds of files and lose a lot of time. Throw a look on Tagspaces to see what I mean in an illustrated way: https://www.tagspaces.org/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412564] Group tags for efficacious searches
https://bugs.kde.org/show_bug.cgi?id=412564 Recesvintvs changed: What|Removed |Added CC||colabor...@pseudoname.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412565] Mount options
https://bugs.kde.org/show_bug.cgi?id=412565 Recesvintvs changed: What|Removed |Added CC||colabor...@pseudoname.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412565] New: Mount options
https://bugs.kde.org/show_bug.cgi?id=412565
Bug ID: 412565
Summary: Mount options
Product: dolphin
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: colabor...@pseudoname.io
CC: kfm-de...@kde.org
Target Milestone: ---
When mounting a partition in Plasma, Dolphin mainly, I don't know which mount
options are being used.
This needs to be configurable because, for example, I have an external USB disk
I use to save tons of documents: PDF, EPUB, ODT, old Windows formats, etc.
These type of files are very well compressed, saving a lot of space ("modern
disk are so big that space is not an issue" is a shitty excuse, sorry if any
one was thinking to reply to me with that nonsense. I decide what is big enough
for my necessities, not other persons) and loading faster for the disk needs to
read less data, more useful than it sounds when you have some 400 MB PDFs on a
slow mechanic disk on an USB 2 connection. So, I formatted that disk in BTRFS
and wrote a line in my fstab to mount it using the BTRFS compression.
Well, I read somewhere that Dolphin doesn't read fstab to mount external
partitions, ergo I suppose that my BTRFS disk isn't being mounted as I really
want when I mount it through Dolphin or any other KDE app; it very probably
isn't even being mounted with compression support, right?
So, I suggest to add an avanced tab or something like that to configure mount
options for external drives. Maybe the configuration tool should not be for
Dolphin especifically but a general one for Plasma, and sit in the System
Preferencies app in the form of a KCM module.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 412568] New: Add a browsing history
https://bugs.kde.org/show_bug.cgi?id=412568 Bug ID: 412568 Summary: Add a browsing history Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: colabor...@pseudoname.io CC: kfm-de...@kde.org Target Milestone: --- Is very annoying and time wasting not being able to go back and forth in a rapid way, like other file managers and web browsers do. I didn't have to opportunity to use the "legendary" old Konqueror too much, but I did it some and I remember it had a browsing history. I don't understand how come the first developers who started Dolphin could think that removing it was a good idea, but I think that a browsing history is really an useful feature that improves the workflow of the users and saves time, instead of having to click 10 times, or more, without knowing what folder will come next, to find the folder we really want to reach. I think that if web browsers developers and other desktops and OS file manager developers haven't removed this option, must be because effectively most users do think such tools are useful. I think dolphin would improve a lot if added this simple feature. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412568] Add a browsing history
https://bugs.kde.org/show_bug.cgi?id=412568 Recesvintvs changed: What|Removed |Added CC||colabor...@pseudoname.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412568] Add a browsing history
https://bugs.kde.org/show_bug.cgi?id=412568 --- Comment #2 from Recesvintvs --- (In reply to Nate Graham from comment #1) > This was just added a few days ago and should be in Dolphin 19.12.0. :) Great! Thank you. > *** This bug has been marked as a duplicate of bug 157819 *** This feature had already been requested in begining of 2008? O_O I'm very glad to see it's going to be a reality soon, but I can't pretend I'm not also impressed by how a good feature may be kept in the freezer for almost 12 years... Ok, since the problem seems to be solved, feel free to delete this report if you want. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412565] Mount options
https://bugs.kde.org/show_bug.cgi?id=412565 --- Comment #2 from Recesvintvs --- (In reply to Nate Graham from comment #1) > Dolphin uses the Solid framework for mounting, which does read /etc/fstab > and respects any manually-adjusted mount parameters you've defined. Can you > confirm that the partition is actually not being mounted correctly, or is > this a supposition? I read somewhere, I think it was in the KDE forums, some years ago, that Dolphin had its own mount method. Perhaps was an old post. There's a lot of outdated info in KDE forums and many blogs that is obsolete and should be updated or deleted. Anyway, the case is that Compsize (https://github.com/kilobyte/compsize) reports this about one of my docs-only folders: Processed 16313 files, 12991 regular extents (12992 refs), 5967 inline. Type Perc Disk Usage Uncompressed Referenced TOTAL 99% 13G 13G 13G none 100% 13G 13G 13G lzo 49% 2.8M 5.6M 5.6M zstd34% 5.7M 16M 16M I can't really swear the partition in question is being mounted incorrectly or the problem comes from other side, but considering this is a folder which content is only text documents, seems obvious that the BTRFS compression is not being used. Some PDF in this folder contain embedded JPG images and some others are PDF with the format's builtin compression, thus BTRFS doesn't try to [re]compress them, that's true, but a great percentage of the files in this folder are EPUB, ODT, DOC, TXT, MD, HTML... A miserable 1% of compression is way too few to believe that compression is really being applied. Could you tell me if I can do any test or use any especific tool to make sure that Dolphin is the culprit, or not? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412565] Mount options
https://bugs.kde.org/show_bug.cgi?id=412565 --- Comment #4 from Recesvintvs --- I'm also afraid I don't know much about BTRFS or any other file system format. I'm just an average user and my technical knowledge is rather basic. The only way I know to verify how a partition has been mounted is simply using the command "mount", and a "mount | grep sdb1" returns: /dev/sdb1 on /run/media/myuser/mountpoint type btrfs (rw,noatime,compress=zstd:3,noacl,space_cache,commit=60,subvolid=5,subvol=/) I don't know if that's the correct way, but in case it is, I think that something is failing because even if mount says that zstd compression is being used, the numbers say the opposite. I can't believe that I get only a testimonial 1% of compression if zstd compression were really working. I'll test by mounting the external disk manually creating a folder and copying some files, and then remounting with Dolphin, repeating the process and looking if it makes any difference. In case it would, I'll report back. In case it would not, I suppose the problem must come from something else and this bug should be closed. Thank you. And if some other people read this and have any suggestion, I'm open to try them to solve the problem. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] New: Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 Bug ID: 417886 Summary: Sharing layouts dont work Product: lattedock Version: 0.9.8.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: colabor...@pseudoname.io Target Milestone: --- SUMMARY Sharing a layout to have a common dock for all activities dont work. The shared layout just becomes empty. STEPS TO REPRODUCE To be sure that it was not some malfunction in my user's configuration, I created a new user and started a fresh Plasma session. 1. Launch latte/dock 2. Restart session so the Default layout appears among the available layouts (it doesn't until I relog in)* 3. Create two new activities. 4. Create two new layouts, without anything special, I just followed the default steps and dafault values in the default Layouts->Configure dialog window, and apply the changes. 5. Switch from the Default layout to one of the new layouts -lets call it "New Layout 1"-. 6. Add a new dock in that New Layout 1. This dock will be present in all the activities. 7. Go back to the Configure layout window and tell that New Layout 1 is applied only to the activity, lets call it, "New Activity 1". Apply the changes. 8. The recently created dock is, unexpectedly, still present in all the activities, so, restart Plasma session so changes are applied. 9. Now the dock that belongs to New Layout 1 that is assigned to New Activity 1 only stands in the correct activity and not in the rest. Ok, so far so good with just minor annoyances. 10. Now switch to the Default layout if you are not there already. 11. Create a new dock, and to make it better identifiable for this test, place it at the top border of the screen, or one side or do whatever you want to not confuse it with the other dock created before. 12. Open the layouts configuration tool and activate the «Multiple» thing. Then click to mark the Default layout and then click on the button to share it and select New Activity 1 and New Activity 2 and all the new test activities you want to test the sharing feature. Apply and rstart session to apply changes. OBSERVED RESULT Once I relog in, the Default layout dock, that one that should stand at the top border, has disappeared. Instead of being present in all the activities it isnt present in any, not even the Default activity where I created it. The other layouts are ok, only the shared one is missing EXPECTED RESULT The layout should be sared with the other activities so there should be a common dock for all of them. Plasma 5.18.1, KF 5.67 on Gentoo no multilib (64 bits libraries only) As an appendix, I'd add that: a) If I try and reopen the layouts config windows, and go back to single mode, and even I especifically set that the Default layout be only applied to the Default activity, nothing changes even restarting the session. It seems that the docks I could have created for that layout were just vanished. b) So, I tried and reshare the Default layout with the other two, and added a new dock for that Default layout, that is once again sahred with the other manually created layouts. But the new dock is now only prsent in the Default layout/activity, also after restarting session, like if the share button didnt have any effect. --- * Shouldn't be a warning message to advise the users that they must restart the session to apply the changes? BTW, when using Multiple layouts and switching activities, the screen message "Switching to NameofActivity" doesnt appear anymore. Don't know if this is an intended behavior or a bug. If it's intended, I think that changing bahavior is confusing. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 417889] New: Exiting user session leaves user processes running
https://bugs.kde.org/show_bug.cgi?id=417889 Bug ID: 417889 Summary: Exiting user session leaves user processes running Product: ksmserver Version: 5.18.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: colabor...@pseudoname.io CC: plasma-b...@kde.org Target Milestone: --- If I start a session with one user, do some activity and then close the session, and then I start a new session with a different user, I can see, in htop, several instances of the process "agent" that belong to the former user, and which path is /usr/libexec/geoclue-2.0/demos/. By the name I guess it has to do with geolocation, which I have not activated for that user (not sure if for any), so I guess it must come active by default. I don't think that's a nice privacy policy even in Linux and KDE dont have backdoors. Ok, let's center and not divagate too much... The point is that I believe that one user's processes should be shut down, or killed if they refuse to terminate gracefully, once the user logs out. There have been similar reports even since 10 years ago, but I'm not sure if those are exactly like this one. In one, it seemed related to encryption or Akonadi; in the other, affected the login process; this one I report doesnt seem to produce any malfunction in anything (the processes just "sit" there wasting resources). but if you consider this is a duplicate, feel free to mark it as such, but then please reopen the one that says it's resolved/fixed. The mentioned reports are these: https://bugs.kde.org/show_bug.cgi?id=244250 https://bugs.kde.org/show_bug.cgi?id=348123 Gentoo pure 64 bits (no multilib), KF 5.67, Plasma 5.18.1. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 417889] Exiting user session leaves user processes running
https://bugs.kde.org/show_bug.cgi?id=417889 --- Comment #2 from Recesvintvs --- (In reply to David Edmundson from comment #1) > can I see output of your > > "loginctl show-session" Sorry, I'm on Gentoo, using OpenRC instead of Systemd, and I'm afraid I don't know of an equivalent command for loginctl. Can you suggest one? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 417889] Exiting user session leaves user processes running
https://bugs.kde.org/show_bug.cgi?id=417889 --- Comment #3 from Recesvintvs --- Ok, forget about the former comment. I found it on Gentoo's fora. # ck-list-sessions Session2: unix-user = '1004' realname = '(null)' seat = 'Seat1' session-type = 'unspecified' session-class = 'user' session-state = 'active' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2020-02-19T15:06:53.014753Z' login-session-id = '2' XDG_RUNTIME_DIR = '/var/run/user/1004' VTNr = '7' -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #2 from Recesvintvs --- Ok, after rereading my report I understand it's a bit confusing, also I made a copule of mistakes in my description (I was a bit dense after trying every tweak I was able to imagine 😅 ). So, lets see if I can explain myself better with the help of screenshot, as you ask: This is my layout editor once everithing is configured: -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #3 from Recesvintvs --- Created attachment 126215 --> https://bugs.kde.org/attachment.cgi?id=126215&action=edit Layout configuration -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #4 from Recesvintvs --- And this below is the default activity with the default layout and the dock I want all the activities to have: -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #5 from Recesvintvs --- Created attachment 126216 --> https://bugs.kde.org/attachment.cgi?id=126216&action=edit Shared layout -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #6 from Recesvintvs --- But is the final result: - Activity 1 (Layout 1): -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #7 from Recesvintvs --- This crappy forum app has stopped permitting me to upload the rest of the screenshots you asked. This site should move to Discourse? Ok, I'm trying to upload to other server and share the link here. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #8 from Recesvintvs --- I hope this works. It's the Activity 1 with the Layout 1: https://ibb.co/7XqnXw7";>https://i.ibb.co/7XqnXw7/A1.jpg"; alt="A1" border="0"> https://ibb.co/pLSDT32";>https://i.ibb.co/pLSDT32/A2.jpg"; alt="A2" border="0"> -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #9 from Recesvintvs --- Ok, it doesnt... Well, heres the direct link. Activity 1: https://ibb.co/7XqnXw7 And this is the Activity 2: https://ibb.co/pLSDT32 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #10 from Recesvintvs --- And finally, this is the Default activity, whit the Default layout, after sharing it and restarting the Plasma session: https://ibb.co/2ZwPsc8 As you can see, none of the layouts show the shared dock, not even the original layout where it was added initially. I can readd the dock creating it again, from scratch, but then it "survives" only in the layout active when I recreate it; it's not shared to the other layouts even it the layout configurator says so. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #11 from Recesvintvs --- I was revising the attachments and see that the first one isn't rendered as image but text. Meybe because it's a PNG file. I'm attaching it again as JPG right below. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #12 from Recesvintvs --- Created attachment 126217 --> https://bugs.kde.org/attachment.cgi?id=126217&action=edit Layout configurator -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 417941] New: Migrate to Discourse
https://bugs.kde.org/show_bug.cgi?id=417941 Bug ID: 417941 Summary: Migrate to Discourse Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: colabor...@pseudoname.io CC: she...@kde.org Target Milestone: --- The application that this site uses is old, limited and malfunctioning when one tries to upload a few screenshots; besides, one cannot edit a comment once published if has made a mistake or remembers some detailes he had forgotten when posting the bug report, or thinks it can be better reprahased, etc, etc. So I'd want to suggest that if it doesn't involve much complication, BKO abandoned this clumsy platform and use Discourse instead, or any other similar, gratis (if you make the installation and hosting by yourself) and open source, I propose Discourse because is the only that I know and I know that it's well tested and mantained and used eficaciuosly by bug report systems and forums like Manjaro's. Mozilla's Twitter's, etc. I guess BKO webmasters already know of it, but in case they dont, please throw an eye on it: https://www.discourse.org/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417942] New: Icons get cutted from 72 px dock vertical size, to up
https://bugs.kde.org/show_bug.cgi?id=417942 Bug ID: 417942 Summary: Icons get cutted from 72 px dock vertical size, to up Product: lattedock Version: 0.9.8.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: colabor...@pseudoname.io Target Milestone: --- SUMMARY If you have a 4K screen you will probably need to increase Latte Dock's size to see it confortably. But if you go up to 72 pixels or even upper, you will start to see that some icons begin to appear cutted by their sides. Please see the attached screenshot. Plasma 5.18.1, KF 5.67 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417942] Icons get cutted from 72 px dock vertical size, to up
https://bugs.kde.org/show_bug.cgi?id=417942 --- Comment #1 from Recesvintvs --- Created attachment 126218 --> https://bugs.kde.org/attachment.cgi?id=126218&action=edit Latte Dock at 80 px height -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #1 from Recesvintvs --- Created attachment 126219 --> https://bugs.kde.org/attachment.cgi?id=126219&action=edit Detail of the systray on Latte -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] New: System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 Bug ID: 417943 Summary: System tray icons too small, and no option to increase them Product: lattedock Version: 0.9.8.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: colabor...@pseudoname.io Target Milestone: --- Here I post a detailed screenshot of the system tray widget on Latte Dock. Note that I've put a ruler, stuck to the screen, so you can see that some icons are almost as small as 2,6 or 2,7 mm wide, no more. This is on a 27" 4K screen, which normally one will watch from a distance of 70 or 80 cm at least; so, even with a perfect vision, it's not very comfortable. for the Plasma native panel one could edit the file plasma-org.kde.plasma.desktop-appletsrc and increase the size. Dealing with config files is far away from an optimal solution for an average desktop user, but it worked; but it seems that this doesn't have any effect in Latte, I guess it don't use plasma-org.kde.plasma.desktop-appletsrc, nor there is any GUI to change icons' size (or at least I havent been able to find it). Maybe something is scaping to me? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 417889] Exiting user session leaves user processes running
https://bugs.kde.org/show_bug.cgi?id=417889 --- Comment #4 from Recesvintvs --- Hi. I wanted to add some info. I didn't know that Consolekit was deprecated nor that Elogind could be used in non systemd systems, but since now Im aware of it, I uninstaled CK and are now using Elogind. So, here you have the exact info that you asked (don't think it's necessary to run it as root, but just in case doing it as a "foot user" some info were missing): # loginctl show-session EnableWallMessages=no KillUserProcesses=no RebootToFirmwareSetup=no IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch DelayInhibited=sleep InhibitDelayMaxUSec=5s UserStopDelayUSec=0 HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=ignore HoldoffTimeoutUSec=30s IdleAction=ignore IdleActionUSec=30min PreparingForShutdown=no PreparingForSleep=no Docked=yes LidClosed=no OnExternalPower=yes RemoveIPC=yes RuntimeDirectorySize=1678897152 InhibitorsMax=8192 NCurrentInhibitors=3 SessionsMax=8192 NCurrentSessions=1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #14 from Recesvintvs --- Sorry for the ignorance, but what are the layout files? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #15 from Recesvintvs --- Oh, ok, the .latte files inside .config/latte. Sorry, below they are attached. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #17 from Recesvintvs --- Created attachment 126221 --> https://bugs.kde.org/attachment.cgi?id=126221&action=edit L2 layout -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #16 from Recesvintvs --- Created attachment 126220 --> https://bugs.kde.org/attachment.cgi?id=126220&action=edit L1 layout -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #18 from Recesvintvs --- Created attachment 126222 --> https://bugs.kde.org/attachment.cgi?id=126222&action=edit Default layout (sorry, I forgot to rename it to english) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417942] Icons get cutted from 72 px dock vertical size, to up
https://bugs.kde.org/show_bug.cgi?id=417942 --- Comment #3 from Recesvintvs --- Ok, that solved the visual glitch. 👍 Eujaristó! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #4 from Recesvintvs --- (In reply to Michail Vourlakos from comment #2) > If you want to edit the Latte systray you can do show at the Latte layout > files. If I understand you well you mean that I can edit the .latte files like for Plasma desktop files, right? Well, I've done like I used to do in the old file plasma-org.kde.plasma.desktop-appletsrc: I have quitted Latte, searched, in the the default layout (where lives the dock which systray I want to modify), the line beginning with "extraItems=", added "iconSize=" as a new line right after, and played with different values; then I restarted latte, but there have been no changes and the file Por omisión.layout (that's how it's named the default layout file in my spanish configured desktop) is overwritten every time I restart Latte. I supose that I'm not doing the things well... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #5 from Recesvintvs --- (In reply to Michail Vourlakos from comment #3) > But please give me some information what setting you are adding in the > configuration file, because > I can play with this with my systray tweaks at > https://github.com/psifidotos/plasma-systray-latte-tweaks I see, but besides the icon color that GUI only permits to modify icons space, no? I don't mind very much the separation between icons but the size of them. Sometimes they are hard to distinguish but not for being too close one to the others, but because a bad "legibility" of the icons themselves. I don't know if I've explained me well; as you sure have noted, english tonge is not one of my talents 😅. Please dont hesitate saying "Hey, dude, I don't understand a s*it of what you say". Ill try to do my best and try again -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 417889] Exiting user session leaves user processes running
https://bugs.kde.org/show_bug.cgi?id=417889 --- Comment #6 from Recesvintvs --- (In reply to David Edmundson from comment #5) > If it's just the stuff from the shared dbus-daemon changes > > toggling this to yes > > KillUserProcesses=no > > should fix it And where should I make that change (average user here with modest knowledge)? loginctl only shows info but doesnt allow to edit it, right? Also, the available commands for loginctl don't sound like if any was a sort of editing tool: activate kill-session lock-session show-session unlock-session attach kill-user lock-sessions show-user unlock-sessions disable-linger list-seats seat-statusterminate-seat user-status enable-linger list-sessions session-status terminate-session flush-devices list-users show-seat terminate-user -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417942] [Solved] Icons get cutted from 72 px dock vertical size, to up
https://bugs.kde.org/show_bug.cgi?id=417942 Recesvintvs changed: What|Removed |Added Summary|Icons get cutted from 72 px |[Solved] Icons get cutted |dock vertical size, to up |from 72 px dock vertical ||size, to up -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417942] [Solved] Icons get cutted from 72 px dock vertical size, to up
https://bugs.kde.org/show_bug.cgi?id=417942 Recesvintvs changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #8 from Recesvintvs --- > Send me a plasma applets rc file that you have added the iconSize record and > it works in your Plasma 5.18 system and your plasma panels. Here you have it: -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #9 from Recesvintvs --- Created attachment 126231 --> https://bugs.kde.org/attachment.cgi?id=126231&action=edit plasma-org.kde.plasma.desktop-appletsrc -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #10 from Recesvintvs --- As you can see, only adding the line "iconSize=2" at the end of the paragraph that beins with "extraItems" in the section "[Containments][26][General]" does the trick. I attach below also a before/after screenshot for ilustrative purposes. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #11 from Recesvintvs --- Created attachment 126232 --> https://bugs.kde.org/attachment.cgi?id=126232&action=edit Systray without and with "iconSize" tweak -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #14 from Recesvintvs --- (In reply to Michail Vourlakos from comment #12) > that works just fine with Latte you probably have added the iconSize value > in wrong systray... I will add that option in my plasma systray tweaks > also... I think your words might be significant: What do you mean with «works just fine with Latte» and «you probably have added the iconSize value in wrong systray»? I have not added anything anywhere but in the file plasma-org.kde.plasma.desktop-appletsrc, and only after you asked me to send you that file. I think I mentioned it in the other bug, but probably I should have done it here too. I'm using a "dummy" user account for all these tests. I try to do it always, if possible, when I report a bug. I have a user account on my system that I only use for tests in case of problems. That user gets completely wiped its home folder every time I need to report a new bug, so I reproduce the bug with a fresh and clean session. I do this to be sure that the problem, isn't due to some configuration that isnt supported anymore by KDE nor because some corrupted file or anything that could come from an user configuration. I explain this for make clear that these tests have been done without any change from my side but adding "inconSize=2" in the plasma config file to show you haow I could increase the icons size in the Plasma panel but not in Latte. But besides that, everithing is done using default values. Sorry if I had made you think otherwise So, according to you comment I understand that you are asuming that I should have added the iconSize thing somewhere besides the file plasma-org.kde.plasma.desktop-appletsrc, am I right? If yes, please, tell me where should I have added the "iconSize" modifier? Maybe there is the root of the problem. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #15 from Recesvintvs --- (In reply to Michail Vourlakos from comment #13) > please go to folder "~/.config/latte" and run command "ls -al" and send here > its output, I want to check something. "pruebas", meaning "tests", is the username, as you can guess. ls -al /home/pruebas/.config/latte total 32 drwxr-xr-x 1 pruebas pruebas 302 feb 20 21:47 . drwxr-xr-x 1 pruebas pruebas 1364 feb 20 21:47 .. -rw-r--r-- 1 pruebas pruebas 3804 feb 20 15:01 Extendido.layout.latte -rw-r--r-- 1 pruebas pruebas 1600 feb 20 21:47 L1.layout.latte -rw-r--r-- 1 pruebas pruebas 1391 feb 20 21:47 L2.layout.latte -rw-r--r-- 1 pruebas pruebas 122 feb 20 21:47 .multiple-layouts_hidden.layout.latte -rw-r--r-- 1 pruebas pruebas 3186 feb 20 15:01 Plasma.layout.latte -rw-r--r-- 1 pruebas pruebas 4978 feb 20 21:47 'Por omisión.layout.latte' -rw-r--r-- 1 pruebas pruebas 3948 feb 20 15:01 Unity.layout.latte -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 417941] Migrate to Discourse
https://bugs.kde.org/show_bug.cgi?id=417941 --- Comment #3 from Recesvintvs --- Ah, sorry. I mentioned Discourse because Manjaro uses it as bug tracker (https://forum.manjaro.org/c/manjaro-arm/bug-reports) and was the only that sounded a bit to me, not because I know anything about these matters (besides KDE's bug tracking platform sucks xD). I'm glad to read that you are planning to migrate to a better platform :), even if in a long term... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 --- Comment #17 from Recesvintvs --- > Solution B: > The iconSize=2 value must be added in your latte layout file. In your case > that is: > ~/.config/latte/Por omisión.layout.latte Ok, that was the problem. I had to add "iconSize=2" as a new line to the paragraph that begins with «[Containments][Some number here][General] extraItems=» in the .latte file that affects the dock in question. Exactly like in the file plasma-org.kde.plasma.desktop-appletsrc and problem gone. I should have digged deeper in those .latte files once I knew of them; we would have save many headaches. 😅 I've tried your GUI as well. Perfect. The perfect solution for the vast majority, I think, who dont feel confortable editing config files o that ignore absolutelly, like I did, that exist those useful .latte files inside .config/latte directory. It also has that icon color configuration tool that is very useful when one cant see well the icons because the desktop wallpaper has a similar color. Very nice tool . I hope it will be integrate in Latte so people doesnt have to installa and uptade it from Github manually. So, problem solved. Efjaristó polí, Michail. :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417943] [Solved] System tray icons too small, and no option to increase them
https://bugs.kde.org/show_bug.cgi?id=417943 Recesvintvs changed: What|Removed |Added Summary|System tray icons too |[Solved] System tray icons |small, and no option to |too small, and no option to |increase them |increase them -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #20 from Recesvintvs --- (In reply to Michail Vourlakos from comment #19) > Unfortunately in my system your three layouts configured in Multiple mode > and Sharing the Default to L1 and L2 WORK JUST FINE at all cases, both for > Latte v0.9.8.1 and master version. So something else is different in your > computer but I can not think what yet. O_O Well, I can't figure it either; besides this issue, everything seems to work well in my installation. In any case I guess I can use a Plasma panel for the common widgets and then use some Latte instancies for the specific widgets I want only for each activity in particular. Thanks for your time anyway. :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #21 from Recesvintvs --- Hi, I wanted to add something just in case it could shed some light or give you any clue. I've been playing a bit more before giving up, and I've noted something that had already seen but didnt pay much attention because I thought that it should be only a visual glitch, but no: When I share a layout and apply the change, the dock pertaining to that layout shows darker borders; well, better said, not the dock alone but the dock and any icon on it. It turns out that when I share a layout the dock is placed twice in the same layout where the dock is originally, not in the "destination" layout, the layout I want to share with; so what I get is one dock over the other, and if I move the cursor over them, the icons move and grow son one can see perfectly hoy there's a dock under the other. This only pesists during the session. When I restart the Plasma session or kill Latte (I dont like to close programs this way, but seems that "kquitapp5 latte-dock" does not work) and restart it, the duplicate dock disapears and the layout becomes empty, as I told at the beginnig of this bug report. Better, watch the following screenshot. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #22 from Recesvintvs --- Created attachment 126281 --> https://bugs.kde.org/attachment.cgi?id=126281&action=edit Duplicate layout -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #24 from Recesvintvs --- Launching Latte from Konsole throwed a lot of output and very rapidly, so I lost the track to the point where the issues apeared for the first time. Besides I think that my Konsole window hasn't retained all the output lines, so I'm attaching all the content of Konsole's window that I've been able to copy and paste. I hope it's enough, in case contrary, please tell me how can I save more content than the one that Konsole keeps in its buffer. I'm no expert of the command line at all, I'm afraid. Besides, I have not any file called "lattedock". Here is the permissions info of all the files and folders in my .config directory that contain "latte". I hope it serves: ls -la ~/.config | grep latte drwxr-xr-x 1 pruebas pruebas 274 feb 22 21:53 latte -rw--- 1 pruebas pruebas 1203 feb 22 21:53 lattedock.copy1.bak -rw--- 1 pruebas pruebas 1203 feb 22 21:53 lattedock.copy2.bak -rw-r--r-- 1 pruebas pruebas 1444 feb 22 21:53 lattedock.layout.bak -rw--- 1 pruebas pruebas 381 feb 22 21:53 lattedockrc -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #25 from Recesvintvs --- Created attachment 126310 --> https://bugs.kde.org/attachment.cgi?id=126310&action=edit Output for "latte-dock -d" I'll write a brief description: - Latte launchedfrom Konsole with "latte-dock -d" - I created one new layout, Latte crashed and restarted automatically. - Then I reopened the config dialog and asigned that layout to one activity, applied and closed (I believe). - I switched to the 2nd activity to place the dock at the left border for clear distinction. - Switched back to the default activity, entered the configuration window again and shared the default layout with the 2nd activity so the default layout, with its dock in the inferior central part of the screen ir common to both activities. Clicked the Apply button. And then the issue appeared and I saw how the dock for this activity was duplicated and in the 2nd activity only was the original panel I had put to the left, but no dock at the botton border from the default layout. I stopped doing anything related to Latte and copypasted the output. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #26 from Recesvintvs --- I forgot to say that all those steps were done starting anew, in a deleted user data "virgin" session. No traces of former intents or configurations. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 417941] Migrate to Discourse
https://bugs.kde.org/show_bug.cgi?id=417941 --- Comment #5 from Recesvintvs --- I'd seen several bug reports like this: https://discourse.mozilla.org/t/localisation-file-bug-in-thunderbird-extension/24276 and I thought Mozilla was using Discourse as a bug tracker. Maybe just some people is using incorrectly Mozilla's Discourse to report bugs and I was mislead by that. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #35 from Recesvintvs --- (In reply to Michail Vourlakos from comment #27) > Since which Latte version you are using Latte in your system? I dont remember exactly. Since 0.8.somethjing, I believe; like a year ago or something like that. I hadn't tried to share layouts until some days ago, thought. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #36 from Recesvintvs --- (In reply to Michail Vourlakos from comment #28) > and please send also your .config/lattedockrc file Right after this it is. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #37 from Recesvintvs --- Created attachment 126350 --> https://bugs.kde.org/attachment.cgi?id=126350&action=edit lattedockrc -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #38 from Recesvintvs --- (In reply to Michail Vourlakos from comment #34) > thank you very much for this report... I found two MAJOR issues based on > that report that should be fixable with Latte 0.9.9. I believe that now you > will also be just fine with your Shared Layout issues... You are very wellcome. It's the least thing I can do in return for you generous dedication and sharing this great piece of software with all of us, and asking for nothing in return. :) > I believe that now you will also be just fine with your Shared Layout > issues... I'm going to try. Thanks -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #39 from Recesvintvs --- Ok. so I've installed the version available at https://phabricator.kde.org/source/latte-dock/. I think that is the latest. Unfortunately, still doesn't work. :-/ I follow the usual steps: start with a virgin Latte configuration, launch Latte, add a new layout, assign it to a different activity, swich to multuple layouts mode, and share the default layout with both the default activity and the newly created activity. Now Latte doesnt crash in any moment of the process, the changes are applied inmediately after clicking the apply button without needing to restart Latte, and the docks aren't duplicated anymore. But I still don't have one particular dock for the new layuot/activity (called L1) and another dock common to both default and L1 activity/layout. Instead, I have an empty defult activity and the other activity whit the two docks. Please look the screenshots below. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #40 from Recesvintvs --- Created attachment 126352 --> https://bugs.kde.org/attachment.cgi?id=126352&action=edit Default activity (empty) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #41 from Recesvintvs --- Created attachment 126353 --> https://bugs.kde.org/attachment.cgi?id=126353&action=edit User created activity (correctly using both layouts) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886
--- Comment #42 from Recesvintvs ---
The docks are correctly assigned to the different layouts, as you can see in
more screenshots following this comment. The inferior dock belongs to the
default layout, so Latte's configurator only allows to move it to the layout L1
(and the other default layouts, Plasma and Unity); and the lateral dock belongs
to the layout L1, so I can only move it to the default layout ("Mi
distribución" in my localized installation).
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #43 from Recesvintvs --- Created attachment 126355 --> https://bugs.kde.org/attachment.cgi?id=126355&action=edit Common dock's "ownership" -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #44 from Recesvintvs --- Created attachment 126356 --> https://bugs.kde.org/attachment.cgi?id=126356&action=edit 2nd activity/layout's "ownership" -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886
--- Comment #45 from Recesvintvs ---
Obviously these screenshots have been taken in the Activity 2. The default one
doesn't show anything besides the desktop wallpaper.
Also, as you see, I've cutted the screenshots a bit because. Using a default
Plasma session with no changes at all but the strictly necessaries in 4K screen
the fonts and windows are too small. I think cutting the useles areas in the
screenshots will make then be sown bigger.
BTW, I've noted that the name of the default layout has changed from "Por
omisión" ("By default") to "Mi distribución" ("My distribution"). I suppose
that is only a cosmetic thing, but just in case it could indicate something, I
better comment it to you.
And to end with today's report, I don't know if this could indicate something,
but the default layout is not showed among the available layouts; only the one
that I created for this test, L1 ("Actual" in spanish doesnt mean "actual/real"
in english but "in action/use right now", and is a text that Latte creates, not
me. I hope this doesn't lead to confusion), Plasma and Unity layouts. The
default one "Mi distribución", one seems to be ignores here. I comment it in
case it were indicative of something.
Hereunder are the last screenshots for today, xD.
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #46 from Recesvintvs --- Created attachment 126357 --> https://bugs.kde.org/attachment.cgi?id=126357&action=edit Both docks showing the available layouts -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #47 from Recesvintvs --- Oh, WTF! I've been too impatient... I've just seen that the version I've installed from Phabricator isnt 0.9.9 but 0.9.85. I can't delete my latest posts, sorry. Don't take them into account since they don't apply to the 0.9.9 version you mentioned. Sorry for the mess 😅 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886
--- Comment #51 from Recesvintvs ---
> Did you build master version by yourself?
I cloned the repository on my home directory and run the install.sh script.
Previously I edited its final line "sudo make install" to delete "sudo" because
I don't use sudo, but I did nothing else; then I run it from a root session and
after the installation was finished, launched Latte as a normal user.
> Based on how you configured your layouts it works just fine based on your
> screenshots...
I know that they have been many screenshots and too much information sometimes
is worse than few information, but please note that the default layout isn't
being applied to one of the activities when it should be working on both. One
is ok but the other is empty.
> Explain me how your layouts you want to work and please give me English names
> for the layouts to explain you how to set them.
I want that the two activities, the default one and the one I made manually,
have a dock in the lower border of the screen, the same dock in common, so if I
add a widget when I am in one activity, said widget will be present too in the
dock when I switch to the other activity; not much different than what you
showed here:
https://psifidotos.blogspot.com/2019/05/latte-and-shared-layouts-dream.html.
Then I want that the second activity, the one manually created by me, has that
same dock and, also, another dock only for this second activity to place there
launchers for programs that I just want to use in said activity. That's why I
created a new layout and called it L1 and assigned it to the activity I created
on purpose, I called it A1 or Ac1, I don't remember now.
So, the default activity should use the default Latte layout with a single dock
at the middle inferior part of the screen, and the 2nd activity should use this
default layout because I've shared it, and also its own layout, called L1, with
an exclusive panel at the left side of the screen.
The 2nd activity is behaving fine, as I want, as shown in the screenshot:
https://bugsfiles.kde.org/attachment.cgi?id=126353
The problem is in the default activity: it is empty when it should have the
dock:
https://bugs.kde.org/attachment.cgi?id=126352
The configuration window shows that its layout ("Mi distribución") is shared,
but is only being applied to one activity only.
The names are set by Latte. Is using my locale configuration and almost every
text it shows is in spanish, I'm not changing anything of that. Latte itself
has "chosen" to name the default layout as "Mi distribución", not me.
In any case, you can call the default layout just "Default Layout" or "DL", or
(lets put some beauty in all this technical and prosaic stuff) "Athina", ;D,
whatever. I don't mind, I just want to have a working shared dock 😩; and the
layout I added manually, if dont like L1, call it "Custom Layout", "CL", or
"Santorini". As you prefer, I dont have any preference if you think it can
help.
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #52 from Recesvintvs --- (In reply to Michail Vourlakos from comment #50) > More precisely explain me for each layout at which Activities you want it to > be shown... Damn, I didn't see this message. Easy: - Default activity: Default layout and only it, whatever Latte wants to call it, be it "Mi distribución", "Por omisión" or "Smoking kills" - Second activity: Default layout AND specific layout made by me. I had named it L1 but I dont mind if it has to be named whatever you want. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #54 from Recesvintvs --- Ok, thanks, Michail. I'll try tomorrow. It's a bit late now. I'll report back 👍 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886
--- Comment #55 from Recesvintvs ---
Hi again. I hadnt time yesterday. Excuse for the delay.
Since I have the impression that my explanations werent as clear as I hoped, I
have made a screencast of the process. I hope it helps.
It covers since the first login on a fresh session ("rm -r .* /home/pruebas/"
run before) until the Latte's configuration process and failure, so you can
see every thing I have done and every configuration I have changed, even how I
created the 2nd activity and made them look distinct, which arent related at
all with Latte, but I want to ilustrate all.
I've reduced the resolution to 1600x900 so it dont weigh too much and besides
things don't look too tiny; also I swiched the language of Latte to US so you
don't get confused with names. Everything is recorded so you dont miss a single
change I could have done.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 418721] New: Extend "Night Colors" to color schemes
https://bugs.kde.org/show_bug.cgi?id=418721 Bug ID: 418721 Summary: Extend "Night Colors" to color schemes Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: colabor...@pseudoname.io CC: plasma-b...@kde.org Target Milestone: 1.0 In first place, I'm not sure if this request belongs here; I dont know where it belongs, to be sincere. Sorry if it doesn't. Move it where you see it fitter. Now, the Night Color feature is a nice one, but I'd like to suggest to add the posibility of not only changing the color temperature but also the color scheme. The use case may be easier to visualize for developers who live in countries where the day in the summer may begin at 6 AM and end past 22 with a very wide "dynamic range" -let me use this fotographic metaphor- from night to very bright sun hours, and a lot of gradual luminosity variances along the day- Anyway I hope that more or less anyone can imagine the advantages and "solidarize" with people who are tired to switch color schemes manually 2 or 3 times a day almost every day. D-: Brightness control isn't always the solution because it affects also contrast thus readability. So, I'd be better that desktop could switch from a light scheme to a dark one, or even better, let me chose as many color schemes changes as I wanted -actually they wont be more than 3 o 4-, so I can have, for example, a light, but not too much, scheme in the early morning; a very light, almost with pure white backgrounds, in the midday; a "light dark" in the afternoon; and a really dark one at night when I'm only using a timid led desktop lamp to illuminate the room. The ideal functioning I think that would be that Plasma would read my monitor's photometer info and according to that data I could configure which scheme use for each margin of luminosity values. But as far as I know Plasma cant communicate with the light sensors of desktop screens, correct me if I'm wrong. So while that moment comes, if ever, a daytime and geolocation based solution like is being used for the Night Colors tool would be a working hack. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 417889] Exiting user session leaves user processes running
https://bugs.kde.org/show_bug.cgi?id=417889 --- Comment #9 from Recesvintvs --- Thanks Cristoph. Yes, the one who "needsinfo" is me, hehe. As soon as I can try the solution provided by D. Edmundson I'll mark this bug as resolved if said proposed solution remedies the problem. But I have no clue of where I must set "KillUserProcesses=yes" That's why I didn't anything for more than 15 days. I'll try to do some Google search by myself if I can recall it the next days. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 418722] New: Add stacks like on MacOS
https://bugs.kde.org/show_bug.cgi?id=418722 Bug ID: 418722 Summary: Add stacks like on MacOS Product: frameworks-plasma Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: colabor...@pseudoname.io CC: plasma-b...@kde.org Target Milestone: --- Could something like this be added to Plasma, both for the desktop itself and the folder view widget? https://support.apple.com/en-us/HT209101 NB: I've selected the "components" component because I had to select one, but I dont know which component is the correct. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 418723] New: Pin items
https://bugs.kde.org/show_bug.cgi?id=418723 Bug ID: 418723 Summary: Pin items Product: klipper Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: plasma-widget Assignee: plasma-b...@kde.org Reporter: colabor...@pseudoname.io Target Milestone: --- It would be nice to be able of pinning Klipper entries so they are visible every time we invoke Klipper. Think of it pretty much like the pinned conversations in Telegram: you may have 300 chats but the 4 o 5 your participate the most, you keep always at the top of the list instead needing to search for them. For intense Klipper users, those who have configured it to save 1000 or 2000 entries, this would be a very time saving feature when we want to invoke data we may need to paste frequently, like names, signatures, bash long commands, etc. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 418724] New: Persistent widget size configuration
https://bugs.kde.org/show_bug.cgi?id=418724 Bug ID: 418724 Summary: Persistent widget size configuration Product: klipper Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: plasma-widget Assignee: plasma-b...@kde.org Reporter: colabor...@pseudoname.io Target Milestone: --- In big screens the default pop up panel for Klipper is a little ridiculous. Before the Plasma 5.18 regressions one was able to adjust its size freely, but this configuration would be reseted with every session restart. When Klipper's size will be customizable again, would be nice that it also were persistent, so if I want it to occupy the 70% of my screen's vertical space and show me 23 or 25 entries it won't be resetted next time I log in and show only 8 entries. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 418725] New: Do not close Klipper is the user don't click outside it
https://bugs.kde.org/show_bug.cgi?id=418725 Bug ID: 418725 Summary: Do not close Klipper is the user don't click outside it Product: klipper Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: plasma-widget Assignee: plasma-b...@kde.org Reporter: colabor...@pseudoname.io Target Milestone: --- My use case is that I use a lot of clipper entries, and from time to time I do some cleansing clicking on the trash bin icon at the right of each Klipper entry. If one entry is a word or a line, the bin's icon more or less fits into the line and you can click, click, click, click, etc, and after each deletion the next entry takes the former entry's position, making keeping your entries list tidy rapid and easy. But if one of the entries contains several lines or images, then the height of the band or stripe or however it's called, becomes bigger, and then your second or third click will probably not hit in the trash bin icon but a bit higher or lower. The annoyance of this is that Klipper then gets retracted and you have to move your mouse to making it emerge again. And scroll down or use the search box to recover the position where you were before. Also, the entry that you accidentally clicked a little over or under the trash bin icon, becomes selected and sits in the first top place of Klipper's list. I know that this is not a real bug, but it is a rather annoying behavior that really hinders the workflow. So I dont think I should report it as a wish but as a bug. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 418725] Do not close Klipper if the user don't click outside it
https://bugs.kde.org/show_bug.cgi?id=418725 Recesvintvs changed: What|Removed |Added Summary|Do not close Klipper is the |Do not close Klipper if the |user don't click outside it |user don't click outside it -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 418725] Do not close Klipper if the user does not click outside it
https://bugs.kde.org/show_bug.cgi?id=418725 Recesvintvs changed: What|Removed |Added Summary|Do not close Klipper if the |Do not close Klipper if the |user don't click outside it |user does not click outside ||it -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 418725] Do not close Klipper if the user does not click outside it
https://bugs.kde.org/show_bug.cgi?id=418725 --- Comment #1 from Recesvintvs --- I forgot to add my conclusion, which is very obvious actually, but to not let place to ambiguity I'll say that the correct behavior I think should be that no matter how many cliks the user performs outside Klipper buttons, as long as they are inside the Klipper's list surface Klipper must keep spread out and only retract when the user clicks outside -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 418722] Add stacks like on MacOS
https://bugs.kde.org/show_bug.cgi?id=418722 Recesvintvs changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #2 from Recesvintvs --- (In reply to David Edmundson from comment #1) > There is a folder view widget plasmoid. > > I am not taking requests for cloning UIs And this lack of respect from some devs to users' intelligence is another example of what discourages users to report bugs... No, folder view plasmoid has nothing to do with stacking files; and if I've been missing for years that there's an stacking option in folder view plasmoid, please ilustrate me and accept my most sincere apologies. Folder view does NOT stack files acording to their type, date, tags and several other criteria. Actually, stacking files would benefit default Plasma desktop and Folder view widgets. If I have a folder with a lot of downloaded files that may be PDFs, MP4s. Opuses, MP3s, MDs, etc, etc, it would be very useful to stack them according to its type, so I can easily move the PDFs to my Documents folder, for example. Also if I could stack all the files in a folder that have the tag architecture I could just select that stack and copy to a pendrive or send them to my cloud space to keep using them for my university works for my Architecture studies on my laptop. It's not about cloning any UI but about adding an nonexistent feature in Plasma. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 418722] Add stacks like on MacOS
https://bugs.kde.org/show_bug.cgi?id=418722 --- Comment #3 from Recesvintvs --- Oh, yes, of course I can use Dolphin's filter bar, do a tag search, change the order to make dolphin show the files by date/type/whatever... and surely a dozen more ways including using the console, but this is just easier, smarter and keeps the folder or desktop view cleaner. -- You are receiving this mail because: You are watching all bug changes.
