Public bug reported:
Release -> 18.04 LTS
Laptop Model -> Lenovo Ideapad S145
My wifi device is not detected.( Says Wifi Adapter not found).
Touchpad is not working.
Everything else is fine.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.3.0-28-generic 5.3.0-28.30~18.04.1
apport-collect 1849669 says the below...
"You are not the reported or subscriber of this problem report, or the
report is a duplicate or already closed.
Please create a new report using apport-bug"
** Attachment added: "Screenshot from 2019-11-01 07-26-19.png"
i some how upgraded with reinstalling all *ubuntu-desktop versions and
reinstalling gdm3/lightdm/python3 etc.. which one exactly worked.. i
did't know..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
distro-info:
Installed: 0.21ubuntu2
Candidate: 0.21ubuntu2
Version table:
*** 0.21ubuntu2 500
500 http://in.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
This is what i got
--
You received this bug notification because you are a member of
Yes. I have exact same bug. Still unable to upgrade :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849669
Title:
do-release-upgrade (19.04 -> 19.10) aborts
To manage notifications about this
2019-10-19 13:05:38,522 INFO Using config files '['./DistUpgrade.cfg']'
2019-10-19 13:05:38,522 INFO uname information: 'Linux DreamServer
5.0.0-32-generic #34-Ubuntu SMP Wed Oct 2 02:06:48 UTC 2019 x86_64'
2019-10-19 13:05:38,912 INFO apt version: '1.8.3'
2019-10-19 13:05:38,912 INFO python
Upgrade from 19.04 to 19.10 failed for me
Fetched 586 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Restoring original system state
Aborting
Reading package
Update: After upgrading to 17.04 (i.e. kernel 4.10*), I no longer have
this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655356
Title:
NMI watchdog: BUG: soft lockup - CPU#1 stuck for
Just upgraded to 17.04 and this appears to be fixed i.e. I don't see the
stupid 'initctl' running anymore!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173915
Title:
initctl continuously takes
Any update on a fix to this problem?
My work around is to kill the initctl if/when I restart; I haven't
noticed any adverse effect on anything I do on a daily basis and it is
running more than 2+ weeks with no sign of initctl going crazy. Since I
very rarely reboot (only after any updates and
Before trying the upstream kernel, I tried to replicate the issue. After
noticing it was happening every time there are heavy file I/O. I was
able to easily reproduce it at will by running apps that do lot of file
I/O. I was also monitoring free memory every second to understand why
kernel is
@jsalisbury, Thank you for the suggestions. I don't have the xenial
kernel handy as I have the habit of running apt-get autoremove after
upgrades. However, I will try the latest upstream kernel over this
weekend and report the results.
--
You received this bug notification because you are a
Kernel update to 4.8.0-34 did not make any difference.
Help please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655356
Title:
NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
Yesterday, I disabled NMI watch (a workaround discussed in another
similar bug report) but it still crashed this morning.
root@gorilla:~# sysctl -a|grep kernel.nmi_watchdog
kernel.nmi_watchdog = 0
Today, I upgraded to 4.8.0-34 from 4.8.0-32 kernel to see if that makes
any difference.
--
You
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802627/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802623/+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/1655356
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802624/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802626/+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/1655356
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802622/+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/1655356
Title:
NMI
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802625/+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/1655356
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802619/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802620/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
n memory. Removed the external backup drives to
isolate the problem. Checked similar issues on lanchpad.net but most of them
are related to video driver and power supply.
Appreciate help.
Thanks
-Arul
Attachments:
syslog
uname.txt
swaps.txt
dmesg.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802621/+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/1655356
Title:
NMI
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1655356/+attachment/4802618/+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/1655356
Title:
NMI
Attached files.tar containing
cpuinfo.txt
df.txt
dmesg.txt
initctl.txt
lspci.txt
lsusb.txt
meminfo.txt
swaps.txt
uname.txt
** Attachment added: "files.tar"
https://bugs.launchpad.net/ubuntu/+bug/1655356/+attachment/4802359/+files/files.tar
--
You received this bug notification because you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655356
Title:
NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
video driver and power supply.
Appreciate help.
Thanks
-Arul
Attachments:
syslog
uname.txt
swaps.txt
dmesg.txt
df.txt
lspci.txt
lsusb.txt
meminfo.txt
cpuinfo.txt
** Affects: ubuntu
Importance: Undecided
Status: New
** Attachment added: "syslog"
https://bug
Anyone found a fix or workaround for this problem? I have the same w/
Ubuntu 16.10
/sbin/initctl emit indicator-services-start
The initctl spinning out of control. This was NOT the case with the
previous version 16.04 and it only started to happen with 16.10.
--
You received this bug
The same issue affects when i tried to upgrade to 16.04 from 15.10
UbuntuGnome
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251588
Title:
ubuntu-release-upgrader crashed in save() with
*** This bug is a duplicate of bug 1251588 ***
https://bugs.launchpad.net/bugs/1251588
I have the same issue when i try to upgrade to 16.04 from 15.10 of
UbuntuGNome
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Rory, are you sure minidlna is now available in Trusty? or you
installed it from ppa:djart/minidlna ?
Here is how mine looks...
root@gorilla:~# apt-cache show minidlna
N: Unable to locate package minidlna
E: No packages found
root@gorilla:~# apt-get install minidlna
Reading package lists...
I tried re-authorizing with 'grive -a' but the error is still not going
away However, sync appear to be working just fine.
Wonder what is 're-linking' mean
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that Chroot is working in the proposed (2.4.6-2ubuntu2.1 )
Thank you for the fix.
-Arul
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails
I can confirm that Chroot is working in the proposed (2.4.6-2ubuntu2.1 )
Thank you for the fix.
-Arul
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot
Any update on when can we get a fix for this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot when not started as root error
To
Any update on when can we get a fix for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot when not started as root error
To manage notifications
Thank you for reviewing this bug report and assigning the severity.
While I agree with you on the assigned severity of Medium, I'd like
to point out that though ChrootDir is not a default option, it relates
to the security of apache server. I am not sure how many users simply
use the server w/
Thank you for reviewing this bug report and assigning the severity.
While I agree with you on the assigned severity of Medium, I'd like
to point out that though ChrootDir is not a default option, it relates
to the security of apache server. I am not sure how many users simply
use the server w/
** Changed in: ubuntu
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881164
Title:
massive syslog entries (GHES: Failed ...) after upgrade to oneiric
To
Public bug reported:
I have set my chroot directory as shown below.
ChrootDir /var/www
When started with the above chroot setting, apache2 exits with the
following error
[Sat Nov 16 13:52:40.621872 2013] [unixd:alert] [pid 3747] (34)Numerical
result out of range: AH02158: Cannot chroot when
Public bug reported:
I have set my chroot directory as shown below.
ChrootDir /var/www
When started with the above chroot setting, apache2 exits with the
following error
[Sat Nov 16 13:52:40.621872 2013] [unixd:alert] [pid 3747] (34)Numerical
result out of range: AH02158: Cannot chroot when
Finally, this problem is fixed in quantal (Ubuntu 12.10)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881164
Title:
massive syslog entries (GHES: Failed ...) after upgrade to oneiric
To manage
I moved to quantal (Ubuntu 12.10) and the problem is gone.
Looks like it is fixed in the chromium version i.e. Version 22.0.1229.94 Ubuntu
12.10 (161065)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same problem with my Ubuntu 12.04 as well. i.e. Chromium crashes very
frequently. This is 'confirmed' as a bug back in Aug but no solution so
far!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035932
Public bug reported:
Please help me on this.
I cant update anything. It is showing the following error
An unresolvable problem occurred while initializing the package information.
Please report this bug against the 'update-manager' package and include
the following error message:
Brian, thanks for the explanation, I had the same issue after upgrade to
Precise and its all good now after removing the old/duplicate rules as
per your suggestion!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
Brian, thanks for the explanation, I had the same issue after upgrade to
Precise and its all good now after removing the old/duplicate rules as
per your suggestion!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: update-manager
Traceback (most recent call last):
File /usr/lib/python2.5/logging/_init_.py, line 753, in emit selt.flush()
File /usr/lib/python2.5/logging/__init__.py, line 731, in flush
self.stream.flush()
IOError[Errno 9] Bad file descriptor
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/29802670/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/29802671/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
50 matches
Mail list logo
