Comment 24 for bug 1650977

Revision history for this message
Glenn Sciortino (glsciortino) wrote :

I totally agree Mike! It's in my nature to question and test stuff. I think that's the reason we all use Linux here, because it gives us the freedom to do that.

As regards to your question, my monitors are listed in this way in Linux mint 'Display' settings

Left - HDMI-0
Middle - DVI-I-1 (Primary)
Right - DVI-D-0

The below two links are a screen shot of my Display settings and also the output to an
xrandr --query command.

-> https://s27.postimg.org/bwzkitrmb/Display_037.png
-> http://dpaste.com/0Q8N0WK

Regarding the reasoning you presented regarding the programmer's left to right approach, is what actually led me to testing my initial hypothesis of setting the left most monitor as the primary one, since from my programming experience that would have been the most straightforward approach.
What this shows me, is the lack of a proper testing phase in the beta stages, which in my opinion would have been vital in avoiding this issue. It's no use implementing new features, if we end up breaking others that are working. But then again, testing should be a community effort and that's why we're here.

Mike your timing problem explanation does make sense to me, but my point was that if Nemo is trying to load the icons on the primary monitor and for some reason (maybe the timing issue you mentioned) its not able to, then by that reasoning Nemo should hang and crash. However this is not the case because if Nemo does crash, simply clicking on the files icon in the taskbar should restart the Nemo process and re-instate the icons on the desktop (try killing the Nemo process and test it out). This led me to beleive that Nemo IS actually loading the Desktop icons (since it's not crashing), but the question is where? Also, the fact that sometimes the last created folder does seem to show up after a reboot, strongly suggests to me that its not skipping the desktop icon loading step when an error is encountered (by error I mean refer to your timing issue).