But you are not a consumer, and this is free (libre) open-source software, not something you bought. It is something you participate in. "Won't fix" doesn't necessarily mean that they aren't going to participate in or assist a solution, it means that the ultimate responsibility lies with the upstream maintainer of the package.
In your analogy, toyota would pass the info (and offer support to) the company that makes the defective part. Either that company comes through or they end up needimg to select a different part (or package) from a different company. It is a process that requires patience and good faith coordination. There are good reasons for this. Not just to avoid duplication of effort, but also to avoid unnecessarily creating confusion, fragmentation, new problems or even messing up the upstream efforts to solve the issue. So from a fellow FLOSS end user (who unfortunately has few skills to offer except bug reporting), I feel that your attitude is far more interesting to examen. Toward an open source world, Ethan On Mon, Apr 27, 2020, 17:20 Larrywbradley <1852...@bugs.launchpad.net> wrote: > (In reply to Eike Rathke from comment #24) > > Indeed, NOTOURBUG. > > Interesting attitude. If you buy a Toyota and the engine goes bad, do > you expect Toyota to say, "Sorry, not our problem, they sold us bad > engines." Your name is on the product. The product is broken. As a > consumer, I look to you to fix it, not some nefarious mix of different > manufacturers (each maker of an OS, in this case). Seems like it would > be in the best interest of the Document Foundation to at least work with > Linux, Windows and Mac developers to find an overarching solution, or > separate solutions, for this problem. You simply cannot have a viable > product by taking a flyer on these kinds of issues, essentially saying > "tough luck, it's not our problem" to the end user. Again, it's your > name on the product, and the end user could care less what environment > he is in, all he knows that YOUR product is busted. Just my two cents. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1852183 > > Title: > [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 > > Status in LibreOffice: > Won't Fix > Status in Mutter: > Unknown > Status in mutter package in Ubuntu: > Fix Committed > Status in mutter source package in Eoan: > Triaged > Status in mutter source package in Focal: > Fix Committed > > Bug description: > I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. > > In this environment, copy/cut/paste often fails. Specifically, the > paste command sometimes does not paste the text that was cut/copied > most recently. Instead, it pastes text that was cut/copied at some > prior time. > > I use LibreOffice Writer a lot, and I now see this problem very often, > i.e. many times every day. > > There is some discussion of the problem here: > > https://ask.libreoffice.org/en/question/213510/copypaste-issues- > libreoffice-calc/ > > Several posters there say that they are also using Ubuntu 19.10. > > Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: > > https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 > -Clipboard-Manager > > It seems like that could be related. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
