| Summary: | Caja can't finish loading/showing all the folders in $HOME unless you reload by pressing F5 button | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | eatdirt, lovaren, marja11, ouaurelien, smelror |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | caja | CVE: | |
| Status comment: | |||
| Attachments: | ll output for HOME | ||
|
Description
Kristoffer Grundström
2019-03-09 12:20:21 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package. CC'ing kekepower, who packaged caja for cauldron. Assignee:
bugsquad =>
pkg-bugs @Stig You can update MATE *if and only if that fixes the bug* and you don't break other packages. Needless to say this requires serious *testing* on your side. Updates are not backports, and this is not a question of taste, this is Mageia policy. cheers. CC:
(none) =>
eatdirt (In reply to Chris Denice from comment #3) > @Stig > You can update MATE *if and only if that fixes the bug* and you don't break > other packages. Needless to say this requires serious *testing* on your side. > > Updates are not backports, and this is not a question of taste, this is > Mageia policy. > > cheers. Thanks. I will test in a vm to see if the current 1.18.x version fixes this bug. Don't think it will break anything, but better safe than sorry. Cheers, Stig Kristoffer, If you want to pre-test my updates, you can use my mirror server. urpmi.addmedia "MATE test" https://mirror.kekepower.com/linux/mate/RPMS/x86_64/ and then update as normal. I haven't built it for i586. Let me know if you need it. I didn't experience your issue before the update, so I'm thinking it may have something to do with some file you may have in your home directory. The main thing here is to test if this update fixes the issue. Cheers, Stig I did what you told me and I can still reproduce the issue. If I run caja via gdb I cannot reproduce the issue. Have you tried on a brand new user? (In reply to Stig-Ørjan Smelror from comment #8) > Have you tried on a brand new user? I tested with a new user now and the issue seems to be fixed. Note that I wrote "seems". Btw, do you have a public key that I can use to keep urpmi/dnf from warning me about unsigned packages? No I don't. Sorry. This was just a pre test that I built for us. I'm not sure if it'll get pushed to Mageia 6 at all since it really didn't fix your original issue. Also, since we didn't see this behavior in a new user account, there could be something else going on that makes it hard to debug. Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team CC:
(none) =>
ouaurelien |