This should probably be dup'd to bug 1731796.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734405
Title:
package samba 2:4.3.11+dfsg-0ubuntu0.16.04.11 failed to
install/upgrade: subprocess new
Happened again. Auto-bug reporting didn't recognize this report as
similar, so created bug 1734405
Note - compiz was in Z state (per top), consuming 100% of a cpu (per
top) throughout the incident. I was able to login via ssh and look at
things.
I don't believe that a stuck compiz process could
Public bug reported:
Same scenario as Bug #1731796; probably same root cause.
Observed the lockup a bit more closely this time.
It began with compiz in Z state (according to top), consuming 100% of a
cpu. In this situation, it was possible to ssh to the system.
I was running software updater,
The bug detection and reporting system wants to report this bug twice
;-) It's the same incident, but perhaps the actual error managed to
happen twice somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
My ubuntu system locks up regularly. Bugs I've reported about this get
closed for inattention, after being ignored, and queries about how to do
basic debugging get the same treatment, so I just power cycle whenever
it happens again.
This time the lock up happened while the
Public bug reported:
This is a bug report about errors during the upgrade process. I don't
know whether or not my samba installation was working immediately before
the upgrade; the windows box that was intended to be a client died and
has not been replaced. Don't believe my answers to the forced
Public bug reported:
My ubuntu system locks up regularly. Bugs I've reported about this get
closed for inattention, after being ignored, and queries about how to do
basic debugging get the same treatment, so I just power cycle whenever
it happens again.
This time the lock up happened while the
Public bug reported:
I don't believe that sane-utils is anything other than an innocent
victim of bug 1680502 - a general system hang involving systemd sleeping
uninterruptably while zombies pile up behind it, and cpu usage
skyrockets.
This morning I got a 1680502 hang during an attempt to
Today's "hang" involved a zombie compiz consuming 100% of a cpu, along
with an emacs instance consuming another 100%. Load average around 11,
and climbing. Only 22 zombies currently, but it was 4 when I managed to
get on with ssh.
I was in the process of installing software updates, using the GUI
Hmm - 73 zombies?! And systemd is in an uninterruptible sleep. It moreover has
not accumulated any time since I first ran top, so I'd say it's still in the
*same* uninterruptible sleep... for at least 14 minutes. Also, the number of
zombies has been increasing, as of right now, it's 187.
I
Note that the compiz process appears to be zombie, and "kill -9"
naturally fails to make it go away. I suppose it might be racking up all
this time attempting to dump core.
I wish I knew whether compiz has been berserk in all the cases where I
power cycled the system to regain control. If it has,
My apologies for going dark on you. I intend to try the upstream kernel,
but I've been haviing trouble finding time. With luck, I'll get it
installed this coming weekend.
Meanwhile, I've since had 2 or 3 standard recurrences, and one this
morning involving significantly diferent behaviour. (Of
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860539/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860533/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860537/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
This time, apport-collect appears to have worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
Title:
Hang after upgrade to 16.04
To manage notifications about this bug go to:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860538/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860536/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860534/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860535/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860527/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
Title:
Hang
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860531/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860528/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to
16.04 LTS.
12.04 was not entirely stable; something was crashing regularly, and the
Ubuntu tools make it hard for a user to
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860532/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860529/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1680502/+attachment/4860530/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Assigning this to "linux" package. I have no evidence as to whether this
is a kernel issue, or a case of user space processes with crazy
priorities and tight loops etc. However in my experience (a) it takes a
kernel person to distinguish the two (b) kernel people are more
responsive than whoever
No pop-ups after today's hang, so that symptom is probably coincidental.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680502
Title:
Hang after upgrade to 16.04
To manage notifications about this
It's done it again today. What do I need to gather to give you something
useful? And is there any way to get some action? Perhaps assign it to
kernel, even though like as not it's an application-level hangup?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I tried to run apport-collect specifying this bug, but I think something
may not have worked.
$ apport-collect 1680502
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=Km4k3CpdglJ0WgdZk2DF_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your
After I power cycled the system, I got 3 of the "system problem
detected" pop-ups, and told it I wanted them reported. I wasn't given an
opportunity to see what was reported, or add to it, so was unable to
reference this bug number. IF I understand what's behind the "user
friendly" wrapping, this
Public bug reported:
Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to
16.04 LTS.
12.04 was not entirely stable; something was crashing regularly, and the
Ubuntu tools make it hard for a user to determine what. The upgrade went
moderately well; I now get error messages
Public bug reported:
I tried to use do-release-upgrade to go from 14.04 to 16.04; instead the
upgrade crashed, I was left with a somewhat functional box that thought
it was on 16.04, yet still suggested I upgrade to 16.04.
Possibly relevant factors
- The system being upgraded was a virtual
What I eventually did to recover was something like:
dpkg -l | grep nvidia
followed by
sudo apt-get remove
of everything found above.
I'm not sure now whether this was the headers dependency issue
recurring, or some other nvidia problem. There were some error messages
at one point that
I think I may have the same thing, but not on initial install of the
system. My system worked, and then the unity GUI update installer
decided I needed a new kernel. (apt-get upgrade appeared to think the
kernel was pinned.) Now I have a system I don't know how to fix,
presently booted from a DVD,
Public bug reported:
This morning when I rebooted my 12.10 system it was essentially
unusable. I suspect it was broken by installing updates, using the GUI
tool that's part of unity. I believe I have nvidia. I'm pretty sure the
update tool has been giving me new kernels regularly; I'm guessing
Public bug reported:
I was installing Ubuntu 12.10. This was a fresh install into a newly
made partition. The system was on the corporate LAN, which has
functional DHCP, DNS and internet connectivity. I selected download
updates while installing. The system installed normally - but the
moment I
38 matches
Mail list logo
