Re: why are / and /home the same filesystem?
On Tue, 2022-02-08 at 16:48 +1030, Tim via users wrote: > You may actually want hard size limits on different partitions. You can still have this with subvolumes. See btrfs-quota(8). poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: why are / and /home the same filesystem?
> Am 07.02.2022 um 23:35 schrieb Patrick O'Callaghan : > > On Mon, 2022-02-07 at 11:50 -0800, Gordon Messmer wrote: >> On 2/6/22 08:17, Paolo Galtieri wrote: >>> so why are / and /home the same device? >> >> >> To the question of "why," I'd think the answer is in the discussion >> held >> in the devel@ mailing list linked below. Generally, sharing the >> storage >> pool in order to avoid running out of space in one location when >> there >> was still space left in the pool due to "bad" partitioning choices >> was >> seen as a benefit. >> >> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/IOPR2R3SCKOFUCKPLMS4MDD5664SGQFR/ > > From btrfs-quota(8): > > On the other hand, the traditional approach has only a poor solution to > restrict directories. At installation time, the harddisk can be > partitioned so that every directory (eg. /usr, /var/, ...) that needs a > limit gets its own partition. The obvious problem is that those limits > cannot be changed without a reinstallation. The btrfs subvolume feature > builds a bridge. Subvolumes correspond in many ways to partitions, as > every subvolume looks like its own filesystem. With subvolume quota, it > is now possible to restrict each subvolume like a partition, but keep > the flexibility of quota. The space for each subvolume can be expanded > or restricted on the fly. The quote describes a situation which has gone for more of a decade now. Since we have LVM (when got that part of the Linux kernel? kernel 2.6? 2004 or so? Don’t know exactly), no one would partition a hard disk along file system subdirectories. You create logical volumes instead, which can easily "changed without a reinstallation“ and space for any logical volume "can be expanded or restricted on the fly“. The latter even easier with „thin provisioning“. And of course you can do backups and restores via snapshot, it's called LVM snapshot. What a surprise. And you can do all that without that "subvolume (only) looks like its own filesystem“ but in reality are not separate and independent filesystems but merely pretend to be. BTRFS has specific advantages, without a doubt. And it is attractive for specific use cases. But it's not a silver bullet against all the tribulations of file storage, nor is it the only way to the future of IT. And by far it is not the almighty system, which fits everything as default, as many "BTRFS missionaries" would have you believe, throwing buzz words around. Peter ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: why are / and /home the same filesystem?
> Am 08.02.2022 um 12:11 schrieb Patrick O'Callaghan : > > On Tue, 2022-02-08 at 16:48 +1030, Tim via users wrote: >> You may actually want hard size limits on different partitions. > > You can still have this with subvolumes. See btrfs-quota(8). Yes, a sentence beginning with „You can have this with ….“ is probably true for every IT topic. The question is rather whether you can realistically have it in everyday practice. Workstation WG made BTRFS default with F33. Even now with F35 one year later, where is easily accessible documentation for a user who wants to install Workstation? Neither the current Installation Guide nor the Administrator's Guide give any information about how to handle BTFRS. The complete text is up to date with Fedora 25 or perhaps a bit later, only minimally updated to subsequent versions. And I see no Workstation doc listet on docs.fp.o, unlike the other Fedora editions, again, after a year. And is there an adapted installation step in Anaconda to expose an option to set a max. limit (e.g. like to handle the root login - deactivated, key only, . . .) and probably some other valuable capabilities? I can’t remember to have seen something like that. Therefore, a user is dependent on clear and informative terminology. And, well, sub-„volume“ after 32 Fedora releases has a specific meaning. (And that is one of my issues with those „missionaries“ who fight about their principles, but don’t care about their flock) Peter ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: why are / and /home the same filesystem?
On Tue, 2022-02-08 at 13:56 +0100, Peter Boy wrote: > > On the other hand, the traditional approach has only a poor > > solution to > > restrict directories. At installation time, the harddisk can be > > partitioned so that every directory (eg. /usr, /var/, ...) that > > needs a > > limit gets its own partition. The obvious problem is that those > > limits > > cannot be changed without a reinstallation. The btrfs subvolume > > feature > > builds a bridge. Subvolumes correspond in many ways to partitions, > > as > > every subvolume looks like its own filesystem. With subvolume > > quota, it > > is now possible to restrict each subvolume like a partition, but > > keep > > the flexibility of quota. The space for each subvolume can be > > expanded > > or restricted on the fly. > > The quote describes a situation which has gone for more of a decade > now. Since we have LVM (when got that part of the Linux kernel? > kernel 2.6? 2004 or so? Don’t know exactly), no one would partition a > hard disk along file system subdirectories. You create logical > volumes instead, which can easily "changed without a reinstallation“ > and space for any logical volume "can be expanded > or restricted on the fly“. The latter even easier with „thin > provisioning“. And of course you can do backups and restores via > snapshot, it's called LVM snapshot. What a surprise. I've been using BTRFS for several years now and it suits me. I could never get my head around LVM and considered it overkill for what most workstation users need, but that's a matter of personal taste. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: why are / and /home the same filesystem?
On 2/8/22 05:56, Peter Boy wrote: no one would partition a hard disk along file system subdirectories. Want to bet? Some of us, especially home users, consider LVM a pointless complication for our use case and never use it. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: why are / and /home the same filesystem?
On 2/8/22 12:44, Joe Zeff wrote: On 2/8/22 05:56, Peter Boy wrote: no one would partition a hard disk along file system subdirectories. Want to bet? Some of us, especially home users, consider LVM a pointless complication for our use case and never use it. I am still using EXT4 partitions (via manual partition setup) for F35 on my notebook for /boot, /, and /home: temp stuff deleted. $ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 69G 27G 39G 42% / /dev/sda1 974M 293M 614M 33% /boot /dev/sda5 372G 241G 113G 69% /home I've still got plenty of room on my 500GB SSD drive, so I am not concerned about space. Perhaps with F36 (or F37 if I skip), I will try and see if btrfs gains me anything for possible performance loss. Oh, in /home/common/ietf I have ALL RFCs and drafts! (over 138K drafts!), so lots of little files ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Acer Chromebook 15
On 2/7/22 01:28, Michael Hennebry wrote: Is it possible to put fedora on an Acer Chromebook 15? I've been trying to no avail. Google has shown me lots of sets of directions for booting from USB, none of which have worked. I've gotten it to the point that it claims OS checking is off, but then it goes to chrome. Grrr. Should I just throw out the chromebook? I would like to know the answer to this too. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
laptop failing with latest kernel update
hello, I performed a normal update today after some time without updating, which I believed contained a kernel update (to 5.16.5-100.fc34.x86_64 I believe). After doing the update and rebooting my pc started behaving erratically. Bootup time was longer, then it sort of got stuck, then some problems were reported by the reporting app in Gnome. My computer was simply malfunctioning all over the place, sometimes freezing completely. Decided to boot to the previous kernel (5.15.16-100.fc34.x86_64) and my pc is back to normal. The Reporting app does not let me send a report saying "The backtrace does not contain enough meaningful function frames to be reported. It is annoying but it does not necessarily indicate a problem with your computer. ABRT will not allow you to create a report in a bug tracking system but you can contact kernel maintainers via e-mail." How should I report this issue in this case? How can I change the grub boot default for now to boot to the older kernel by default? or should I try reverting (removing updated kernel) to the older kernel altogether for now? thank you, Anil F ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: laptop failing with latest kernel update
On 2/8/22 16:10, Anil Felipe Duggirala wrote: How should I report this issue in this case? One way is to god directly to Bugzilla and open the report yourself. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: why are / and /home the same filesystem?
On Tue, 2022-02-08 at 17:15 -0500, Robert Moskowitz wrote: > > > On 2/8/22 12:44, Joe Zeff wrote: > > On 2/8/22 05:56, Peter Boy wrote: > > > no one would partition a hard disk along file system > > > subdirectories. > > > > Want to bet? Some of us, especially home users, consider LVM a > > pointless complication for our use case and never use it. > > I am still using EXT4 partitions (via manual partition setup) for F35 > on > my notebook for /boot, /, and /home: > > temp stuff deleted. > > $ df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sda2 69G 27G 39G 42% / > /dev/sda1 974M 293M 614M 33% /boot > /dev/sda5 372G 241G 113G 69% /home > > > I've still got plenty of room on my 500GB SSD drive, so I am not > concerned about space. Perhaps with F36 (or F37 if I skip), I will > try > and see if btrfs gains me anything for possible performance loss. > > Oh, in /home/common/ietf I have ALL RFCs and drafts! (over 138K > drafts!), so lots of little files I used to do the same, having to manually partition because the default setup was LVM. However I prefer BTRFS because a) I don't have to guess what size of partitions to create at install time, something which is difficult to change later, and b) BTRFS includes features such as snapshots and built-in RAID without having to deal with an additional layer as with LVM. Again, it's a matter of preference. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Acer Chromebook 15
On Mon, 7 Feb 2022 at 05:29, Michael Hennebry < henne...@web.cs.ndsu.nodak.edu> wrote: > Is it possible to put fedora on an Acer Chromebook 15? > I've been trying to no avail. > Google has shown me lots of sets of directions for booting from USB, > none of which have worked. > I've gotten it to the point that it claims OS checking is off, > but then it goes to chrome. > Grrr. > Should I just throw out the chromebook? > You could donate it to a local school that provides chromebooks to students who can't do in-person learning due to COVIDS-19, measles, etc. -- George N. White III ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: why are / and /home the same filesystem?
On 2/8/22 04:56, Peter Boy wrote: The quote describes a situation which has gone for more of a decade now. Since we have LVM (when got that part of the Linux kernel? kernel 2.6? 2004 or so? Don’t know exactly), no one would partition a hard disk along file system subdirectories. You create logical volumes instead, which can easily "changed without a reinstallation“ and space for any logical volume "can be expanded or restricted on the fly“. The latter even easier with „thin provisioning“. Expanded, sure. But restricted? I don't think that's as clear for LVM. IIRC, XFS can't be shrunk at all, and ext4 can only be shrunk offline. Users should be able to create, destroy, or resize qgroups online for btrfs. I'm unclear on what you mean is easier with thin provisioning; can you clarify that? I may be naive here, as I use writable snapshots in LVM but not thin provisioning specifically: my impression was that users needed to be very careful not to allow the volume group to run out of space when using either of these, because filesystems generally don't deal well with the unexpected write failures that occur when LVM has no more extents to allocate. btrfs' free space handling can be surprising to users, and statfs() might suggest there is more space available than there is, but it's not the sort of thing that can corrupt the filesystem itself. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: why are / and /home the same filesystem?
On 2022-02-08 17:28, Gordon Messmer wrote: On 2/8/22 04:56, Peter Boy wrote: The quote describes a situation which has gone for more of a decade now. Since we have LVM (when got that part of the Linux kernel? kernel 2.6? 2004 or so? Don’t know exactly), no one would partition a hard disk along file system subdirectories. You create logical volumes instead, which can easily "changed without a reinstallation“ and space for any logical volume "can be expanded or restricted on the fly“. The latter even easier with „thin provisioning“. Expanded, sure. But restricted? I don't think that's as clear for LVM. IIRC, XFS can't be shrunk at all, and ext4 can only be shrunk offline. Users should be able to create, destroy, or resize qgroups online for btrfs. I'm unclear on what you mean is easier with thin provisioning; can you clarify that? I may be naive here, as I use writable snapshots in LVM but not thin provisioning specifically: my impression was that users needed to be very careful not to allow the volume group to run out of space when using either of these, because filesystems generally don't deal well with the unexpected write failures that occur when LVM has no more extents to allocate. btrfs' free space handling can be surprising to users, and statfs() might suggest there is more space available than there is, but it's not the sort of thing that can corrupt the filesystem itself. Exactly! I tried using thin provisioning once as a way to solve the "how much in / and how much in /home" dilemna and ended up regretting it. There is no indication of how much space is really available and when it ran out, it was messy. At least btrfs gives you an accurate number even if it might be a little confusing at first why / is getting so small when you fill up /home. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: why are / and /home the same filesystem?
On Tue, Feb 8, 2022 at 6:30 AM Peter Boy wrote: > > > > > Am 08.02.2022 um 12:11 schrieb Patrick O'Callaghan : > > > > On Tue, 2022-02-08 at 16:48 +1030, Tim via users wrote: > >> You may actually want hard size limits on different partitions. > > > > You can still have this with subvolumes. See btrfs-quota(8). > > Yes, a sentence beginning with „You can have this with ….“ is probably true > for every IT topic. > > The question is rather whether you can realistically have it in everyday > practice. Yes, (open)SUSE enables qgroups by default for years. Fedora doesn't enable them, but it's worth checking out 'man btrfs quota'. They're pretty cool, and the docs consider the dilemmas raised by snapshots, and how that affects accounting. There are some performance concerns. Desktop users don't need to worry about it, you can enable them, play, disable them. The whole quota btree is removed, no residue remains on the file system. > Workstation WG made BTRFS default with F33. Even now with F35 one year later, > where is easily accessible documentation for a user who wants to install > Workstation? Neither the current Installation Guide nor the Administrator's > Guide give any information about how to handle BTFRS. The complete text is up > to date with Fedora 25 or perhaps a bit later, only minimally updated to > subsequent versions. ? https://docs.fedoraproject.org/en-US/fedora/f35/install-guide/install/Installing_Using_Anaconda/ Those are Fedora 33 screenshots. "btrfs" appears 34 times in the document. There's an entire section on creating a btrfs layout. https://docs.fedoraproject.org/en-US/fedora/f35/install-guide/install/Installing_Using_Anaconda/#sect-installation-gui-manual-partitioning-btrfs Since I wrote up the lightweight changes for docs when btrfs became the default, I'm aware that the documentation has weaknesses. It is still LVM centric, and doesn't have hints for Btrfs nuances. In particular, with how to get the installer to reuse the "home" subvolume for the /home mountpoint. It is super easy to do, but totally non-obvious. The part most folks run into is not reusing "home" subvolume itself, which is just a matter of clicking on the previous installation "home" and assigning it to the /home mountpoint. But rather how to install to / because it won't let you reuse the "root" subvolume. This is due to the installer requiring a new clean filesystem for root. Ext4 and XFS require reformat, but Btrfs gets a partial exemption. You don't have to reformat, but you do need a new "root" subvolume, so you just create a new mountpoint with the + button, specify the mountpoint as /, and leave the capacity field blank. It'll add / mountpoint *and* create a new subvolume in the process. You can either delete the old "root" subvolume, or keep it - it's a matter of space available but as all subvolume share space it's a pretty simple calculation whether you have room for it or not. > And I see no Workstation doc listet on docs.fp.o, unlike the other Fedora > editions, again, after a year. 1. https://docs.fedoraproject.org/en-US/docs/ 2. click on engineering teams, https://docs.fedoraproject.org/en-US/engineering/ 3. click on workstation working group, https://docs.fedoraproject.org/en-US/workstation-working-group/ > And is there an adapted installation step in Anaconda to expose an option to > set a max. limit (e.g. like to handle the root login - deactivated, key only, > . . .) and probably some other valuable capabilities? I can’t remember to > have seen something like that. Workstation is a different installation experience than Server. Workstation does a Live install, using rsync, and users are setup in GNOME Initial Setup rather than in the installer. > Therefore, a user is dependent on clear and informative terminology. And, > well, sub-„volume“ after 32 Fedora releases has a specific meaning. There are only so many words. I'm reminded of the word "chunk". You see this word quite a bit in computer storage. If you specialize in one thing or another, you might get the idea that chunk is a specialized word that has a pretty specific meaning. And then you're surprised when you come across that same term in another context, it means something quite different. Chunk in mdadm is what the SNIA dictionary calls "strip" or "stripe element" [1] On Btrfs, chunk is a different thing entirely, there's no SNIA equivalent term. So it's certainly easy to get confused when terms get reused. [1] can you believe those two terms are synonyms?[2] [2] part of the problem might be the English language, really. If you've ever been confused about strip and stripe [3], it's not you, it's the words themselves. [3] These two terms are not synonyms. [4] [4] It really could make you a bit bonkers. I've really digressed now. -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Screensavers and power management
Hi, I have fedora35 installed on my desktop with a Radeon RX 570 driving three monitors, with the Cinnamon desktop, although it could be the other variation of Cinnamon that's available by default - I checked the Settings menu and can't find any way to determine which it is. I'd like all three monitors to turn off after 15 minutes of inactivity. What is the best way to do that? Simple question, but clearly not a simple answer. I'm an old-school admin from a time when we had to build our own X11 config files. I just expect things to work now, so I haven't really kept up with the desktop, even though fedora and whatever graphical display it provides by default has been my primary desktop since before Windows XP. Now, when I set the "turn off the screen when inactive for" option to 5m in the Power Management settings, I find that it takes far longer than five minutes for it to actually turn off the monitors, but then not only do they all immediately turn back on, but all of the windows on the middle monitor are shifted to the two left and right monitors. wtf? It's incredibly frustrating to have to reposition all windows back to their original location. How do I troubleshoot this? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Screensavers and power management
On Tue, 2022-02-08 at 21:43 -0500, Alex wrote: > Hi, > I have fedora35 installed on my desktop with a Radeon RX 570 driving > three monitors, with the Cinnamon desktop, although it could be the > other variation of Cinnamon that's available by default - I checked > the Settings menu and can't find any way to determine which it is. > I'd > like all three monitors to turn off after 15 minutes of inactivity. > What is the best way to do that? Simple question, but clearly not a > simple answer. > > I'm an old-school admin from a time when we had to build our own X11 > config files. I just expect things to work now, so I haven't really > kept up with the desktop, even though fedora and whatever graphical > display it provides by default has been my primary desktop since > before Windows XP. > > Now, when I set the "turn off the screen when inactive for" option to > 5m in the Power Management settings, I find that it takes far longer > than five minutes for it to actually turn off the monitors, but then > not only do they all immediately turn back on, but all of the windows > on the middle monitor are shifted to the two left and right monitors. > wtf? It's incredibly frustrating to have to reposition all windows > back to their original location. > > How do I troubleshoot this? ... Hi, I suspect there are multiple issues you are experiencing, and some of them I have for a long time, totally unrelated to the desktop environment used and distribution. I'm also experincing issues with display power management not working, I don't know which one it is really and do these match with the issues you are experiencing, but one thing is common and that is AMD graphics card (here: AMD Radeon RX 550 / 550 Series (polaris12)) and there are some known issues with them waking up displays[1][2] (at least what I found, could be unrelated, I gave up when I saw for how long they exist). I mostly use other desktop environments (Gnome and KDE) both with wayland session, and they had their own issues when they lose a display (output) things were crashing ..., but that is now improved. But still I see issues with applications move to other display after display goes to sleep and returns. (also experienced same issues with XFCE). Not helpful really, but just my rant about it since I have those issues for some time now. Regards, Branko [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1840 [2] https://gitlab.freedesktop.org/drm/amd/-/issues/662 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
