Fixed with kernel 5.3.0-59
** Changed in: linux-signed-hwe (Ubuntu)
Status: New => 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/1882810
Title:
Regression: "shutdown -P" no
Public bug reported:
Since my latest upgrade (to kernel 5.3.0-53), "shutdown -P" no longer
powers off my computer. Apparently, the shutdown works normally up to
the last step: power off.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.3.0-53-generic 5.3.0-53.47~18.04.1
I think my current problem is related to long standing "nouveau" problems with
nVidia graphic cards: my "syslog" contains many entries of the form "nouveau
:00:0d.0: bus: MMIO write of FAULT at 00b020" (of "..." varies and
at "..." can end in "b000", "b010" instead of "b020").
Public bug reported:
I had nouveau related problems in Ubuntu 16.04: quite often, the display
screen was replaced by an irregular black and white pattern and the
system no longer reacted to the mouse or the keyboard.
Since the Ubuntu 18.04 upgrade, the problem shows itself slightly
differently.
I just recognized that the freeze does not inhibit all reactions to the
keyboard: "SysRq" keys are still recognized (at least this was the case
in my last 3 graphical login freezes).
I will try to find out whether I can clean the state via "SysRq" keys
(maybe the "V" key).
--
You received this
I have looked in "syslog". Apparently, the freeze always happens after
the message "systemd[]: Started Zeitgeist full-text search indexer".
In one case, "syslog" contains a sequence of about 100 zero bytes after
this message (and before the startup message after the reboot).
--
You received
I have activated "bionic-proposed", updated my system and performed a
test. Unfortunately, the problem is still there.
It showed itself slightly differently (this time - but the appearance
has varied in the past as well): instead of an irregular black and white
patterned background, I got my
Meanwhile, I have performed about half a dozen successful graphical
logins with the 4.15.0.36 kernel. As a consequence, I do no longer
believe that the observed problem has to do with the kernel upgrade to
4.15.0.36. Instead, I believe now that it is an intrinsic problem of the
graphical login in
Public bug reported:
Today, I performed the following upgrade:
Start-Date: 2018-10-06 06:52:59
Commandline: aptdaemon role='role-commit-packages' sender=':1.121'
Install: linux-headers-4.15.0-36-generic:i386 (4.15.0-36.39, automatic),
linux-modules-extra-4.15.0-36-generic:i386 (4.15.0-36.39,
Small correction for comment "#18": the command to selectively restore a
configuration option is "dconf write" (not "dconf set").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Title:
unity
The problem was caused by an old (created under Ubuntu 12.04) DCONF
configuration (attached).
Apparently, there is code to reset such outdated configuration. In my
case, however, "/usr/lib/i386-linux-gnu/unity/compiz-config-profile-
setter" (usually) crashed (sometimes a SIGSEGV; sometimes the
"unity" starts again successfully. Unfortunately, I do not why.
What I did:
I noticed that in "~/.cache.upstart.unity7.log" I saw
compizconfig - Info: Backend : gsettings
compizconfig - Info: Integration : true
compizconfig - Info: Profile : unity-lowgfx
The "unity-lowgfx" surprized me.
** Attachment added: "fail.activity"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5084784/+files/fail.activity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
** Attachment added: "ok.activity"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5084786/+files/ok.activity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Title:
** Attachment added: "diff.activity"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5084787/+files/diff.activity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
I have compared the "syslog" messages for a failing ("unity" startup
fails) and a successful ("unity" startup correct) login. There are some
differences. But for me, they do not seem critical: in the failing case,
apparently, someone tries to start a "bamfdaemon" which is already
running; in the
If I create a new user, "unity" starts fine (for this user).
This implies that the problem depends on the configuration of an old user
(created under Ubuntu 12.04).
"https://askubuntu.com/questions/17381/unity-doesnt-load-no-launcher-no-dash-appears/;
suggested to fix the problem by "dconf
Bug may be related to https://bugs.launchpad.net/ubuntu/+source/at-
spi2-core/+bug/1285444
There the content of ".xsession.errors" was requested:
** Attachment added: "xsession-errors"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5083418/+files/xsession-errors
** Attachment added: "dbus.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082963/+files/dbus.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Title:
** Attachment added: "upstart-event-bridge.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082968/+files/upstart-event-bridge.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "unity-panel-service.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082964/+files/unity-panel-service.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "window-stack-bridge.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082967/+files/window-stack-bridge.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "unity-settings-daemon.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082966/+files/unity-settings-daemon.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Downgrading of the above packages from "xenial-updates" to "xenial" has
not solved the problem. Further analysis is for the "xenial-updates"
versions.
At the beginning of the "unity session", "top" reveals a very high CPU
(and disk) usage by "dconf-service". Apparently, it is used by "compiz-
Public bug reported:
After today's update, the unity session after user login lacks window
decorations, panel and launcher. The only things correctly set up are
the background and the "auto-start" application windows (however, those
lack window decorations and do not present their menues).
I have lived for more than 1 year with the problem (as told earlier, the
freeze happens nowadays only occasionally) and, thus, I do not need a
backport but can wait for 18.04 to be released. Thank you again!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Using a different drive, I could successfully burn the daily Ubuntu Live
CD. I was not able to reproduce the freeze with the corresponding
installation.
Thank you for your support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> 3) As per your snipped log, it looks like you are grabbing logs from your
> install. What is
> needed are the logs/video from booting
> http://cdimage.ubuntu.com/daily-live/current/.
You are right. All attachments come from the installation, not the
"current" Ubuntu.
I see no chance to get
** Attachment added: "Full "kern.log""
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049380/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649566
Title:
** Attachment added: "Full dmesg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049379/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649566
Title:
** Attachment added: ""nouveau" related entries in "kern.log""
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049298/+files/nouveau.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> Then please post the results requested in
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/comments/21
> so it may be reviewed.
Comment 21:
>> If still reproducible, please post results following:
>> https://wiki.ubuntu.com/DebuggingKernelBoot
This is not applicable as booting is
> 1) To see if this is already resolved in Ubuntu, could you please test
> http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
I tried, but the resulting DVD does not boot:
-- maybe, because it is for for the x64 platform while I typically use the
i386 platform
Responses to your previous questions:
1) It may take a bit of time before I can make the tests with the current
Ubuntu version. And, I fear that such tests might not be reliable: after the
temporary use of the NVidia driver I could use the "nouveau" driver for some
time even without the special
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047624/+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/1649566
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047620/+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/1649566
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047621/+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/1649566
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047616/+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: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047627/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649566
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047623/+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: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047618/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649566
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047622/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047617/+files/Dependencies.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/1649566/+attachment/5047619/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047626/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649566
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1649566/+attachment/5047625/+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/1649566
Title:
apport information
** Tags added: apport-collected ubuntu xenial
** Description changed:
Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version
in each case). From 14.04 on, I was unable to graphically log in. A few
seconds after the login (varying between 1 and 10 s),
In comment #6 I had reported that "apport-collect 1649566" reproduces
the freeze.
I was now able to successfully transfer the data by calling "apport-
collect" outside the X system. Because, it did not run under X, it might
not contail all information you would like. In this case, let me know
how
Calling "apport-collect 1649566" reproducible causes the crash reported in this
ticket.
Is there a different way to provide the information you need?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For me, the situation has significantly improved with the latest Ubuntu
16.04: for "normal" operation, I no longer need "nouveau.config=NvMSI=0"
as kernel boot parameter.
I still see that things are not yet perfect:
* moving the mouse over the window top bar occasionally shows a black and
Public bug reported:
Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version
in each case). From 14.04 on, I was unable to graphically log in. A few
seconds after the login (varying between 1 and 10 s), the screen changed
to a pattern with dense white stripes on the violet/red
Affects Ubuntu 16.04 (XEmacs-mule 21.4.22) as well.
Setting "XMODIFIERS" to an empty value lets the problem go away. Likely,
the problem is caused by the particular value of "XMODIFIERS"
("@im=ibus", here).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for mentioning why firefox connects to Google.
After reading the privacy section of
http://en.wikipedia.org/wiki/Google_Safe_Browsing;, I have
banned all Google access via firewall rules -- I do not want Google to be able
to identify my computer.
--
You received this bug notification
Public bug reported:
A freshly started firefox with all extensions disabled, the flash
plugin enabled and all other plugins either disabled or in mode ask
before enabling, makes connections to some (not directly recognizable)
Google IP addresses.
At first, it used IP addresses from
In fact, this is not a bug - but a misunderstanding on my side about the
difference between halt and poweroff together with a change in
behaviour of halt.
If I use poweroff, the computer is correctly powered off. If I use
halt, the computer is halted but not powered off -- probably, as it
should
I tried the kernel. It does not boot. It comes until Switching to
clocksource tsc -- then nothing else.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags removed: needs-upstream-testing
** Tags added: kernel-unable-to-test-upstream
--
You received this bug
Public bug reported:
After system shutdown (and the message system halted) power remains
switched on.
I suspect that the signal to switch off power is not long enough.
I know that this problem has been reports often and already for a long
time -- but, it still is not fixed.
ProblemType: Bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054472
Title:
Failure to switch off power after system shutdown
To manage notifications about this bug go to:
Public bug reported:
Starting gnome_sudoku results in
lsdm: gnome-sudoku
[1] 3110
lsdm: /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning:
g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed
import gobject._gobject
** Changed in: gnome-games (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024377
Title:
gnome-sudoku crashes with SIGSEGV
To manage notifications about this
The problem was caused by a PYTHONPATH setting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024377
Title:
gnome-sudoku crashes with SIGSEGV
To manage notifications about this bug go to:
Poweroff still does not work for me with 3.2.0-26-generic-pae
#41-Ubuntu SMP Thu Jun 14 16:45:14 UTC 2012 i686 athlon i386 GNU/Linux
on an ASRock N68-GS3 UCC mainboard. The system shuts down, reports
system halted but power is not switched off.
--
You received this bug notification because you
62 matches
Mail list logo
