Walter: Yep, I do know that cups is for printing, but I didn't take the time to actually read the entire bug thread to try to figure out why this is happening . . . just quickly saw that the OP had nvidia graphics and I have had some issues in various distros relating to nvidia drivers not upgrading with other upgrades . . . causing substantial problems with the system ???? It's "non-critical" for me in that for the most part I'm not printing much of anything at home due to the expense of it . . . .
And, thanks for the full command, since I was already "in" /var/crash I just ran "sudo rm file name" didn't use the "-f" . . . cursor just returned, file wasn't showing in Trash, but then possibly the "bug report" process changed the name of the file to "xxxx.crash.upload" ??? as there are now two files ending in "upload" in "var/crash" . . . ?? Done with messing with it for today, I'll see if the "system report" window opens when I log back in tomorrow morning . . . otherwise we might be done on this thread if filing the bug report "deals with it"?? I'll try to post to Lu developer list for the next potential issue that may come up in 20.04 . . . ?? I'm sure there's a process involved with doing that that I'll look at later. On Mon, Jan 13, 2020 at 11:06 AM Walter Lapchynski <w...@ubuntu.com> wrote: > On Mon, Jan 13, 2020 at 10:52:18AM -0800, Fritz Hudnut wrote: > > seems like the OP is also using > > nvidia graphics, might relate there?? > > Given this is related to CUPS, it's doubtful it has anything to do with > graphics. In case you're not aware, CUPS is a print server. > > > Now to find "sudo" and try to trash that file . . . . > > `sudo rm -f /var/crash/_usr_sbin_cups-browsed.0.crash` > > -- > @wxl | polka.bike > C563 CAC5 8BE1 2F22 A49D > 68F6 8B57 A48B C4F2 051A >
-- Lubuntu-users mailing list Lubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
