Public bug reported:

Having a number of crash issues in Unbunt mate 16.04 when loading
programs that freeze the cursor and desktop when launched/run from a
terminal. It not one individual program, as can happen anytime a program
begins to run. Just today it acurrs when loging in WIFI network.

I am confussed by the amount of debug informaton and that which is outdated.
Trying to explore the default debug programs that are pkged with Ubuntu mate. 
not sure yet which thse are or what PKGS are required, due to the information 
found on the online.
Does apport require Whoopsie to file a report. When installed and doing ls - l 
/var/crash all reports are prfixed with name Whoopsie. Then I see debug command 
can be run as apport-cli (-f) or pkg name.
Ubutu-debug (Alt + F2) only list installed programs. My issues seems to be more 
systematic than programs. Installed apport-gtk, it does not launch/run at 
command line. 

At a lose as to where to start debugging as not been able know how to
debug system.

For ezxample if I run the program with debug (tilda) using ubuntu-debug
then other programs in .xsession-errors start to load, sudk as
bluepromity and KDE, the tilda drop down opens but no debugging occurs.
the other lauched pkgs gnerate ther own errors.

So this time around I used apport-cli tilda option S

When I fist time run and selected to view report the tile name was
something like CPU core meltdown.

Now I am starting to get ownership issues from firefox. 
(/usr/lib/firefox/firefox:6538): dconf-WARNING **: Unable to open 
/var/lib/snapd/desktop/dconf/profile/user: Permission denied

I created a new admin user and deletd he old but left the deleted
admin/user home directory. As mention mistaken I ran Bleachbit and
removed the older user .cache and belive it removed the old user profile
that I was hopping to trans the bookmarks to the new account.

I changed the GID in group (admin (user name)) for the new admin/user from 
10001 to 1000 (the old Admin. Added new admin to sudo. Deleted the old Amin 
from all groups. Yet now see not so simply done. I do so in hopes of avoiding 
possible prior Networking and LXC/LXD conflicts and concerns about other 
programs such as geomagpy CDF file network viewing. 
The resaon I made the new admin/user account was do to a mate-panel problem I 
described in a prior bug report. The panle did not appear after booting.. There 
seems to be a matter of various msgs reporting the a inappropriate window 
manager is being used. The best I can determine is its some thing like.       
As stated in prior report I had to run command mate-panle ( to display) then 
marco reset( to have window funtions) I ran Pkg compiz reconfigure and compiz 
reset and think  servive compiz restart. I dont want to overstate this here as 
its another bug report but this seeemed to be the culprit that led to bigger 
issue and creating a new admin/user. The .xsession-errors carried over

Now see
ERROR: apport (pid 15949) Sat Dec  1 16:56:19 2018: called for pid 3362, signal 
11, core limit 0, dump mode 1
ERROR: apport (pid 15949) Sat Dec  1 16:56:19 2018: executable: 
/usr/bin/mate-panel (command line "mate-panel")
ERROR: apport (pid 15949) Sat Dec  1 16:56:19 2018: gdbus call error: Error 
connecting: Could not connect: Connection refused

ERROR: apport (pid 15949) Sat Dec  1 16:56:19 2018: debug: session gdbus call: 
ERROR: apport (pid 15949) Sat Dec  1 16:56:25 2018: wrote report 
/var/crash/_usr_bin_mate-panel.1001.crash


[Sun Dec  2 10:31:39 2018] magic group: gid=0 (root)
[Sun Dec  2 10:31:39 2018] logfile: /var/log/ninja.log
[Sun Dec  2 10:31:39 2018] whitelist mapped in memory at 0x7f5348386000
[Sun Dec  2 10:31:39 2018] entering daemon mode
[Sun Dec  2 10:31:39 2018] entering main loop
[Sun Dec  2 10:31:39 2018] generating initial pid array..
[Sun Dec  2 10:31:39 2018] now monitoring process activity
[Sun Dec  2 10:32:52 2018] NEW ROOT PROCESS: polkit-agent-he[6498] ppid=5695 
uid=0 gid=1000
[Sun Dec  2 10:32:52 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=5375
[Sun Dec  2 10:32:52 2018]   + UNAUTHORIZED PROCESS DETECTED: 
polkit-agent-he[6498] (parent: polkit-mate-aut[5695])
[Sun Dec  2 10:32:52 2018]   - nokill option set, no signals sent
[Sun Dec  2 10:33:05 2018] NEW ROOT PROCESS: polkit-agent-he[6529] ppid=5695 
uid=0 gid=1000
[Sun Dec  2 10:33:05 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=5375
[Sun Dec  2 10:33:05 2018]   + UNAUTHORIZED PROCESS DETECTED: 
polkit-agent-he[6529] (parent: polkit-mate-aut[5695])
[Sun Dec  2 10:33:05 2018]   - nokill option set, no signals sent
[Sun Dec  2 10:55:16 2018] NEW ROOT PROCESS: sudo[8852] ppid=7637 uid=0 gid=1000
[Sun Dec  2 10:55:16 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=7628
[Sun Dec  2 10:55:16 2018]   + UNAUTHORIZED PROCESS DETECTED: sudo[8852] 
(parent: bash[7637])
[Sun Dec  2 10:55:16 2018]   - nokill option set, no signals sent
[Sun Dec  2 14:50:52 2018] ninja version 0.1.3 initializing
[Sun Dec  2 14:50:53 2018] magic group: gid=0 (root)
[Sun Dec  2 14:50:53 2018] logfile: /var/log/ninja.log
[Sun Dec  2 14:50:53 2018] whitelist mapped in memory at 0x7f3e907d7000
[Sun Dec  2 14:50:53 2018] entering daemon mode
[Sun Dec  2 14:50:53 2018] entering main loop
[Sun Dec  2 14:50:53 2018] generating initial pid array..
[Sun Dec  2 14:50:53 2018] now monitoring process activity
[Sun Dec  2 15:15:09 2018] NEW ROOT PROCESS: sbsustart[5518] ppid=5202 uid=0 
gid=1000
[Sun Dec  2 15:15:09 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=2884
[Sun Dec  2 15:15:09 2018]   + UNAUTHORIZED PROCESS DETECTED: sbsustart[5518] 
(parent: mate-session[5202])
[Sun Dec  2 15:15:09 2018]   - nokill option set, no signals sent
[Sun Dec  2 15:15:29 2018] NEW ROOT PROCESS: package-system-[5849] ppid=5611 
uid=0 gid=0
[Sun Dec  2 15:15:29 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=5202
[Sun Dec  2 15:15:29 2018]   + UNAUTHORIZED PROCESS DETECTED: 
package-system-[5849] (parent: update-notifier[5611])
[Sun Dec  2 15:15:29 2018]   - nokill option set, no signals sent
[Sun Dec  2 15:29:12 2018] ninja version 0.1.3 initializing
[Sun Dec  2 15:29:12 2018] magic group: gid=0 (root)
[Sun Dec  2 15:29:12 2018] logfile: /var/log/ninja.log
[Sun Dec  2 15:29:12 2018] whitelist mapped in memory at 0x7fdf998d2000
[Sun Dec  2 15:29:12 2018] entering daemon mode
[Sun Dec  2 15:29:12 2018] entering main loop
[Sun Dec  2 15:29:12 2018] generating initial pid array..
[Sun Dec  2 15:29:12 2018] now monitoring process activity
[Sun Dec  2 15:29:42 2018] NEW ROOT PROCESS: sbsustart[3031] ppid=2677 uid=0 
gid=1000
[Sun Dec  2 15:29:42 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=2559
[Sun Dec  2 15:29:42 2018]   + UNAUTHORIZED PROCESS DETECTED: sbsustart[3031] 
(parent: mate-session[2677])
[Sun Dec  2 15:29:42 2018]   - nokill option set, no signals sent
[Sun Dec  2 15:30:03 2018] NEW ROOT PROCESS: package-system-[3327] ppid=3105 
uid=0 gid=0
[Sun Dec  2 15:30:03 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=2677
[Sun Dec  2 15:30:03 2018]   + UNAUTHORIZED PROCESS DETECTED: 
package-system-[3327] (parent: update-notifier[3105])
[Sun Dec  2 15:30:03 2018]   - nokill option set, no signals sent
[Sun Dec  2 15:30:33 2018] NEW ROOT PROCESS: sudo[3429] ppid=3382 uid=0 gid=1000
[Sun Dec  2 15:30:33 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=3363
[Sun Dec  2 15:30:33 2018]   + UNAUTHORIZED PROCESS DETECTED: sudo[3429] 
(parent: bash[3382])
[Sun Dec  2 15:30:33 2018]   - nokill option set, no signals sent
[Sun Dec  2 15:33:31 2018] NEW ROOT PROCESS: sudo[4685] ppid=4579 uid=0 gid=1000
[Sun Dec  2 15:33:31 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=2208
[Sun Dec  2 15:33:31 2018]   + UNAUTHORIZED PROCESS DETECTED: sudo[4685] 
(parent: bash[4579])
[Sun Dec  2 15:33:31 2018]   - nokill option set, no signals sent
[Sun Dec  2 15:40:04 2018] ninja version 0.1.3 initializing
[Sun Dec  2 15:40:04 2018] magic group: gid=0 (root)
[Sun Dec  2 15:40:04 2018] logfile: /var/log/ninja.log
[Sun Dec  2 15:40:04 2018] whitelist mapped in memory at 0x7ff1a0df8000
[Sun Dec  2 15:40:04 2018] entering daemon mode
[Sun Dec  2 15:40:04 2018] entering main loop
[Sun Dec  2 15:40:04 2018] generating initial pid array..
[Sun Dec  2 15:40:05 2018] now monitoring process activity
[Sun Dec  2 15:41:15 2018] NEW ROOT PROCESS: sbsustart[3206] ppid=2878 uid=0 
gid=1000
[Sun Dec  2 15:41:15 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=2730
[Sun Dec  2 15:41:15 2018]   + UNAUTHORIZED PROCESS DETECTED: sbsustart[3206] 
(parent: mate-session[2878])
[Sun Dec  2 15:41:15 2018]   - nokill option set, no signals sent
[Sun Dec  2 15:41:29 2018] NEW ROOT PROCESS: blueman-mechani[3493] ppid=3492 
uid=0 gid=0
[Sun Dec  2 15:41:29 2018]   - ppid uid=106(messagebus) gid=110 ppid=1272
[Sun Dec  2 15:41:29 2018]   + UNAUTHORIZED PROCESS DETECTED: 
blueman-mechani[3493] (parent: dbus-daemon[3492])
[Sun Dec  2 15:41:29 2018]   - nokill option set, no signals sent
[Sun Dec  2 15:41:36 2018] NEW ROOT PROCESS: package-system-[3508] ppid=3272 
uid=0 gid=0
[Sun Dec  2 15:41:36 2018]   - ppid uid=1001(tumuck) gid=1000 ppid=2878
[Sun Dec  2 15:41:36 2018]   + UNAUTHORIZED PROCESS DETECTED: 
package-system-[3508] (parent: update-notifier[3272])
[Sun Dec  2 15:41:36 2018]   - nokill option set, no signals sent


I relaize tha filed bug reports are to be focused on the issue at hand but 
being a noice Ubuntu Mate user and the way my bugs are interelated but also 
seperate issues they all contribute to the esktop freeze and lock up and the 
fans loudly raccing on and off, focing a hard shutdown.

Gain this is not appropriate manner to file a bug report.

Iam pressed walking two miles to library for two hours public WIFI time, couple 
times weekly. Not allowing time for collecting data points regarding bug. 
Laptop has frozen three times during this particular bug report forcing hard 
shutdowns to reboot. 
Think it best I try to trouble shoot all errors through online searches to pick 
up possible solutions. just having difficulty even for most relevant, like Not 
loaded in known VMA resource.

Better I maybe try suport questions. I thougth able to work through this 
process but to many what if and vagueness. My appologies
Thanks

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: tilda 1.3.1-1
ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Dec  2 15:45:58 2018
InstallationDate: Installed on 2018-02-23 (282 days ago)
InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
SourcePackage: tilda
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tilda (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806291

Title:
  Tilda opens terminal window and hangs (freeze)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tilda/+bug/1806291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to