[Bug 1804569] [NEW] Screen blackout after login and then goes back to the login screen

2018-11-21 Thread Robust Coding
Public bug reported:

When I enter my credentials into the login screen, it shows black screen
(as if processing something in the background) and then after a minute
or so it goes back to the login screen and I have to enter my
credentials again. This happen sometimes but not all the time.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-39-generic 4.15.0-39.42~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Nov 22 11:40:42 2018
InstallationDate: Installed on 2018-11-08 (13 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  Screen blackout after login and then goes back to the login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1804569/+subscriptions

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

[Bug 1198180] Re: possible leak in upstart 1.5

2013-08-05 Thread coding
I confirm this behaviour.
I use lxc for testing purposes. For each set of tests a few containers are 
created. Lifetime span is about a few seconds, and the tests are beeing run one 
after another continuously. After a few days init takes more than 2GB of 
memory. What's interesting - after stopping the tests two days ago, upstart is 
still creating/destroying non-existing virtual interfaces for the containers:
$ sudo lxc-list
RUNNING

FROZEN

STOPPED
$

$ sudo strace -ff -p 1 2>&1 | grep execve | grep if
[pid  7511] execve("/bin/sh", ["/bin/sh", "-e", "-c", "exec ifdown --allow auto 
$INTERF"..., "/bin/sh"], [/* 16 vars */] 
[pid  7511] execve("/sbin/ifdown", ["ifdown", "--allow", "auto", "vetha9Ks2v"], 
[/* 18 vars */]) = 0
[pid  7513] execve("/bin/sh", ["/bin/sh", "-e", "-c", "exec ifdown --allow auto 
$INTERF"..., "/bin/sh"], [/* 16 vars */] 
[pid  7513] execve("/sbin/ifdown", ["ifdown", "--allow", "auto", "vethDDYJtI"], 
[/* 18 vars */]) = 0
[pid  7514] execve("/bin/sh", ["/bin/sh", "-e", "-c", "exec ifdown --allow auto 
$INTERF"..., "/bin/sh"], [/* 16 vars */] 
[pid  7514] execve("/sbin/ifdown", ["ifdown", "--allow", "auto", "vetheaOt3H"], 
[/* 18 vars */]) = 0
[pid  7523] execve("/sbin/ifup", ["ifup", "--allow", "auto", "vethcqVeRj"], [/* 
17 vars */] 
[pid  7522] execve("/sbin/ifup", ["ifup", "--allow", "auto", "veth0m5onm"], [/* 
17 vars */]) = 0
[pid  7530] execve("/sbin/ifup", ["ifup", "--allow", "auto", "vethh6VSTB"], [/* 
17 vars */] 
[pid  7529] execve("/sbin/ifup", ["ifup", "--allow", "auto", "vethfgF5ty"], [/* 
17 vars */] 
[pid  7538] execve("/bin/sh", ["/bin/sh", "-e", "-c", "exec ifdown --allow auto 
$INTERF"..., "/bin/sh"], [/* 16 vars */] 
[pid  7538] execve("/sbin/ifdown", ["ifdown", "--allow", "auto", "vethcqVeRj"], 
[/* 18 vars */]) = 0
[pid  7539] execve("/bin/sh", ["/bin/sh", "-e", "-c", "exec ifdown --allow auto 
$INTERF"..., "/bin/sh"], [/* 16 vars */] 
[pid  7539] execve("/sbin/ifdown", ["ifdown", "--allow", "auto", "vethfgF5ty"], 
[/* 18 vars */] 
[pid  7537] execve("/sbin/ifup", ["ifup", "--allow", "auto", "vethkx0wFy"], [/* 
17 vars */] 
[pid  7536] execve("/sbin/ifup", ["ifup", "--allow", "auto", "veth9z1M5B"], [/* 
17 vars */]) = 0
[pid  7542] execve("/bin/sh", ["/bin/sh", "-e", "-c", "exec ifdown --allow auto 
$INTERF"..., "/bin/sh"], [/* 16 vars */] 
[pid  7542] execve("/sbin/ifdown", ["ifdown", "--allow", "auto", "vethkx0wFy"], 
[/* 18 vars */]) = 0
[pid  7548] execve("/sbin/ifup", ["ifup", "--allow", "auto", "vethgClCAf"], [/* 
17 vars */] 
[pid  7547] execve("/sbin/ifup", ["ifup", "--allow", "auto", "veth8baiZ7"], [/* 
17 vars */]) = 0
[pid  7560] execve("/bin/sh", ["/bin/sh", "-e", "-c", "exec ifdown --allow auto 
$INTERF"..., "/bin/sh"], [/* 16 vars */] 
[pid  7560] execve("/sbin/ifdown", ["ifdown", "--allow", "auto", "veth8baiZ7"], 
[/* 18 vars */]) = 0
[pid  7558] execve("/sbin/ifup", ["ifup", "--allow", "auto", "vethTcUttE"], [/* 
17 vars */] 

$ sudo pmap -x 1
1:   /sbin/init
Address   Kbytes RSS   Dirty Mode   Mapping
7fde5cf0c000   025082508 rw---[ anon ]
7fde5d30d000   012561256 rw---[ anon ]
7fde5d50e000   025082508 rw---[ anon ]
7fde5da93000   012561256 rw---[ anon ]
7fde5dd96000   0   0   0 r-x--  libnss_files-2.15.so
7fde5dda2000   0   0   0 -  libnss_files-2.15.so
7fde5dfa1000   0   0   0 r  libnss_files-2.15.so
7fde5dfa2000   0   0   0 rw---  libnss_files-2.15.so
7fde5dfa3000   0   0   0 r-x--  libnss_nis-2.15.so
7fde5dfad000   0   0   0 -  libnss_nis-2.15.so
7fde5e1ad000   0   0   0 r  libnss_nis-2.15.so
7fde5e1ae000   0   0   0 rw---  libnss_nis-2.15.so
7fde5e1af000   0   0   0 r-x--  libnsl-2.15.so
7fde5e1c6000   0   0   0 -  libnsl-2.15.so
7fde5e3c5000   0   0   0 r  libnsl-2.15.so
7fde5e3c6000   0   0   0 rw---  libnsl-2.15.so
7fde5e3c7000   0   0   0 rw---[ anon ]
7fde5e3c9000   0   0   0 r-x--  libnss_compat-2.15.so
7fde5e3d1000   0   0   0 -  libnss_compat-2.15.so
7fde5e5d   0   0   0 r  libnss_compat-2.15.so
7fde5e5d1000   0   0   0 rw---  libnss_compat-2.15.so
7fde5e5d2000   0 404   0 r-x--  libc-2.15.so
7fde5e787000   0   0   0 -  libc-2.15.so
7fde5e986000   0  16  16 r  libc-2.15.so
7fde5e98a000   0   8   8 rw---  libc-2.15.so
7fde5e98c000   0  16  16 rw---[ anon ]
7fde5e991000   0   4   0 r-x--  librt-2.15.so
7fde5e998000   0   0   0 -  librt-2.15.so
7fde5eb97000   0   4   4 r  librt-2.15.so
7fde5eb98000   0   0   0 rw---  librt-2.15.so
7fde5eb99000   0  24   0 r-x-- 

[Bug 428318] Re: unable to mount an ext2 partition by label or uuid, unbootable system

2009-10-31 Thread coding
@Andreas: It really doesn't matter if it is 512 times 1 byte or 1 time
512 bytes, but yes - doing one write is better ;)

-- 
unable to mount an ext2 partition by label or uuid, unbootable system
https://bugs.launchpad.net/bugs/428318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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


[Bug 428318] Re: unable to mount an ext2 partition by label or uuid, unbootable system

2009-10-30 Thread coding
Well, I had similiar situation as described in Andreas' report here: 
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/464411
but in my case doing dd bs=1 count=512 if=/dev/zero of=/dev/sda1 was sufficient 
(there were remainings of something that looked as old fat bootsector)

-- 
unable to mount an ext2 partition by label or uuid, unbootable system
https://bugs.launchpad.net/bugs/428318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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