Public bug reported:
New to Linux/UBUNTU but expert in Windows/programming.
Evidently my Device/Display options are very limited, when I connect a
projector the second display can use only a low resolution, much below the
projectors capability. I tried to check for the video driver and I got
I have found that if I set the reboot once at 15 min, the server works
for 5-6 days. If the reboots are done once at 10 min, the server get
stuck in 24-48h max. Now I'm testing the reboots once at 20min, it
should take 10 days or more until is stuck.
Also, I have tried all "reboot=" grub options,
I have activated RuntimeWatchdogSec=20s and ShutdownWatchdogSec=1min in
/etc/systemd/system.conf and set the reboot, the server get stuck in
105min.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
The test server get stuck after ~9h, here is the debug log.
** Attachment added: "shutdown-log-process.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5241740/+files/shutdown-log-process.txt
--
You received this bug notification because you are a member of
Tested with multiple OSs, all stuck: Ubuntu 14, Fedora 29, Arch Linux
current 2019.02.01.
We received a detailed note from the next level of support with HPE and
decided to test with Ubuntu 16 (our production one) and set "ps -ef >>
/shutdown-log.txt" in to the debug.sh script. Maybe we can see
This get stuck in max 5 hours. We'll try to install a non systemd
Ubuntu, like v14 to test it.
** Attachment added: "centos7.PNG"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5240612/+files/centos7.PNG
--
You received this bug notification because you are a
We installed Centos 7 and started the reboot test now. If this fail
again then is a hardware issue, if not, then it can be from Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
That was already tested and no luck.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
Status in dbus package in Ubuntu:
I have disabled the acpi services (acpid.path, acpid.service,
acpid.socket and set up the reboot once at 5 min. The server get stuck
after 13h.
Something else to try?
** Attachment added: "reboot-acpi-off.zip"
After 5 hours of reboot the server is stuck. See the attached debug log
and ILO capture.
** Attachment added: "Ubuntu-18.zip"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5238635/+files/Ubuntu-18.zip
--
You received this bug notification because you are a
We sent all the logs and captures data to HPE and they asked to update
the BIOS to the latest one. We already using the latest firmware, 4
months past the recommended firmware. Also, we have 200 servers with
Windows 10 doing same test - reboot after each test and there are no
hangs. HPE stated
Public bug reported:
I have a Dell Latitude E7470 laptop with a docking station and two
external monitors.
I made a system update yesterday (without restart), and I tried to work
today.
When the laptop lid is laid off, all displays are black and stays that
way. When it's open, it works fine. If
After 36h of rebooting, the system is stuck. Attached is the debug log.
** Attachment added: "shutdown-logsysd237.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5232412/+files/shutdown-logsysd237.txt
--
You received this bug notification because you are a
We will notify them if the systemd does not fix the issue. So far, after
the systemd upgrade, the server reboots fine in 24h test (reboot once at
5 min).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
reboot=pci does not help, it get stuck after 19 hours (reboot once at 5
min). Attached is the debug log. On ILO we get the same as I sent in my
first post - see capture from the arhive.
We'll update systemd to 237 and test it.
** Attachment added: "shutdown-log-reboot-pci.txt"
I did not tried reboot=pci, will try now. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
Status in dbus package in
Here at Mozilla, we have 200 servers running on HP Moonshot system, all
have same hardware configuration and Ubuntu 16.04.2. The OS is not up to
date, we use it as is was released. We using a program to tests Firefox
source code and after each test we reboot the servers using
/sbin/reboot. After a
UPDATES that could have caused the work-space switcher to malfunction:
Start-Date: 2018-02-01 00:51:22
Commandline: (hidden)
Upgrade: libwebkit2gtk-4.0-37:i386 (2.18.5-0ubuntu0.16.04.1,
2.18.6-0ubuntu0.16.04.1), gir1.2-webkit2-4.0:i386 (2.18.5-0ubuntu0.16.04.1,
2.18.6-0ubuntu0.16.04.1),
RE: 64-bit version OS
Hi christopher,
So, you're recommending that I abandon this bug report? Meaning that
there is no hope of being fixed? :)
I will consider shifting to 64-bit, I did in the past, only that some
thoughts are still holding me back.
Many thanks!
--
You received this bug
Hi again, Christopher,
Thanks for the tip! /var/log/apt is only listing some updates from the
2nd February, so that is now too helpful.
I however found my way around in Ubuntu Software Center and was able to
locate the updates by date, however, I can't exactly recall which day it
was that ruined
RE: http://cdimage.ubuntu.com/daily-live/current/
I am currently using a 32 bit version still (because of an older version
of truecrypt).
Do you, Christopher, think that if I set up bionic-desktop-amd64.iso on
a usb stick and boot to try out Ubuntu, I will be able to test the
desktop work-space
Hi Christopher, I would like, however I can not remember, sorry. If I am
not mistaking, there was an update (the update window popped up) with
only a few KB in size... the usual "Ubuntu base" ?
If there is any way of me figuring out how o answer your question,
please let me know and I will do my
I forgot to mention that if I am on a workspace and I click the browser
on my launchpad (the browser is already open on another workspace) then
actually nothing happens now...I used to be sent to the workspace the
browser is open, however NOW... nothing... I have to manually switch to
the
Public bug reported:
Hello!
After the update manager popped up and I've done the update, it seems
that the ctrl alt arrows are no longer working to switch between the
workspaces?
I can still switch by using the mouse andthe icon on the launcher, it
just takes more time and Idislike that.
Public bug reported:
Applicatin crashes on login
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
Uname: Linux 4.13.4-041304-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Sep 27 09:34:46 2017
ErrorMessage: telepítve
** Attachment added: "mem.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4649398/+files/mem.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This still happens in 16.04 LST! As it was described several times above
the shutdown process somehow blocks/gets in a deadlock when un-mounting
the swap partitions. I did not understood exactly what happens but the
recovery console clearly shows that the swap space is still on and
vailable and
cantor and gwenview also crashes when closing the lid of the laptop.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
@dino99:
The problem is present in Xenial. Nothing changed after I upgraded to Ubuntu
16.04 LTS preview.
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I'm just wondering if we could set some timeout for the shutdown in the
systemd configuration files.
I tried to add the following to the /usr/lib/systemd/user/shutdown.target
config:
JobTimeoutSec=30
JobTimeoutAction=poweroff-force
but unfortunately it has no effect.
--
You received this bug
I can confirm too that the issue is probably something to do with the
swap usage.
My first guess was that the problem has something to do with the
system's update, but seems that real cause is the swap usage. The
shutdown usually goes fine when the system is used only for a short time
and fails
** Attachment removed: "Shutdown process (without splash screen)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4512903/+files/shutdown.png
** Attachment added: "Shutdown process (without splash screen)"
I can confirm that happens with 15.10 too.
Attached a screenshot that shows a successful shutdown process (without
splash screen). The red line marks the moment where the process hangs if
the shutdown fails.
The workaround with the SysRq key presented here worked for me:
*** This bug is a duplicate of bug 1033598 ***
https://bugs.launchpad.net/bugs/1033598
** This bug has been marked a duplicate of bug 1033598
the CAPTCHA challenge in Ubuntu Software Center is much too difficult to
solve for a real human being
--
You received this bug notification
Same on BQ E4.5 with latest firmware
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1413600
Title:
Cannot silence an incoming call with volume keys
Status in
Looks like today's ubuntu updates fixed the bug, which is strange. The
/var/log/apt/history.log entry produced by the update is:
Start-Date: 2015-02-03 22:51:31
Commandline: aptdaemon role='role-commit-packages' sender=':1.136'
Install: linux-image-extra-3.13.0-45-generic:amd64 (3.13.0-45.74),
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1414494
Title:
reboot after shutdown Gigabyte
Since we are not sure if this is a kernel issue, I added upstart to the
affected projects.
If someone from the upstart maintainers is able to cross out upstart as
the source of the bug, then I will open an upstream bug report against
the latest kernel.
To penalvch: halting instead of poweroff is
Could not reproduce it on Ubuntu 14.04.1 + subdownloader 2.0.14-1.1.
(BTW, the original report was filed against Ubuntu 12.04 LTS, which is
still supported... whatever... if no one bothered to confirm it for 1.5
years, I won't care neither.)
** Changed in: unity
Status: Incomplete =
)
Because I using both Ubuntu and Windows, I set UTC=no setting into
/etc/default/RCS file.
Because now happened a time zone change (I using Europe/budapest timezone), I
ran hwclock -w --localtime command.
Next clock change need in europe/budapest timezone with 2015. last march sunday.
Attila
Thank you Julien at #7, you saved my day!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1286836
Title:
package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to
41 matches
Mail list logo
