You can see specific examples here: http://youtu.be/N7-fZJaJUv8 * Creating a new folder gives no notification but creating a file does * Creating a new folder with the same name errors out with no options, but creating a new file gives options * The dialog for dealing with a name-conflict for files is absurd, telling me the file I have not created already exists and is newer than the file that does already exist, and worse yet it has pop up text telling me that if I select to "overwrite" the file I will be prompted again when I am not! * The file creation notification is often wrong, telling me I have created a file when I have not or even telling me I have created a file with a name other than what I did (implying I overwrote an existing file). It also sometimes tells me a name and sometimes does not. * Copy and Paste gives the incorrect option to "Paste URL" instead of "Paste File", then warns you will overwrite the file with itself * Dialogs allowing renaming of a file in mid-creation which are completely different depending on how you go there * The delete key does not delete a file, but right clicking gives the option to delete; shift delete deletes a file but delete does not (the meny bypasses the safeguard of the trash) * Dragging files from the trash to the desktop changes their permissions (which leads to an error saying my disk might be full!) * Dragging files from the trash back to the trash gives an absurd error offering the options of skipping and auto skipping, whatever that means, and leads to a file move conformation that makes no sense * The trash toolbar has the option to create a folder - it does not work * The menu has the same option grayed out, but does have the option to create files (which does not work yet leads to a confirmation) * The menu also has the option to rename which you are told you cannot do, you truly cannot do, but the name appears to change anyway - leading to other errors * When you empty the trash you are told you cannot undo this, but the undo option is still available in the menu; it leads to an error about not being able to rename files (why?)
This is unmanageable, one ticket per issue please. Most of those aren't even Dolphin bugs, but kio bugs.
In order to report bugs do I need to learn what "kio bugs" mean? OK, I know it is "KDE Input/Output" but I really do not know what bug fits with what program or which of these errors fits that category. To be honest I do not know how to categorize most of these. In any case, I have done what I can to report them. If there are specific questions as to what I did or how to replicate these things I am happy to help. If you want me to include logs or the like I am happy to provide those as well. Whatever I can do to help make this better, but I am not a developer and do not play one on TV. :)
On Mar 22, 2014, at 2:15 PM, Christoph Feck <christoph@maxiom.de> wrote: > https://bugs.kde.org/show_bug.cgi?id=332452 > > Christoph Feck <christoph@maxiom.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > CC| |christoph@maxiom.de > Resolution|--- |INVALID > > --- Comment #1 from Christoph Feck <christoph@maxiom.de> --- > This is unmanageable, one ticket per issue please. Most of those aren't even > Dolphin bugs, but kio bugs. > > -- > You are receiving this mail because: > You reported the bug. > I have no way of knowing what is a Dolphin bug vs. a KIO bug. If you can forward this to whomever is the responsible party that would be great. If you or they need me to collect logs, answer questions about how to replicate what I show, etc., I am happy to. I have no clue how to categorize these, though. The idea that these things are “resolved” is a bit silly - they are “ignored”, not “resolved”. usenet@gallopinginsanity.com
Geejus! I woul not know how to label those either. Is this true? Is this what KDE is really like? I am going to test this. Thanks Brock McNuggets for reporting this stuff. Hopefully the developers take this seriously and start working on these things.
You do not need to know which bug is for which KDE component. This is the reason why issued need to be reported separately. The KDE bug triaging team (which I am part of) can then re-assign these reports to the individual components and their maintainers.
Thank you for the response. OK, do not want to spam the system. Should I just report each bullet point separately and provide a link to the video showing it? On Mar 22, 2014, at 3:04 PM, Christoph Feck <christoph@maxiom.de> wrote: > https://bugs.kde.org/show_bug.cgi?id=332452 > > --- Comment #5 from Christoph Feck <christoph@maxiom.de> --- > You do not need to know which bug is for which KDE component. This is the > reason why issued need to be reported separately. The KDE bug triaging team > (which I am part of) can then re-assign these reports to the individual > components and their maintainers. > > -- > You are receiving this mail because: > You reported the bug. > usenet@gallopinginsanity.com
On Mar 22, 2014, at 2:55 PM, <juw29812@coieo.com> <juw29812@coieo.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=332452 > > juw29812@coieo.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |juw29812@coieo.com > > --- Comment #4 from juw29812@coieo.com --- > Geejus! I woul not know how to label those either. I have no clue to though am happy to provide logs and the like. I could also report each bullet point individually but would not only surely categorize them incorrectly but would likely be blamed for spamming the system. > Is this true? Is this what KDE is really like? Absolutely. To be fair I am running Mint KDE in a VM, in part so I can more easily record these things. If you look at the video there are others in the playlist which show even more errors. > I am going to test this. Feel free to email me directly with what you find so we do not spam this system here. Or post it here or not at all - whatever you feel best. > Thanks Brock McNuggets for reporting this stuff. You are welcome. > Hopefully the developers take this seriously and start working on these things. That is my primary goal for making the video and doing my best to get it known by the developers. As I said, I have some others I could also send in but if they are just going to claim these things are “resolved” I am not sure what benefit there is. Still, I think letting them know is the right thing to do, as long as it is done respectfully and not with 1000 reports which would be rightfully considered spam. > > -- > You are receiving this mail because: > You reported the bug. > usenet@gallopinginsanity.com
First of all, thanks for the bug report. (In reply to comment #2) > In order to report bugs do I need to learn what "kio bugs" mean? No, you can file any problem that you see while running Dolphin as a Dolphin bug. We will reassign reports to other products if appropriate. However, this only works if you file one report per problem. > If there are specific > questions as to what I did or how to replicate these things I am happy to > help. If you want me to include logs or the like I am happy to provide those > as well. Whatever I can do to help make this better, but I am not a > developer and do not play one on TV. :) Please include *detailed* steps to reproduce the problems in your new reports. Just one example: "Creating a new folder" can be done in lots of different ways (using the context menu action, by pressing F10, by running mkdir in a shell, etc, ...). It is not obvious to us which way you used, or if the problem appears no matter which way you use to create a new folder. You might argue that everyone can just watch your video to identify the steps to reproduce, but I hope that it's obvious that reading the steps in a detailed bug description is a lot easier for the people who read incoming bug reports in their spare time (and who are, most of the time, not the ones who wrote the buggy code). (In reply to comment #3) > The idea that these things are “resolved” is a bit silly - > they are “ignored”, not “resolved”. Nobody here wants to ignore problems. "Resolved" does not mean that the problems are fixed. It just means that the present bug report has been closed because it has been suggested that you better file individual reports about the problems you found. (In reply to comment #6) > Thank you for the response. > > OK, do not want to spam the system. Should I just report each bullet point > separately and provide a link to the video showing it? Yes, but please provide a lot more details in each report than you did in your bullet points. Try to make sure that everyone can reproduce the problem immediately without having to ask further questions. In some cases, a screenshot that highlights the problem at first sight may also be more helpful than a link to the video. (In reply to comment #7) > That is my primary goal for making the video and doing my best to get it > known by the developers. As I said, I have some others I could also send in > but if they are just going to claim these things are “resolved” I am not > sure what benefit there is. Please try to keep the discussion constructive. Nobody has claimed that any of the problems you found are resolved. Thanks. I will add some comments to your bullet points, to help you make the individual reports more useful. (In reply to comment #0) > * Creating a new folder gives no notification but creating a file does As I said above, please describe in detail how you create files/folders. Also describe exactly what notification you are referring to. Maybe a screenshot helps. > * The dialog for dealing with a name-conflict for files is absurd, telling > me the file I have not created already exists and is newer than the file > that does already exist, and worse yet it has pop up text telling me that if > I select to "overwrite" the file I will be prompted again when I am not! I'm not sure if I understand what you mean. Please provide steps to reproduce the problem. > * The file creation notification is often wrong, telling me I have created a > file when I have not or even telling me I have created a file with a name > other than what I did (implying I overwrote an existing file). It also > sometimes tells me a name and sometimes does not. Please provide steps to reproduce the problem. > * Copy and Paste gives the incorrect option to "Paste URL" instead of "Paste > File", then warns you will overwrite the file with itself Please provide steps to reproduce the problem. > * Dialogs allowing renaming of a file in mid-creation which are completely > different depending on how you go there Please provide steps to reproduce the problem. > * The delete key does not delete a file, but right clicking gives the option > to delete; shift delete deletes a file but delete does not (the meny > bypasses the safeguard of the trash) It seems to me that you describe the indended behavior here. I'm not sure what you consider buggy about that? > * The trash toolbar has the option to create a folder - it does not work What is the "trash toolbar"? > * The menu has the same option grayed out, but does have the option to > create files (which does not work yet leads to a confirmation) Which menu? Menu bar? Context menu? > * The menu also has the option to rename which you are told you cannot do, > you truly cannot do, but the name appears to change anyway - leading to > other errors I have no idea what you mean. Please provide steps to reproduce the problem.
On Mar 23, 2014, at 8:08 AM, Frank Reininghaus <frank78ac@googlemail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=332452 > > --- Comment #8 from Frank Reininghaus <frank78ac@googlemail.com> --- > First of all, thanks for the bug report. > > (In reply to comment #2) >> In order to report bugs do I need to learn what "kio bugs" mean? > > No, you can file any problem that you see while running Dolphin as a Dolphin > bug. We will reassign reports to other products if appropriate. However, this > only works if you file one report per problem. Thank you. Fair enough. >> If there are specific >> questions as to what I did or how to replicate these things I am happy to >> help. If you want me to include logs or the like I am happy to provide those >> as well. Whatever I can do to help make this better, but I am not a >> developer and do not play one on TV. :) > > Please include *detailed* steps to reproduce the problems in your new reports. > Just one example: "Creating a new folder" can be done in lots of different ways > (using the context menu action, by pressing F10, by running mkdir in a shell, > etc, ...). It is not obvious to us which way you used, or if the problem > appears no matter which way you use to create a new folder. > > You might argue that everyone can just watch your video to identify the steps > to reproduce, but I hope that it's obvious that reading the steps in a detailed > bug description is a lot easier for the people who read incoming bug reports in > their spare time (and who are, most of the time, not the ones who wrote the > buggy code). The video shows the exact steps with nothing left out. It shows every detail of what I have done. To be honest, trying to write all of these bugs out would take a lot more time than the videos. As you can see, in the 8 minutes of video or so I show a *lot* of bugs. I sincerely do not even know where to begin. Hopefully the developers and those who work with them do. > (In reply to comment #3) >> The idea that these things are “resolved” is a bit silly - >> they are “ignored”, not “resolved”. > > Nobody here wants to ignore problems. "Resolved" does not mean that the > problems are fixed. It just means that the present bug report has been closed > because it has been suggested that you better file individual reports about the > problems you found. I have now sent in individual reports, though I am admit I did so quickly and did not write out each step for each bug. In some cases the bugs are tied together… comparing how files and folders lead to different types of dialogs and such. In others, the notifications are wrong in many places - likely tied to one bug but I do not know. I do not think it is the notification system itself which has the bug but some underlying mechanism for determining when a file is created and what it is called. But how to write out all the permutations? The video shows them great. > > (In reply to comment #6) >> Thank you for the response. >> >> OK, do not want to spam the system. Should I just report each bullet point >> separately and provide a link to the video showing it? > > Yes, but please provide a lot more details in each report than you did in your > bullet points. Try to make sure that everyone can reproduce the problem > immediately without having to ask further questions. In some cases, a > screenshot that highlights the problem at first sight may also be more helpful > than a link to the video. I have provided exquisite details - more than can be easily written out. If log files and the like are needed I am happy to provide them. > > (In reply to comment #7) >> That is my primary goal for making the video and doing my best to get it >> known by the developers. As I said, I have some others I could also send in >> but if they are just going to claim these things are “resolved” I am not >> sure what benefit there is. > > Please try to keep the discussion constructive. Nobody has claimed that any of > the problems you found are resolved. Thanks. I am hoping my reports are constructive. So far I am not sure that is the case. > > I will add some comments to your bullet points, to help you make the individual > reports more useful. > > (In reply to comment #0) >> * Creating a new folder gives no notification but creating a file does > > As I said above, please describe in detail how you create files/folders. Also > describe exactly what notification you are referring to. Maybe a screenshot > helps. Creating them on the desktop by right-click > New Text File (or other type, really). Shown in the video. > >> * The dialog for dealing with a name-conflict for files is absurd, telling >> me the file I have not created already exists and is newer than the file >> that does already exist, and worse yet it has pop up text telling me that if >> I select to "overwrite" the file I will be prompted again when I am not! > > I'm not sure if I understand what you mean. Please provide steps to reproduce > the problem. This one is so extreme I really do not know how to better describe it than to say watch the video. If you have watched it you understand. Just riddled with many bugs and bad wording. Am I expected to post a separate report for each one? This email itself is getting to be a bit much. > >> * The file creation notification is often wrong, telling me I have created a >> file when I have not or even telling me I have created a file with a name >> other than what I did (implying I overwrote an existing file). It also >> sometimes tells me a name and sometimes does not. > > Please provide steps to reproduce the problem. Done. > >> * Copy and Paste gives the incorrect option to "Paste URL" instead of "Paste >> File", then warns you will overwrite the file with itself > > Please provide steps to reproduce the problem. Done. > >> * Dialogs allowing renaming of a file in mid-creation which are completely >> different depending on how you go there > > Please provide steps to reproduce the problem. Done. > >> * The delete key does not delete a file, but right clicking gives the option >> to delete; shift delete deletes a file but delete does not (the meny >> bypasses the safeguard of the trash) > > It seems to me that you describe the indended behavior here. I'm not sure what > you consider buggy about that? If I use “delete” to delete a file is it moved to the trash or deleted immediately? The answer: it depends on which “delete” you mean. Would be much better to label them menu item “Delete Immediately” or something like that. Also, having Delete directly in the menu makes it too easy to accidentally permanently delete a file - would be better to not have it show at all unless you hold down the shift key. > >> * The trash toolbar has the option to create a folder - it does not work > > What is the "trash toolbar”? The toolbar on the trash folder. As shown. Really: these questions are talking longer to ask about and explain than the length of the video. It is only about 8 minutes. >> * The menu has the same option grayed out, but does have the option to >> create files (which does not work yet leads to a confirmation) > > Which menu? Menu bar? Context menu? The menu in the trash folder which allows you to create a new folder (File > Create New> > >> * The menu also has the option to rename which you are told you cannot do, >> you truly cannot do, but the name appears to change anyway - leading to >> other errors > > I have no idea what you mean. Please provide steps to reproduce the problem. Shown in detail in the video. File > Rename allows you to rename, then you are told you could not rename, but the file shows the new name, but it does not really have that name (if you click and delete it you are told it does not exist, and leaving the trash and coming back leads to it showing its old name). Confusing - yes… especially in text. Much easier to just watch and see. Thank you for your time. I do appreciate it. > > -- > You are receiving this mail because: > You reported the bug. usenet@gallopinginsanity.com
One last commment: (In reply to comment #9) > The video shows the exact steps with nothing left out. It shows every detail > of what I have done. To be honest, trying to write all of these bugs out > would take a lot more time than the videos. As you can see, in the 8 minutes > of video or so I show a *lot* of bugs. I sincerely do not even know where to > begin. Hopefully the developers and those who work with them do. Well, I speak only for myself now. Other bug triagers might have other opinions. KDE receives lots of bug reports every day, and there are only very few people who read them. Therefore, if you want that your reports are handled quickly, it might be a good idea to make the report as easy to understand as possible. I try to squeeze in a few minutes of bug report handling a couple of times a day, but this is far from sufficient to handle all Dolphin bug reports (in particular those which do no not make it obvious at first sight what exactly the problem is, and how it can be reproduced) properly. If there are two bug reports, one of which has a few simple steps which allow to reproduce the bug immediately, and the other asks me to watch an 8-minute video to understand what the bug is about, then it should be obvious which of the two reports I will look at, and which bug I might try to fix. And this is not because I am not willing to analyze and fix the other bug, but because it's simply not possible given the amount of time that I can spend on KDE. But as I said, this is just my personal opinion. Maybe others have more resources for bug triaging and will analyze your video in detail.
On Mar 23, 2014, at 10:31 AM, Frank Reininghaus <frank78ac@googlemail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=332452 > > --- Comment #10 from Frank Reininghaus <frank78ac@googlemail.com> --- > One last commment: > > (In reply to comment #9) >> The video shows the exact steps with nothing left out. It shows every detail >> of what I have done. To be honest, trying to write all of these bugs out >> would take a lot more time than the videos. As you can see, in the 8 minutes >> of video or so I show a *lot* of bugs. I sincerely do not even know where to >> begin. Hopefully the developers and those who work with them do. > > Well, I speak only for myself now. Other bug triagers might have other > opinions. > > KDE receives lots of bug reports every day, and there are only very few people > who read them. Therefore, if you want that your reports are handled quickly, it > might be a good idea to make the report as easy to understand as possible. > > I try to squeeze in a few minutes of bug report handling a couple of times a > day, but this is far from sufficient to handle all Dolphin bug reports (in > particular those which do no not make it obvious at first sight what exactly > the problem is, and how it can be reproduced) properly. If there are two bug > reports, one of which has a few simple steps which allow to reproduce the bug > immediately, and the other asks me to watch an 8-minute video to understand > what the bug is about, then it should be obvious which of the two reports I > will look at, and which bug I might try to fix. And this is not because I am > not willing to analyze and fix the other bug, but because it's simply not > possible given the amount of time that I can spend on KDE. > > But as I said, this is just my personal opinion. Maybe others have more > resources for bug triaging and will analyze your video in detail. > > -- > You are receiving this mail because: > You reported the bug. > Thank you for your comments. I have been asking people in a Linux advocacy forum to step in and help write out these bugs - but the videos show them in context and why they are significant. Hopefully some of these advocates will step up and help take some of the load - to write these all out in detail would take hours of time… and then it is not clear anything would be done about them anyway. I sincerely hope these things are fixed and am happy to help as I can. usenet@gallopinginsanity.com
Thanks for your comments! (In reply to comment #11) > Thank you for your comments. I have been asking people in a Linux advocacy > forum to step in and help write out these bugs I see, you are probably referring to these threads: https://groups.google.com/forum/#!topic/comp.os.linux.advocacy/twhZgZ_aIdM https://groups.google.com/forum/#!topic/comp.os.linux.advocacy/ynusVrhY4Ic I see that you have invested an impressive amount of time and energy into keeping the readers of comp.os.linux.advocacy informed about the bugs you found, Brock McNuggets, or maybe I should say "Snit", or "Michael Glasser", which appears to be your real name according to this page, which can be found by Googling "snit linux advocacy": http://www.cosmicpenguin.com/snit.html > I sincerely hope these things are fixed and am happy to help as I can. Cool Michael Glasser, I'm glad to see that you are willing to help. Writing down simple instructions to reproduce the bugs in each individual report would help a lot. I see that you mentioned that doing that would this a lot of time. Time that is spent on reporting and analyzing bugs is very precious, of course, and if writing down what one of the bugs in question is about and how it can be reproduced really takes more time and more words than you have spent on the Usenet discussions, then it might be unreasonable to ask you to do it. In that case, I ask you to accept my apologies. However, I can't help thinking that bugs which are so difficult to describe will also be extremely difficult to debug and fix. Maybe someone else will find ways to provide further insights about the bugs which will help to identify or even fix the problems at some point, we'll see. We would still appreciate it greatly if you could help, Michael Glasser. I understand now that describing the bugs that you found with a few words is a very challenging and time-consuming task, and that you are a very busy person, but maybe you could try to just add a few more details to one bug report per week. This would help immensely. Thanks again for your help and your time, Michael Glasser!
On Mar 24, 2014, at 4:53 AM, Frank Reininghaus <frank78ac@googlemail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=332452 > > --- Comment #12 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for your comments! > > (In reply to comment #11) >> Thank you for your comments. I have been asking people in a Linux advocacy >> forum to step in and help write out these bugs > > I see, you are probably referring to these threads: > > https://groups.google.com/forum/#!topic/comp.os.linux.advocacy/twhZgZ_aIdM > > https://groups.google.com/forum/#!topic/comp.os.linux.advocacy/ynusVrhY4Ic > > I see that you have invested an impressive amount of time and energy into > keeping the readers of comp.os.linux.advocacy informed about the bugs you > found, Brock McNuggets, or maybe I should say "Snit", or "Michael Glasser", > which appears to be your real name according to this page, which can be found > by Googling "snit linux advocacy": > > http://www.cosmicpenguin.com/snit.html Not sure how any of that related to Linux or the bugs I have shown in KDE. Can you explain? > >> I sincerely hope these things are fixed and am happy to help as I can. > > Cool Michael Glasser, I'm glad to see that you are willing to help. Writing > down simple instructions to reproduce the bugs in each individual report would > help a lot. There are lots of bugs I show in that one video. There are many more I have found. Since you seem to have a fascination with COLA, here are some of the ones I have shown there: * Mint KDE working with folders: http://youtu.be/7C9nvniOoE0 * Mint KDE creating files: http://youtu.be/N7-fZJaJUv8 * Mint KDE help: http://youtu.be/3ikizUd3sa8 * Mint KDE general navigation: http://youtu.be/t9y14yZtQuI How long do you think it would take to write down all of the bugs I have found to your satisfaction? I think it comes down to this: I have shown you the bugs. I am happy to answer questions about the bugs. I am happy to provide logs about the bugs. I am happy to work with you. I am not interested in you using this as a medium for trolling, attacking, insulting, getting bent out of shape at seeing KDE as it is, nor any other side issue you wish to bring up. > I see that you mentioned that doing that would this a lot of time. Time that is > spent on reporting and analyzing bugs is very precious, of course, and if > writing down what one of the bugs in question is about and how it can be > reproduced really takes more time and more words than you have spent on the > Usenet discussions, then it might be unreasonable to ask you to do it. In that > case, I ask you to accept my apologies. However, I can't help thinking that > bugs which are so difficult to describe will also be extremely difficult to > debug and fix. I *show* them in exquisite detail. Are there any which you see in those videos for which you have any questions or need any further information? > Maybe someone else will find ways to provide further insights about the bugs > which will help to identify or even fix the problems at some point, we'll see. Seems few in the Linux community care to… though TomB from that forum did say he would submit some. I sincerely hope he does. If each of the claimed “advocates” submitted a few, fully written out to your satisfaction, perhaps that would work. Too many for any one person to do… or even for you and your entire team. > We would still appreciate it greatly if you could help, Michael Glasser. I > understand now that describing the bugs that you found with a few words is a > very challenging and time-consuming task, and that you are a very busy person, > but maybe you could try to just add a few more details to one bug report per > week. This would help immensely. > > Thanks again for your help and your time, Michael Glasser! You are sincerely welcome. > > -- > You are receiving this mail because: > You reported the bug. > usenet@gallopinginsanity.com
(In reply to comment #13) > On Mar 24, 2014, at 4:53 AM, Frank Reininghaus <frank78ac@googlemail.com> > wrote: > > > https://bugs.kde.org/show_bug.cgi?id=332452 > > > > --- Comment #12 from Frank Reininghaus <frank78ac@googlemail.com> --- > > Thanks for your comments! > > > > (In reply to comment #11) > >> Thank you for your comments. I have been asking people in a Linux advocacy > >> forum to step in and help write out these bugs > > > > I see, you are probably referring to these threads: > > > > https://groups.google.com/forum/#!topic/comp.os.linux.advocacy/twhZgZ_aIdM > > > > https://groups.google.com/forum/#!topic/comp.os.linux.advocacy/ynusVrhY4Ic > > > > I see that you have invested an impressive amount of time and energy into > > keeping the readers of comp.os.linux.advocacy informed about the bugs you > > found, Brock McNuggets, or maybe I should say "Snit", or "Michael Glasser", > > which appears to be your real name according to this page, which can be found > > by Googling "snit linux advocacy": > > > > http://www.cosmicpenguin.com/snit.html > > Not sure how any of that related to Linux or the bugs I have shown in KDE. > Can you explain? The usenet threads started by you are about this bug report, so it should be obvious that they are related to "the bugs you have shown in KDE". The other link is not directly related to KDE, it was just where I found your real name (or at least, what some people seem to think is your real name). > >> I sincerely hope these things are fixed and am happy to help as I can. > > > > Cool Michael Glasser, I'm glad to see that you are willing to help. Writing > > down simple instructions to reproduce the bugs in each individual report would > > help a lot. > > There are lots of bugs I show in that one video. There are many more I have > found. Since you seem to have a fascination with COLA, here are some of the > ones I have shown there: > > * Mint KDE working with folders: http://youtu.be/7C9nvniOoE0 > * Mint KDE creating files: http://youtu.be/N7-fZJaJUv8 > * Mint KDE help: http://youtu.be/3ikizUd3sa8 > * Mint KDE general navigation: http://youtu.be/t9y14yZtQuI > > How long do you think it would take to write down all of the bugs I have > found to your satisfaction? > > I think it comes down to this: I have shown you the bugs. I am happy to > answer questions about the bugs. I am happy to provide logs about the bugs. > I am happy to work with you. I am not interested in you using this as a > medium for trolling, attacking, insulting, getting bent out of shape at > seeing KDE as it is, nor any other side issue you wish to bring up. This is starting to get a bit boring. I'm not directly involved in the code which is relevant to your bug reports anyway. All I did was to suggest ways how you could make it easier for others to analyze your bugs, in the hope that this would help to get the problems fixed.
On Mar 24, 2014, at 7:09 AM, Frank Reininghaus <frank78ac@googlemail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=332452 > > Frank Reininghaus <frank78ac@googlemail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Assignee|dolphin-bugs-null@kde.org |unassigned-bugs@kde.org > > --- Comment #14 from Frank Reininghaus <frank78ac@googlemail.com> --- > (In reply to comment #13) >> On Mar 24, 2014, at 4:53 AM, Frank Reininghaus <frank78ac@googlemail.com> >> wrote: >> >>> https://bugs.kde.org/show_bug.cgi?id=332452 >>> >>> --- Comment #12 from Frank Reininghaus <frank78ac@googlemail.com> --- >>> Thanks for your comments! >>> >>> (In reply to comment #11) >>>> Thank you for your comments. I have been asking people in a Linux advocacy >>>> forum to step in and help write out these bugs >>> >>> I see, you are probably referring to these threads: >>> >>> https://groups.google.com/forum/#!topic/comp.os.linux.advocacy/twhZgZ_aIdM >>> >>> https://groups.google.com/forum/#!topic/comp.os.linux.advocacy/ynusVrhY4Ic >>> >>> I see that you have invested an impressive amount of time and energy into >>> keeping the readers of comp.os.linux.advocacy informed about the bugs you >>> found, Brock McNuggets, or maybe I should say "Snit", or "Michael Glasser", >>> which appears to be your real name according to this page, which can be found >>> by Googling "snit linux advocacy": >>> >>> http://www.cosmicpenguin.com/snit.html >> >> Not sure how any of that related to Linux or the bugs I have shown in KDE. >> Can you explain? > > The usenet threads started by you are about this bug report, so it should be > obvious that they are related to "the bugs you have shown in KDE”. Your pointing to Bilk’s site was trolling. Period. And very unprofessional. You went out of your way to make the KDE team look bad. I find that sad. If you think something I have said in those threads helps you to understand the bugs better, or leads to questions about the bugs, I am happy to help you. If you are just looking to go out of your way to troll me I am not interested. In other words, I am hoping you can move past your poor behavior and look at KDE itself. Thank you. > The other link is not directly related to KDE, it was just where I found your > real name (or at least, what some people seem to think is your real name). > >>>> I sincerely hope these things are fixed and am happy to help as I can. >>> >>> Cool Michael Glasser, I'm glad to see that you are willing to help. Writing >>> down simple instructions to reproduce the bugs in each individual report would >>> help a lot. >> >> There are lots of bugs I show in that one video. There are many more I have >> found. Since you seem to have a fascination with COLA, here are some of the >> ones I have shown there: >> >> * Mint KDE working with folders: http://youtu.be/7C9nvniOoE0 >> * Mint KDE creating files: http://youtu.be/N7-fZJaJUv8 >> * Mint KDE help: http://youtu.be/3ikizUd3sa8 >> * Mint KDE general navigation: http://youtu.be/t9y14yZtQuI >> >> How long do you think it would take to write down all of the bugs I have >> found to your satisfaction? >> >> I think it comes down to this: I have shown you the bugs. I am happy to >> answer questions about the bugs. I am happy to provide logs about the bugs. >> I am happy to work with you. I am not interested in you using this as a >> medium for trolling, attacking, insulting, getting bent out of shape at >> seeing KDE as it is, nor any other side issue you wish to bring up. > > This is starting to get a bit boring. It is overwhelming, really. There are many bugs shown there and I am not sure how to best report them all. > I'm not directly involved in the code > which is relevant to your bug reports anyway. All I did was to suggest ways how > you could make it easier for others to analyze your bugs, in the hope that this > would help to get the problems fixed. It is dishonest for you to say that is all you did, but I do appreciate any effort to help get these bugs resolved. If you have looked at those threads you will see I have not used KDE in some time - and have been shocked to find it as I did. usenet@gallopinginsanity.com
Have not used KDE much over the last few years... happy to see many of the bugs noted here have been handled. Not all, but good to see how much work has gone into improvements and fixes.