That is not the only bug that has “slip through our radar”. The latest
update of Ubuntu MATE lies about the owner of files both in the command
line ls -l command and the Caja Properties window. Both claim the owner is
root. Since I am logged on a robert not root I would not be able to create,
modify, or delete any files in my system (ls always says to owner is root).
Since I can make changes then either the file system permissions code is
broken or the owner is being incorrectly reported.
I reported this problem about 4 weeks ago. It has “slip through our radar”.
No response from anybody despite the fact that this is a security problem
in the basic kernel.
Robert
On Fri, Apr 19, 2019 at 7:50 AM Po-Hsu Lin <email address hidden> wrote:
> Hello,
> my apology for this situation, we let this package (linux-signed) slip
> through our radar in the old days. The process has been improved now.
>
> I am gonna close this bug with Invalid, but please feel free to open a
> new bug with command "ubuntu-bug linux" base on what you have
> encountered recently (preferably one issue in a report, and with a
> supported version, as Ubuntu Mate 14.10 has already reaches it End-of-
> Life [1]).
>
> Or ask questions on community forums like https://askubuntu.com
> https://ubuntuforums.org/
>
> Thank you.
>
> [1] https://en.wikipedia.org/wiki/Ubuntu_MATE
>
> ** Changed in: linux-signed (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1799019
>
> Title:
> Linux crashed so severly that I have to reinstall.
>
> Status in linux-signed package in Ubuntu:
> Invalid
>
> Bug description:
> First Google Chrome and Chromium crashed closing all their windows.
> Then most, but not all, of the VisualWorks windows diappeared.
> (Unfortunately the System window closed so I could not exit properly).
> Then the list of open windows at the bottom of the screen disappeared,
> as did the menu bar at the top. With no menu to shutdown, I had to
> turn power off.
>
> When I tried to reboot I got the Ubuntu symbol and the progress dots
> underneath. After more than an hour, I got a command line to log in.
> (Not a terminal window - Ubuntu never started.)
>
> I was able to log in but could do nothing since this was a system
> without MATE or any window GUI.
>
> Every time I try to reboot, I get the save progress dots for over an
> hour and then the terminal mode login prompt.
>
> I had to boot from the distribution DVD to make this report before re-
> installing the system.
>
> Please fix your documentation on reporting system crashes. What is
> "apport" and how do I run it?
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: linux-image-4.15.0-20-generic 4.15.0-20.21
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: MATE
> Date: Sun Oct 21 02:13:33 2018
> LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=C.UTF-8
> SHELL=/bin/bash
> SourcePackage: linux-signed
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1799019/+subscriptions
>
That is not the only bug that has “slip through our radar”. The latest
update of Ubuntu MATE lies about the owner of files both in the command
line ls -l command and the Caja Properties window. Both claim the owner is
root. Since I am logged on a robert not root I would not be able to create,
modify, or delete any files in my system (ls always says to owner is root).
Since I can make changes then either the file system permissions code is
broken or the owner is being incorrectly reported.
I reported this problem about 4 weeks ago. It has “slip through our radar”.
No response from anybody despite the fact that this is a security problem
in the basic kernel.
Robert
On Fri, Apr 19, 2019 at 7:50 AM Po-Hsu Lin <email address hidden> wrote:
> Hello, /askubuntu. com /ubuntuforums. org/ /en.wikipedia. org/wiki/ Ubuntu_ MATE /bugs.launchpad .net/bugs/ 1799019 4.15.0- 20-generic 4.15.0-20.21 ature: Ubuntu 4.15.0- 20.21-generic 4.15.17 DIR=<set> /bugs.launchpad .net/ubuntu/ +source/ linux-signed/ +bug/1799019/ +subscriptions
> my apology for this situation, we let this package (linux-signed) slip
> through our radar in the old days. The process has been improved now.
>
> I am gonna close this bug with Invalid, but please feel free to open a
> new bug with command "ubuntu-bug linux" base on what you have
> encountered recently (preferably one issue in a report, and with a
> supported version, as Ubuntu Mate 14.10 has already reaches it End-of-
> Life [1]).
>
> Or ask questions on community forums like https:/
> https:/
>
> Thank you.
>
> [1] https:/
>
> ** Changed in: linux-signed (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Linux crashed so severly that I have to reinstall.
>
> Status in linux-signed package in Ubuntu:
> Invalid
>
> Bug description:
> First Google Chrome and Chromium crashed closing all their windows.
> Then most, but not all, of the VisualWorks windows diappeared.
> (Unfortunately the System window closed so I could not exit properly).
> Then the list of open windows at the bottom of the screen disappeared,
> as did the menu bar at the top. With no menu to shutdown, I had to
> turn power off.
>
> When I tried to reboot I got the Ubuntu symbol and the progress dots
> underneath. After more than an hour, I got a command line to log in.
> (Not a terminal window - Ubuntu never started.)
>
> I was able to log in but could do nothing since this was a system
> without MATE or any window GUI.
>
> Every time I try to reboot, I get the save progress dots for over an
> hour and then the terminal mode login prompt.
>
> I had to boot from the distribution DVD to make this report before re-
> installing the system.
>
> Please fix your documentation on reporting system crashes. What is
> "apport" and how do I run it?
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: linux-image-
> ProcVersionSign
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: MATE
> Date: Sun Oct 21 02:13:33 2018
> LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_
> LANG=C.UTF-8
> SHELL=/bin/bash
> SourcePackage: linux-signed
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https:/
>