*** This bug is a duplicate of bug 2054795 ***
https://bugs.launchpad.net/bugs/2054795
I'm using completely different hardware and have the same issue as reported in
first post.
Using ISO dated March 9th, 2024
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 2046844 ***
https://bugs.launchpad.net/bugs/2046844
Both Xubuntu and Ubuntu have this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055973
Title:
Installed without issue, using "2021-11-24 08:32" ISO
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951399
Title:
Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to
install
To
1. The specific steps or actions you took that caused you to encounter the
problem.
Started the install process, from the Install system icon.
2. The behavior you expected.
Expected install to completion
3. The behavior you actually encountered (in as much detail as possible).
Near the end of
Public bug reported:
Ubuntu 22.04, dated 11/17
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 21.10.10
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
Public bug reported:
Ubuntu Impish Indri (development branch 21.10
Trying the new installer "ubuntu-desktop-installer", it fails. Ubiquity
installs okay.
=results using the new installer===
ubuntu@ubuntu:~$ ubuntu-desktop-installer
[ERROR:flutter/lib/ui/ui_dart_state.cc(209)]
Oops. I was on 21.10 using older gnome 38. Not sure about 20.04. I
don't think they will get gnome 40.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900907
Title:
20.04 Slow icons in dock
To
Its fixed with current updates and gnome 40:
$ apt policy gnome-shell
gnome-shell:
Installed: 40.2-1ubuntu1
Candidate: 40.2-1ubuntu1
Version table:
*** 40.2-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status
No more slow
This effects the currently released Ubuntu 21.04. It takes 20 seconds
for icons to appear on dock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900907
Title:
20.04 Slow icons in dock
To manage
crash info attached.
** Attachment added:
"_usr_libexec_ayatana-indicator-keyboard_ayatana-indicator-keyboard-service.999.crash"
This ayatana crash happens each time I boot up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915551
Title:
ayatana-indicator-keyboard-service crashed with SIGSEGV in
keyboard_GetLayout()
To
The corrected ISO date is this:
hirsute-desktop-amd64.iso 2021-01-26 05:51
from Kubuntu daily-live current. It still fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
This bug is still failing per current ISO dated 01/25/2021 booting from
Kubuntu 21.04:
$ sudo dmesg|grep failed
[0.538632] Initramfs unpacking failed: Decoding failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug failure is still present as of current ISO dated 01/25/2021 using
Kubuntu:
[code]vmc@01-25-21:~$ sudo dmesg|grep failed
[0.538632] Initramfs unpacking failed: Decoding failed[/code]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Its fixed, sort of. I needed to remove the linux line "maybe-ubiquity"
for it to boot to a desktop. Leaving "maybe-ubiquity" in, I was left
with a black screen with no way to resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sometimes there's a work around in lieu of a fix. I haven't found one
for this bug yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903378
Title:
ubiquity in live session and ubiquity-dm fails
Just booted up to desktop with 'maybe-ubiquity' removed.
Found failed fail in "/var/crash""
** Attachment added: "_usr_lib_ubiquity_bin_ubiquity.0.crash"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1903378/+attachment/5443881/+files/_usr_lib_ubiquity_bin_ubiquity.0.crash
--
You
The current Kubuntu hirsute-desktop-amd64.iso, dated: 2020-12-15 05:55, fails
to start.
If I remove "maybe-ubiquity" from the boot-option, then it will boot up, but
install icon fails.
This has failed same way for the past week.
--
You received this bug notification because you are a member
I found this that removing the file in "/var/crash/", stopped systemd-
journal from filling up. Now systemd process is normal after a reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895573
I'm getting the same error. Systemd-journal is filling up to over a gig of
useless data. Just reports:
"Sep 18 15:27:51 vmc-TC-885 systemd[1]: Failed to start Process error reports
when automatic reporting is enabled."
--
You received this bug notification because you are a member
Ye, I tried X,K,U,b ubuntu, and all boot without errors. I also prefer
gzip. I had the reverse though. I find gzip is faster than lz4, and I'm
using nvme for boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In post#14, I showed how my gzip booted faster.
"We currently believe that the decoding error reported in dmesg is
actually harmless and has no impact on usability on the system."
If 'harmless', then why the error in the first place? Something is
causing it. Sticking the error in the sand is NOT
Xubuntu 20.04 failed:
$ dmesg |grep failed
[0.456889] Initramfs unpacking failed: Decoding failed
[5.838496] thermal thermal_zone2: failed to read out thermal zone (-61)
[6.053231] [drm] failed to retrieve link info, disabling eDP
Then issued the following:
$ sudo update-initramfs
My Secure Boot is always off, and all three U, X, Kubuntu have the
error, as of yesterdays ISO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs unpacking failed
To manage
Boot up is actually faster after fix:
dmesg, boot-time b4-fix
$ dmesg|grep Decoding
[0.461068] Initramfs unpacking failed: Decoding failed
$ systemd-analyze
Startup finished in 14.140s (firmware) + 4.226s (loader) + 6.079s (kernel) +
17.270s (userspace) = 41.717s
graphical.target
Did you read the part: "initramfs unpacking failed: Decoding failed".
So what's the point if its faster and fails?
If you have splash on, you won't see the error message. use dmesg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
as of 10/12/2019 eoan 19.10, Ubuntu, Lubuntu, Xubuntu still have this
issue.
What I do to "fix" it is change:
COMPRESS=lz4, to COMPRESS=gzip, @:
/etc/initramfs-tools/initramfs.conf, then
sudo update-initramfs -u.
--
You received this bug notification because you are a member of Ubuntu
"initramfs unpacking failed: Decoding failed" message still fails.
Using:
eoan ubuntu-budgie, ISO dated 7/18/19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs unpacking
As of today's ISO (7/11) installed, there is no "initramfs unpacking
failed: Decoding failed" message. It appears solved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs
There are two messages that appear, the first is "initramfs unpacking
failed: Decoding failed", right afterwards the partitions is clean
message appears.
So, yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also noticed on July 3rd thereabouts, was a change for 'lz4', that was
approved.
Not sure if I had this error then. I just started noticing around July 7th.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still fails:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
Codename: eoan
===
thermald:
Installed: 1.8.0-1ubuntu1
Candidate: 1.8.0-1ubuntu1
Version table:
*** 1.8.0-1ubuntu1 500
500
** Package changed: ubuntu => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs unpacking failed
To manage notifications about this bug go to:
Public bug reported:
"initramfs unpacking failed: Decoding failed", message appears on boot
up.
If I "update-initramfs" using gzip instead of lz, then boot up passes
without decoding failed message.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: eoan ubuntu
--
This error is for Ubuntu eoan.
** Tags added: eoan ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs unpacking failed
To manage notifications about this bug go to:
Fix with June 21st ISO.
** Changed in: ubiquity (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/1833626
Title:
Failed to create swap space
To manage
I found out it only occurs using Kubuntu 19.10 and ubiquity version
19.10.5, which it now uses.
The current Ubuntu 19.10 still uses ubiquity 19.10.3 and it installs
correctly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ubiquity-kde-version"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1833626/+attachment/5271947/+files/ubiquity-kde-version
** Attachment removed: "ubiquity-kde-dm"
** Attachment added: "ubiquity-kde-dm"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1833626/+attachment/5271945/+files/ubiquity-kde-dm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ubiquity-kde-syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1833626/+attachment/5271946/+files/ubiquity-kde-syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ubiquity-kde-dm"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1833626/+attachment/5271944/+files/ubiquity-kde-dm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ubiquity 19.10.3 installs using swap partition, ubiquity 19.10.5 FAILS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833626
Title:
Failed to create swap space
To manage notifications about this
Ubuntu/Kubuntu 19.20 "eoan" version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833626
Title:
Failed to create swap space
To manage notifications about this bug go to:
Public bug reported:
I get the following error on my swap space:
"The creation of swap space in partition #7 of /dev/nvme0n1 failed"
nvme0n1
├─nvme0n1p1 vfat ESP 961F-698A 36.9M62%
I get the pcie errors on all X,L,K Ubuntu's disco 19.04
[ 3056.549121] pcieport :00:1c.0: AER: Corrected error received:
:00:1c.0
[ 3056.549136] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected,
type=Data Link Layer, (Transmitter ID)
[ 3056.549147] pcieport :00:1c.0:
ubiquity 19.04.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818586
Title:
Unable to install Xubuntu 19.04
To manage notifications about this bug go to:
Ubiquity 19.04.6
/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py:54: PyGIWarning: Gtk was imported
without specifying a version first. Use gi.require_version('Gtk', '3.0') before
import to ensure that the right version gets loaded.
from gi.repository import Gtk, Gdk, GObject, GLib, Atk, Gio
Public bug reported:
Ubiquity hangs on "Updates and software", and does not progress
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "picture of stalling"
cat /proc/version
Linux version 4.19.0-13-generic (buildd@lcy01-amd64-027) (gcc version 8.2.1
20190204 (Ubuntu 8.2.0-17ubuntu6)) #14-Ubuntu SMP Thu Feb 7 21:51:25 UTC 2019
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
p; [[ $(tty) = /dev/tty1 ]]; then
exec startx -- vt1 &> /dev/null
fi
===getty===
sudo systemctl edit getty@tty1
add the following text:
[Service]
ExecStart=
ExecStart=-/sbin/agetty --skip-login --noissue -a vmc %I $TERM
===
To verify that getty is correct:
cat /etc/systemd/system/getty@tty1.service.d/
Auto-login using ".xinitrc" method
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817449
Title:
Lubuntu 19.04 lxqt-config-monitor fails
To manage notifications about this bug go to:
Public bug reported:
$ /usr/bin/lxqt-config-monitor
(0x7e4183c0) Warning: Failed to request backend:
"org.freedesktop.DBus.Error.Spawn.ChildExited" : "Process org.kde.KScreen
exited with status 1"
(0x7e4183c0) Debug: Connecting to KScreen...
(0x7e4183c0) Debug:
Xubuntu is now fixed using current ISO:
disco-desktop-amd64.iso 2018-11-08 02:22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801408
Title:
disco installer crashed with usr-merge
To
Jeremy, Thanks! Its reported that its been fixed. I guess I thought
Ubuntu & Xubuntu shared the same Ubiquity with different proceeds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801408
Title:
xubuntu md5sum: 8496e3986821cb895fc9ed0b202edaf9 fails to install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801408
Title:
disco installer crashed with usr-merge
To manage notifications about
Still fails installing current Xubuntu:
disco-desktop-amd64.iso 2018-11-07 02:42
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801408
Title:
disco installer crashed with usr-merge
To
My crashed stated:
FileNotFoundError:
[Errno2] No such file or directory: '/target/sbin/start-stop-daemon'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801408
Title:
disco installer crashed with
Public bug reported:
Using current Xubuntu Disco ISO. During installation, the installer
crashed.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 18.10.12
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion:
I use getty auto login, and ".xinitrc" starts startlxqt. Maybe I need to
add lxqt-session, but none needed in the past. It works now with just
exec startlxqt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Alf, Thanks. A re-install proved you right. I don't know what or when
it happened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797887
Title:
Lubuntu doesn't honor various settings
To manage
This happened on lubuntu dated, 10/14/18, 12:33 AM. Not sure if there
has been an update since then, and this only happened on this dated ISO.
All the previous ISO's were fine.
I installed exactly as I always have, following Calamares lead all the way to
the end.
I'll try again soon, and let you
I noticed that after installing, my home/.config had some files with
ROOT access only. Once changed back to my user and group, then the
desktop wallpaper settings were honored again.
The PCManFM settings keep getting reset. If I change ".config/pcmanfm-
qt/default/settings.conf" to reflect what
Public bug reported:
Lubuntu 18.10 Cosmic
LXQT 0.13.3
Various settings are not honered on reboot:
Desktop wallpaper settings, PCManFM sort, size settings, set qterminal default.
All the above settings get reset to factory settings after reboot
** Affects: ubuntu
Importance: Undecided
** Attachment added: "bionic-cosmic-panels.pdf"
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1791849/+attachment/5187627/+files/bionic-cosmic-panels.pdf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
System:Host: cos Kernel: 4.17.0-9-generic x86_64 bits: 64 Desktop: Xfce
4.13.2
Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
** Summary changed:
- xfce-panel missing "Background Alpha"
+ xfce4-panel missing "Background Alpha"
--
You received this bug notification because you are
Public bug reported:
The Background-Alpha is missing in Cosmic Xubuntu
** Affects: xfce4-panel (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "cosmic-panel"
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1791849/+attachment/5187323/+files/cosmic-panel.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "bionic panel"
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1791849/+attachment/5187322/+files/bionic-panel.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It woks fine on Xubuntu on xfce-panel. I haven't tried lxqt on Xubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788068
Title:
lubuntu cosmic lxqt-panel world clock truncated in 12-hr format
Manjaro-lxqt:
Name: lxqt-panel
Version : 0.13.0-2
Description : The LXQt desktop panel
Architecture: x86_64
The above panel works correctly with getty-auto-login
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Its not a really strange case. Its used on many distros, and documented many
times as well.
The point is why it doesn't work on Lubuntu, and only Lubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's how you can reproduce it:
(1) Remove or disable sddm
(2) Install getty autologin: https://wiki.archlinux.org/index.php/getty
(3) Reboot.
Here's my files to allow getty-auto-login:
===.xinitrc:===
[[ -f ~/.Xresources ]] && xrdb -merge -I$HOME ~/.Xresources
exec startlxqt
Notice the "clipped" "9" on my attachment.
** Attachment added: "clipped-work-clock"
https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1788068/+attachment/5178385/+files/clipped-world-clock.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Walter, that's because you "pad" with a zeo. Try without padding.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788068
Title:
lubuntu cosmic lxqt-panel world clock area
To manage notifications
Public bug reported:
Configuring world-clock to 12-hr format, the front gigit gets clipped off.
There is not enough area to accurately display full digits correctly.
Especially double digits, as in 12:12PM
** Affects: lxqt-panel (Ubuntu)
Importance: Undecided
Status: New
--
You
Fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785450
Title:
lubuntu Job swap.target failed with result 'dependency'
To manage notifications about this bug go to:
I've went through every thing. Removed everything I normally removed,
installed chrome, removed sddm and installed systemd autologin.
No SWAP errors whatsoever. This was installed from today's ISO. There
was about 80% needed from zsync.
So either it was fixed from a previous updated file or
It occured to me that I do house cleaning before I check the swap error.
Today I decided to instead boot from lubuntu's grub menu then check.
Here's the results:
vmc@vmc-pc:~$ journalctl|egrep "timed|swap"
Aug 11 07:38:33 vmc-pc kernel: zswap: loaded using pool lzo/zbud
Aug 11 07:38
I found out that if I slow down the boot process by using ctrl-s, swap
appears to pass:
Aug 07 06:13:02 vmc-pc kernel: zswap: loaded using pool lzo/zbud
Aug 07 06:13:07 vmc-pc kernel: Adding 2047996k swap on /dev/sda5. Priority:-2
extents:1 across:2047996k FS
Aug 07 06:13:07 vmc-pc systemd[1
Simon,
I installed using bootable USB flash drive. I defaulted all until it came to
install option. I choose Manually, then as always, I selected sda7, ext4,
format.
After installed it used my swap partition, sda5.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
System:Host: vmc-pc Kernel: 4.17.0-6-generic x86_64 bits: 64 Desktop: LXQt
0.13.0
Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine: Type: Desktop System: HP-Pavilion product: AY652AA-ABA s5310y v: N/A
serial:
Mobo: PEGATRON model: Narra6 v: 6.01 serial: BIOS
I found also the following journal messages relating to SWAP:
dev-disk-by\x2duuid-39f23cab\x2d3322\x2d438e\x2dbecd\x2d56e468346656.device:
Job
dev-disk-by\x2duuid-39f23cab\x2d3322\x2d438e\x2dbecd\x2d56e468346656.device/start
timed out.
** Package changed: ubuntu => swapspace (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785450
Title:
lubuntu Job swap.target failed with result 'dependency'
To manage notifications about
Lubuntu 18.10
LXQt: 0.13.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785450
Title:
lubuntu Job swap.target failed with result 'dependency'
To manage notifications about this bug go to:
Public bug reported:
>From each boot I get the following messages:
systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
systemd[1]:
dev-disk-by\x2duuid-39f23cab\x2d3322\x2d438e\x2dbecd\x2d56e468346656.swap: Job
** Summary changed:
- lubuntu bash preferences too big
+ lubuntu qterminal preferences too big
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784198
Title:
lubuntu qterminal preferences too big
It should be qterminal 0.9.0 and NOT bash
** Package changed: bash (Ubuntu) => qterminal (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784198
Title:
lubuntu bash preferences too big
To
Public bug reported:
lubuntu 18.10
LXQt version 0.13.0
When I open bash and select Preferences. The Terminal Settings is much
taller than the screen size. I can't see the OK-Cancel-Apply buttons. I
need to use the mouse from the top of screen and reduce the size
manually.
I expect the settings
** Attachment added: "settings.png"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1784198/+attachment/5169115/+files/settings.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784198
crash attachment
** Attachment added: "_usr_bin_falkon.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/falkon/+bug/1783639/+attachment/5167790/+files/_usr_bin_falkon.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
:1624:0725/114310.118812:ERROR:nss_ocsp.cc(591)] No URLRequestContext for
NSS HTTP handler. host: crl4.digicert.com
Falkon: Crashed :( Saving backtrace in /home/vmc/.config/falkon/crashlog ...
Aborted (core dumped)
There is no ".config/falkon/crashlog" created.
$ falkon -o
Falkon: Runn
No errors using ISO dated: Wed 25 Jul 2018 06:39:14 AM PDT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783024
Title:
Lubuntu Cosmic install fails due to hardcoded paths which are
incorrect
To
Success!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783024
Title:
Lubuntu Cosmic install fails due to hardcoded paths which are
incorrect
To manage notifications about this bug go to:
Just to add, my error is on MBR, and lubuntu is actually installed. The
error occurs right at the end, apparently cleaning up after itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783024
Failed using:
lubuntu-cosmic-desktop-amd64.iso
DATED Mon 23 Jul 2018 05:02:25 PM PDT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783024
Title:
Lubuntu Cosmic install fails due to hardcoded
It failed again using:
lubuntu-cosmic-desktop-amd64.iso DATED Mon 23 Jul 2018 04:14:33 AM PDT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783024
Title:
Lubuntu Cosmic install fails due to
I tried today, using:
lubuntu-cosmic-desktop-amd64.iso DATED: Mon 23 Jul 2018 04:14:33
and it still fails the same way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783024
Title:
Lubuntu Cosmic
Wow, that was quick. Not even confirmed. Thanks Simon!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783024
Title:
Lubuntu Cosmic install fails due to hardcoded paths which are
incorrect
To
I restarted the install going through terminal and recording activity:
lubuntu@lubuntu:~$ sudo calamares
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
00:01:36 [2]: WARNING: Required settings.conf key dont-chroot is missing.
00:01:37 [2]: WARNING:
Public bug reported:
Right near the end of installation, the attached message below appeared.
Installed from USB (as always), using:
lubuntu-cosmic-desktop-amd64.iso, dated Sat 21 Jul 2018 05:37:17 PM PDT
** Affects: ubuntu
Importance: Undecided
Status: New
** Attachment added:
1 - 100 of 349 matches
Mail list logo
