This might be the same bug as #1764087
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764445
Title:
the system is running in low-graphics mode
To manage notifications about this bug go to:
--- Comment From hasri...@in.ibm.com 2018-04-23 04:28 EDT---
The following are the list of failures on Ubuntu mainline 4.17-rc1 kernel,
which is the same as of distro kernel.
Link: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc1/
# uname -a
Linux lep8d 4.17.0-041700rc1-generic
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the
Public bug reported:
(this was initially reported on the forum:
https://forum.snapcraft.io/t/libreoffice-6-0-3-not-so-stable/5032)
When trying to save a file under $HOME (not a subdirectory), the user is
presented with an error dialog:
--- Error ---
Error saving the document Untitled 1:
Object
** Changed in: ubiquity (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765651
Title:
Do not run gnome-initial-setup during OEM preparation
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the
Same issue here with a Dell wireless scanner. I don't think the hardware
matters, as the images are scanned fine by Simple Scan, and I can save
the scanned pages individually as PNG files.
But saving them in a PDF results in a file that has parts of the scanned
pages overlaying each other with
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 3.13.0-145.194
---
linux (3.13.0-145.194) trusty; urgency=medium
* linux: 3.13.0-145.194 -proposed tracker (LP: #1761430)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920)
Thanks Sergeev, that is an interesting insight.
$ mkdir /tmp/service
# works
$ qemu-system-x86_64 -enable-kvm -vnc unix:/tmp/service/vnc-sock
# fails
$ qemu-system-x86_64 -enable-kvm -vnc
unix:/tmp/service/../service/../service/../service/vnc-sock
And while these are running in another shell
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 3.13.0-145.194
---
linux (3.13.0-145.194) trusty; urgency=medium
* linux: 3.13.0-145.194 -proposed tracker (LP: #1761430)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920)
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 3.13.0-145.194
---
linux (3.13.0-145.194) trusty; urgency=medium
* linux: 3.13.0-145.194 -proposed tracker (LP: #1761430)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920)
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 3.13.0-145.194
---
linux (3.13.0-145.194) trusty; urgency=medium
* linux: 3.13.0-145.194 -proposed tracker (LP: #1761430)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920)
This bug was fixed in the package linux - 3.13.0-145.194
---
linux (3.13.0-145.194) trusty; urgency=medium
* linux: 3.13.0-145.194 -proposed tracker (LP: #1761430)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920)
This bug was fixed in the package linux-hwe-edge - 4.15.0-15.16~16.04.1
---
linux-hwe-edge (4.15.0-15.16~16.04.1) xenial; urgency=medium
* linux-hwe-edge: 4.15.0-15.16~16.04.1 -proposed tracker (LP:
#1761184)
* linux: 4.15.0-15.16 -proposed tracker (LP: #1761177)
* FFe:
This bug was fixed in the package linux-hwe-edge - 4.15.0-15.16~16.04.1
---
linux-hwe-edge (4.15.0-15.16~16.04.1) xenial; urgency=medium
* linux-hwe-edge: 4.15.0-15.16~16.04.1 -proposed tracker (LP:
#1761184)
* linux: 4.15.0-15.16 -proposed tracker (LP: #1761177)
* FFe:
This bug was fixed in the package linux - 3.13.0-145.194
---
linux (3.13.0-145.194) trusty; urgency=medium
* linux: 3.13.0-145.194 -proposed tracker (LP: #1761430)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
This bug was fixed in the package linux - 3.13.0-145.194
---
linux (3.13.0-145.194) trusty; urgency=medium
* linux: 3.13.0-145.194 -proposed tracker (LP: #1761430)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920)
*** This bug is a duplicate of bug 1763687 ***
https://bugs.launchpad.net/bugs/1763687
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
pisi@Pisi-U1804PC:~$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=tr_TR.UTF-8
LC_TIME=tr_TR.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=tr_TR.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=tr_TR.UTF-8
LC_NAME=tr_TR.UTF-8
LC_ADDRESS=tr_TR.UTF-8
LC_TELEPHONE=tr_TR.UTF-8
This bug was fixed in the package linux-lts-xenial -
4.4.0-121.145~14.04.1
---
linux-lts-xenial (4.4.0-121.145~14.04.1) trusty; urgency=medium
* linux-lts-xenial: 4.4.0-121.145~14.04.1 -proposed tracker (LP:
#1763688)
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
*
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-lts-xenial -
4.4.0-121.145~14.04.1
---
linux-lts-xenial (4.4.0-121.145~14.04.1) trusty; urgency=medium
* linux-lts-xenial: 4.4.0-121.145~14.04.1 -proposed tracker (LP:
#1763688)
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
*
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ca-certificates (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765972
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: simple-scan (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748179
Title:
Public bug reported:
cinder-volume-Agent is marked as down if upload of volume needs longer
than heartbeat-timeout.
steps to reproduce:
1. create a big Volume (f.e. 100G)
2. fill the volume with data to avoid too fast upload
3. tell cinder to upload the volume as image
4. watch
** Changed in: gvfs (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753548
Title:
gvfsd-dav crashed with SIGABRT in raise()
To manage notifications
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
Sounds like this might be a fix:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/221
Apparently that's related to bug 1765353 too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765593
Title:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1765651
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Description changed:
Could you include the output of the command "locale" on the system which
is displaying the wrong format?
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
Setting ad_gpo_access_control to disabled did not solve the problem.
I can confirm, that all files in the domain users mounted homefolder are
owned by the user with the rights set to 700.
In the timeframe i tried to trigger the error, the only entrances in
/var/log/syslog were:
Apr 23 09:50:10
The fix sounds like something worth trying to get still in for the
release
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => High
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: qemu (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705743
Title:
qemu-system-x86 crashes when VNC connection is established
To manage
** Branch linked: lp:~didrocks/ubiquity/oem-mode-telemetry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765693
Title:
[telemetry] Record OEM installation mode
To manage notifications about this
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
Public bug reported:
I think this is the same bug as
https://bugs.openjdk.java.net/browse/JDK-8199307 but as I don't have an
openjdk account, maybe someone can post this fairly small reproducer
there:
root@bionic:~# wget
Could you add the stdout from when getting the issue or the journal log
around that time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766129
Title:
Clicking any checkbox freezes the program
To
Public bug reported:
[Impact]
An instruction in apache config such as the following will make apache2
fail to start:
IncludeOptional /etc/apache2/mellon/sp-location*.conf
https://paste.ubuntu.com/p/f2Tb9rgrBB/ (full file: /etc/apache2/sites-
enabled/openstack_https_frontend.conf)
Apr 23
The typo has been fixed in that upload
http://launchpadlibrarian.net/366294537/gnome-initial-setup_3.28.0-2ubuntu3_3.28.0-2ubuntu6.diff.gz
-+ _("Failed to get report informaiton:
%s"), error);
++ _("Failed to get report
** Changed in: gnome-initial-setup (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765233
Title:
tweak location formatting
To manage notifications about
The issue has been fixed in that update
https://launchpad.net/ubuntu/+source/gnome-initial-setup/3.28.0-2ubuntu6
** Changed in: gnome-initial-setup (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-initial-setup (Ubuntu)
Status: New => Fix Released
--
You received this bug
** Changed in: ubuntukylin
Status: Fix Committed => Confirmed
** Changed in: ukui-control-center (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766021
Title:
linux: 4.15.0-19.20 -proposed tracker
To
I'm sorry, #1 I reply wrong. That's my bug for another one
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764663
Title:
you need load the kernel first
To manage notifications about this bug go to:
Thanks for your suggestion.
** Summary changed:
- Impossible to choose a language when booting in UEFI, as Ubiquity never opens
due to problematic grub config
+ Impossible to boot in maybe-ubiquity mode and choose a language when booting
in UEFI
** Changed in: grub2 (Ubuntu)
Importance:
This bug was fixed in the package shim-signed - 1.34.4
---
shim-signed (1.34.4) bionic; urgency=medium
* Handle the case that there are no kernel modules available for a given
dkms package. This probably indicates there is a problem with the dkms
module's installation, but
This bug was fixed in the package dkms - 2.3-3ubuntu7
---
dkms (2.3-3ubuntu7) bionic; urgency=medium
* 0009-Add-support-for-UEFI-Secure-Boot-validation-toggling.patch: update
for the new update-secureboot-policy code: have it generate a new MOK if
there isn't one yet, and
Public bug reported:
start Hardware Lister from launch bar
empty panel appears
click
system freezes
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lshw-gtk 02.17-1.1ubuntu3.5
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
Has been resolved:
my zunclient version is 1.0.0
# pip uninstall python-zunclient
# pip install python-zunclient==1.2.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764663
Title:
you need load
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Fix Committed
** Tags
*** This bug is a duplicate of bug 1754174 ***
https://bugs.launchpad.net/bugs/1754174
** This bug has been marked a duplicate of bug 1754174
[Lubuntu] "Install Lubuntu" fails with several commands not found and
permission denied
--
You received this bug notification because you are a
** Summary changed:
- Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually
works on the second attempt
+ [regression] Ubuntu 18.04 login screen rejects a valid password on first
attempt. Usually works on the second attempt
** Tags added: regression
--
You received
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Also affects: resteasy3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682149
Title:
dogtag-pki stops working with resteasy newer than
Hi Michael,
thank you for the discussion, no need to apologize - I can see your troubles
and want to help.
But lets dissect the different aspects of it.
TL;DR:
- path in qemu.conf should not matter
- need to set-uid manually is wanted for security reasons
- apparmor fixes exist, please chime in
** Tags added: regression
** Summary changed:
- Login fails when preceded by incorrect password
+ [regression] Login fails when preceded by incorrect password
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status:
This has been in -proposed for 4 days now, and there have been multiple
bug reports in that time from users who have -proposed enabled - but
none against the latest version which has been in -proposed for 24h+.
Dropping the block-proposed tag now to let this migrate.
** Tags removed:
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766176
Title:
initramfs-tools returns error while
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Fix Committed
** Tags
You have to add the initramfs option to /etc/crypttab, but otherwise
it's just the warning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612906
Title:
cryptsetup does not support ZFS
To manage
*** This bug is a duplicate of bug 1754174 ***
https://bugs.launchpad.net/bugs/1754174
** This bug has been marked a duplicate of bug 1754174
[Lubuntu] "Install Lubuntu" fails with several commands not found and
permission denied
--
You received this bug notification because you are a
The solution seems to be re-issue the apt dist-upgrade command again.
And this time the upgrade process will ended successfully with a
Warning:
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
Here's the installation log from the day the regression happened (I
think).
Start-Date: 2018-04-19 09:16:47
Commandline: apt full-upgrade
Requested-By: dan (1000)
Install: libisc169:amd64 (1:9.11.3+dfsg-1ubuntu1, automatic),
libisc-export169:amd64 (1:9.11.3+dfsg-1ubuntu1, automatic),
My fault didn't explain properly. My computer is UEFI but want to
perform a MBR install to boot on legacy systems. I follow this video:
https://youtube.com/watch?v=F0b4I89LY5E
chroot at 12:20
grub-install at 15:30, which is where I get the error with modinfo.sh. It's
fixed by installing
Thanks for your report. This problem has been fixed in recent builds.
Could you please try a newer image and report back if it is still
happening.
Thanks for your help.
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
Please try to log in to the machine via ssh first, and start monitoring
the system log before reproducing the problem:
journalctl -f
Then reproduce the bug (log in graphically) and let us know what the
output from journalctl -f was at the time the bug occurred.
** Changed in: gdm3 (Ubuntu)
I think I might have hit this finally. The blank purple screen with a
mouse cursor probably means the shell failed to start. And indeed I have
no gnome-shell process running for my UID. The journalctl shows:
pr 23 14:33:47 haz gnome-shell[912]:
g_dbus_connection_call_sync_internal: assertion
EXAMPLE 2
/var/log/auth.log
LOGIN FAILED:
Apr 23 14:33:34 haz gdm-password]: pam_unix(gdm-password:auth): authentication
failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=dan
LOGIN ALMOST SUCCEEDED (but then hit bug 1766137):
Apr 23 14:33:46 haz gdm-password]:
EXAMPLE 3
journalctl -b -f
LOGIN FAILED:
Apr 23 14:40:40 haz gdm-password][1342]: pam_unix(gdm-password:auth):
authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost=
user=dan
Apr 23 14:40:46 haz systemd[1]: Starting Stop ureadahead data collection...
Apr 23 14:40:46 haz
** Summary changed:
- grub-pc-bin not available in ubuntu-18.04-beta2-desktop-amd64.iso
+ grub-pc-bin not available on chroot fresh install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766018
EXAMPLE 1
/var/log/auth.log
LOGIN FAILED:
Apr 23 14:30:40 haz sudo: pam_unix(sudo:session): session opened for user root
by dan(uid=0)
Apr 23 14:30:57 haz gdm-password]: pam_unix(gdm-password:auth): authentication
failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=dan
LOGIN
Public bug reported:
This issue was spotted on a ThunderX ARM64 system and s390x, AMD64
system does not have this issue
Steps:
1. Deploy a ThunderX ARM64 node
2. Enable -proposed, commence apt update and dist-upgrade
Result:
Setting up linux-generic (4.15.0.19.20) ...
Processing triggers
*** This bug is a duplicate of bug 1754623 ***
https://bugs.launchpad.net/bugs/1754623
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1754623, so is being marked as such.
(In reply to comment #80)
> Hello Canonical,
>
> There are two problems here
>
> 1. Hang when CPUs don't respond to IPI. This can be resolved by setting a
> non-zero panic timeout.
> That fix is now available in Ubuntu releases.
>
> 2. But dump capture is still not successful with case1
It's clear that even dogtag 10.6.0 doesn't work with resteasy 3.1, so
either resteasy3.0 needs to stay in bionic, or src:resteasy will be
reverted to 3.0.19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
- Message de réponse -
De : "Pablo Estigarribia"
Pour :
Objet : [Bug 1502263] Re: Shutter does not work in Wayland
Date : dim., avr. 22, 2018 14:35
I have just found another software that works on wayland
https://github.com/lupoDharkael/flameshot
Same problem on a fresh install from Ubuntu 18.04 LTS "Bionic Beaver" - Alpha
amd64 (20180421)
updated today
corrado@corrado-p7-bb-0421:~$ inxi -Fx
System:Host: corrado-p7-bb-0421 Kernel: 4.15.0-15-generic x86_64 bits: 64
gcc: 7.3.0
Desktop: Gnome 3.28.1 (Gtk 3.22.30-1ubuntu1)
*** This bug is a duplicate of bug 1754214 ***
https://bugs.launchpad.net/bugs/1754214
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1754214, so is being marked as such.
Public bug reported:
Please sync wine-development 3.6-1 (universe) from Debian unstable
(main)
Changelog entries since current bionic version 3.5-1:
wine-development (3.6-1) unstable; urgency=medium
* New upstream release 3.6, released Apr 13, 2018.
- Support for PNG format icons.
-
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Fix Committed
** Tags
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Description changed:
901 - 1000 of 1002 matches
Mail list logo