[Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2019-06-28 Thread kinghat
ive had this issue for years. happens on win 10, ubuntu and kde neon. i
either have to close or minimize all chrome windows. no issue from
firefox. i posted the bug years ago to chrome but no idea where that
went.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions

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

[Bug 1757280] Re: Night Light only works on one Monitor

2019-06-09 Thread kinghat
have this issue with 18.04.2 with my 3 identical monitors.

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

Title:
  Night Light only works on one Monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1757280/+subscriptions

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

[Bug 1807286] [NEW] systemd SEGV freezing on install of virtualbox

2018-12-06 Thread kinghat
Public bug reported:

most of the information has been reported at VBox here:
https://forums.virtualbox.org/viewtopic.php?f=7=90643

when installing VBox this happens:
_
sudo ./VirtualBox-5.2.23-126798-Linux_amd64.run
[sudo] password for kinghat: 
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.
VirtualBox Version 5.2.23 r126798 (2018-11-20T16:12:47Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...

Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06
16:33:50 CST):

systemd[1]: Caught , dumped core as pid 5201.


Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 
16:33:50 CST):

systemd[1]: Freezing execution.

Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
Failed to enable unit: Connection timed out
Failed to start vboxdrv.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status vboxdrv.service' for details.
Failed to start vboxballoonctrl-service.service: Connection timed out
See system logs and 'systemctl status vboxballoonctrl-service.service' for 
details.
Failed to start vboxautostart-service.service: Connection timed out
See system logs and 'systemctl status vboxautostart-service.service' for 
details.
Failed to start vboxweb-service.service: Connection timed out
See system logs and 'systemctl status vboxweb-service.service' for details.

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.
_

VB then starts fine. after reboot none of the VMs fail to launch. ive
had weird install issues with VBox on 18.10 for many months.

Description:Ubuntu 18.10
Release:18.10

VirtualBox-5.2.23-126798-Linux_amd64.run

http://paste.debian.net/hidden/ee22b12a/

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: virtualbox (not installed)
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Dec  6 17:21:15 2018
InstallationDate: Installed on 2018-08-20 (108 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: virtualbox
UpgradeStatus: Upgraded to cosmic on 2018-10-10 (57 days ago)

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


** Tags: amd64 apport-bug cosmic

** Attachment added: "what happens after a restart when trying to use VB"
   https://bugs.launchpad.net/bugs/1807286/+attachment/5219833/+files/image.png

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

Title:
  systemd SEGV freezing on install of virtualbox

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

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

[Bug 1783129] Re: Only "main" component enabled after install

2018-08-31 Thread kinghat
i also had this happen to my sever install. this is what was in sources.list by 
default:
https://paste.ubuntu.com/p/n8w6PfkQ3R/

i used post #27: https://bugs.launchpad.net/subiquity/+bug/1783129/comments/27 
to add to my list:
https://paste.ubuntu.com/p/6KHg4QPXvF/

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

Title:
  Only "main" component enabled after install

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1783129/+subscriptions

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