*** This bug is a duplicate of bug 1801408 ***
https://bugs.launchpad.net/bugs/1801408
** This bug has been marked a duplicate of bug 1801408
disco installer crashed with usr-merge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
*** This bug is a duplicate of bug 1801408 ***
https://bugs.launchpad.net/bugs/1801408
** This bug has been marked a duplicate of bug 1801603
[19.04] Installation fails with /plugininstall.py: FileNotFoundError: [Errno
2] No such file or directory: '/target/sbin/start-stop-daemon'
** This
*** This bug is a duplicate of bug 1801408 ***
https://bugs.launchpad.net/bugs/1801408
** This bug has been marked a duplicate of bug 1801408
disco installer crashed with usr-merge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
*** This bug is a duplicate of bug 1801408 ***
https://bugs.launchpad.net/bugs/1801408
** This bug is no longer a duplicate of bug 1801603
[19.04] Installation fails with /plugininstall.py: FileNotFoundError: [Errno
2] No such file or directory: '/target/sbin/start-stop-daemon'
** This bug
*** This bug is a duplicate of bug 1801408 ***
https://bugs.launchpad.net/bugs/1801408
** This bug is no longer a duplicate of bug 1801603
[19.04] Installation fails with /plugininstall.py: FileNotFoundError: [Errno
2] No such file or directory: '/target/sbin/start-stop-daemon'
** This bug
*** This bug is a duplicate of bug 1801408 ***
https://bugs.launchpad.net/bugs/1801408
** This bug is no longer a duplicate of bug 1801603
[19.04] Installation fails with /plugininstall.py: FileNotFoundError: [Errno
2] No such file or directory: '/target/sbin/start-stop-daemon'
** This bug
*** This bug is a duplicate of bug 1801603 ***
https://bugs.launchpad.net/bugs/1801603
** This bug has been marked a duplicate of bug 1801603
19.04 Installer crashed in Virtualbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1801603 ***
https://bugs.launchpad.net/bugs/1801603
** This bug has been marked a duplicate of bug 1801603
19.04 Installer crashed in Virtualbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1801603 ***
https://bugs.launchpad.net/bugs/1801603
** This bug has been marked a duplicate of bug 1801603
19.04 Installer crashed in Virtualbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1801603 ***
https://bugs.launchpad.net/bugs/1801603
** This bug has been marked a duplicate of bug 1801603
19.04 Installer crashed in Virtualbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1801603 ***
https://bugs.launchpad.net/bugs/1801603
** This bug has been marked a duplicate of bug 1801603
19.04 Installer crashed in Virtualbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
List of extensions installed on the system.
** Attachment added: "extensions.list"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+attachment/5206748/+files/extensions.list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
journal of the session
** Attachment added: "journal.log.gz"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+attachment/5206749/+files/journal.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
Quite often all the extension (excepted the dock) are disabled after
unlocking the screen.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportV
Public bug reported:
I have to unlock the screen twice to unlock the screen.
On 1rst attempt I have a completely aubergine screen without any widget at all
(no label, password field, buttons, ...)
Then I have to lock the screen and unlock it again to display the usual screen
and be able to log i
journal from this session
** Attachment added: "journal.log.gz"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800475/+attachment/5206743/+files/journal.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Changed in: ubiquity (Ubuntu)
Assignee: kero Adel (kero3adel) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766945
Title:
(EFI on top of legacy install) choosing
*** This bug is a duplicate of bug 1799097 ***
https://bugs.launchpad.net/bugs/1799097
** This bug has been marked a duplicate of bug 1799097
Install selected time zone city (Seattle) hit next hit back hit next then
crash
--
You received this bug notification because you are a member of
I don't think it's related to auto-login. I had this problem last week
but it is not reproducible after a reboot. I attached the journal from
last week.
I have the following extensions enabled:
- Alternate Tab
- Better volume indicator
- Media player indicator
- No topleft hot corner
- Sound input
*** This bug is a duplicate of bug 1799097 ***
https://bugs.launchpad.net/bugs/1799097
** This bug has been marked a duplicate of bug 1799097
Install selected time zone city (Seattle) hit next hit back hit next then
crash
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1799097 ***
https://bugs.launchpad.net/bugs/1799097
** This bug has been marked a duplicate of bug 1799097
Install selected time zone city (Seattle) hit next hit back hit next then
crash
--
You received this bug notification because you are a member of
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799097
Title:
Install selected time zone city (Seattle) hit next hit back hit next
Thanks for your report. Xorg packages installed from a PPA are blocking
the upgrade. Please revert to version of the official Ubuntu repository
and try again. I'm closing this report because it is not a bug with
Ubuntu.
Do not hesitate to submit any bug you may find.
** Changed in: ubuntu-release
debug.log in debug mode.
** Attachment added: "debug"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799097/+attachment/5204021/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
*** This bug is a duplicate of bug 1799097 ***
https://bugs.launchpad.net/bugs/1799097
** This bug has been marked a duplicate of bug 1799097
Install selected time zone city (Seattle) hit next hit back hit next then
crash
--
You received this bug notification because you are a member of
Thanks for your report.
Confirmed on Cosmic (release) by going back and forth between the
Timezone and the User setup pages.
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
** Tags added: rls-dd-incoming
--
You
Public bug reported:
Crashed while going back and forth between Timezone and User pages
ProblemType: Bug
DistroRelease: Ubuntu 18.10
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: 2.20.10-0ubuntu13
Architec
Thanks for your report.
Xorg packages from the oibaf PPA are blocking the upgrade. Could you
please revert to versions from the official Ubuntu repository and try
again.
Thanks.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687637
Title:
Kubuntu installer crashes when checking format box
To manage notif
*** This bug is a duplicate of bug 1687637 ***
https://bugs.launchpad.net/bugs/1687637
** This bug has been marked a duplicate of bug 1687637
Kubuntu installer crashes when checking format box
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Description changed:
- Test Case:
+ Test Case 1:
+ With e2fsprogs 1.44.4-2:
+
+ Download this file system image:
+
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz
+
+ Run the following commands:
+
+ bunzip2 vda1b.qcow2.bz
+ qemu-img
** Package changed: ubiquity (Ubuntu) => e2fsprogs (Ubuntu)
** Changed in: e2fsprogs (Ubuntu)
Importance: High => Critical
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Possibly related issues:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1783757
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Apparently it's clearly reproducible with Cosmic alongside Cosmic.
Has anyone been able to reproduce with Cosmic alongside something else
than Cosmic such as an earlier release, another distribution or
operating system?
--
You received this bug notification because you are a member of Ubuntu
Bug
@APoliihron, when it happened to you what was the original operating
system that you resized? Was it cosmic on cosmic or something else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798562
Title:
@Apolihron, yes but depending on the corruption the system can go into
initramfs if it completely fails to boot (your screenshot), it may boot
but the FS will be RO, or it may recover transparently and all sort of
other side effects are possible.
--
You received this bug notification because you
Public bug reported:
Test Case:
1. Perform a first installation of Ubuntu
2. Reboot into the freshly installed system and verify everything works as
expected
3. Do a second installation and select "Install alonogside". Keep the size
proposed by the installer and proceed to the end of installatio
ls -altrR /boot/efi/
/boot/efi/:
total 12
drwx-- 3 root root 4096 Dec 31 1969 .
drwx-- 4 root root 4096 Oct 16 13:30 EFI
drwxr-xr-x 4 root root 4096 Oct 17 12:51 ..
/boot/efi/EFI:
total 16
drwx-- 3 root root 4096 Dec 31 1969 ..
drwx-- 2 root root 4096 Oct 16 13:30 BOOT
drwx-
This is the output on the Inspiron 11 with secure boot off
BootCurrent: 0013
Timeout: 0 seconds
BootOrder: ,0010,0011,0012,0013,0014,0015,0016,0017,0018,0019,001A,001B
Boot* ubuntu
HD(1,GPT,efb1a75e-ea53-471c-a21d-17bad475f131,0x800,0x10)/File(\EFI\ubuntu\shimx64.efi)
Boot0010
@Pau, could you boot your system (with secure boot disable), then from a
terminal run the command in command #3:
sudo efibootmgr -v
and paste the output.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Also affects: mokutil (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mokutil (Ubuntu)
Importance: Undecided => Critical
** Changed in: mokutil (Ubuntu)
Status: New => Confirmed
** Tags added: rls-dd-incoming
--
You received this bug notification because you ar
** Description changed:
Test Case:
1. In UEFI mode perform a first installation of Ubuntu with the following
partitioning scheme (adjust the size of the partition to your disk)
sda1 8G swap
sda2 10G /boot
sda3 100G /
sda4 100G /home
sda5 20G ESP
Proceed with the installation an
Public bug reported:
Test Case:
1. In UEFI mode perform a first installation of Ubuntu with the following
partitioning scheme (adjust the size of the partition to your disk)
sda1 8G swap
sda2 10G /boot
sda3 100G /
sda4 100G /home
sda5 20G ESP
Proceed with the installation and reboot
2. Do a sec
I cannot reproduce on any other machine, setting to incomplete for now.
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
installer logs from the affected system
** Attachment removed: "Casper.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1798171/+attachment/5201867/+files/Casper.txt
** Attachment removed: "UbiquitySyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1798171/+at
Public bug reported:
Cosmic desktop installation on UEFI system with secure boot enabled,
third party drivers checked, installation on entire disk.
On boot the system fails with:
Failed to open \EFI\BOOT\mmx64.efi - Not Found
Failed to load image \EFI\BOOT\mmx64.efi - Not Found
Failed to start M
** Attachment added: "DSC_0954.JPG"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1798171/+attachment/5201872/+files/DSC_0954.JPG
** Description changed:
- Cosmic desktop installation on UEFI system with secure boot enabled and
- third party drivers checked. On boot the system fails
Thanks for your report.
You have Xorg packages from the oibaf PPA installed on your system.
Please revert to the version from the official Ubuntu repository and try
the upgrade again. I'm closing this report because it is not a bug with
Ubuntu.
Do not hesitate to submit any bug you may find.
**
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725384
Title:
On touch screens, the apps icon in the dock does not open when touched
To manage notifications about this
@Dimitri, what do you mean by "Clearing all the boot entries" ? I didn't
do anything but installing this machine with ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796260
Title:
UEFI instal
** Changed in: plymouth (Ubuntu Cosmic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV
Reopening per comment #14
** Changed in: plymouth (Ubuntu Cosmic)
Status: Fix Released => Triaged
** Changed in: plymouth (Ubuntu Cosmic)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
"sudo gedit" works fine and the screen reader reads the UI and what I
type.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797861
Title:
Screen reader doesn't read installer's GUI during a live sess
I verified in Bionic and this is a new problem in Cosmic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797861
Title:
Screen reader doesn't read installer's GUI during a live session
installation
Public bug reported:
cosmic desktop rc
There are the following issues with g-i-s and a11y:
- General: Pages titles are not read
- General: Description of the pages is not read
- Help Improve Ubuntu: User cannot navigate with the keyboard to the Yes/No
radio button
- Software: Left/Right navigati
** Summary changed:
- Screen reader doesn't read installer's GUI
+ Screen reader doesn't read installer's GUI during a live session installation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797861
Public bug reported:
Ubuntu Cosmic Desktop RC
During a live session installation, the screen reader is activated and
working (for example it's reading this message while I'm typing) but it
doesn't read Ubiquity's windows.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity 18.10.9
Pro
Public bug reported:
Ubuntu Desktop
There is no progress dots anymore during boot. Instead there is a purple
screen for a while, then a flash, the Ubuntu logo with fixed white dots
and finally the login screen.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: plymouth 0.9.3-1ubuntu10
ProcVe
** Description changed:
ubuntu cosmic desktop 20180925
After installation gdm fails to start and there is only a black screen
with a blinking cursor on the top left of the screen.
- gdm3 can be started manually from a tty
+ gdm3 can be started manually from a tty.
+ Switching to anothe
Thanks for your report.
You have xorg packages from the padoka PPA which are blocking the
upgrade. Please revert to packages from the official Ubuntu repository
and try the upgrade again. I'm closing this report because it is not a
bug with Ubuntu.
Do no hesitate to submit any bug you may find.
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797377
Title:
In tablet mode, OSK is not displayed in the WiFi network auth dialog
To manage notifications about this b
** Description changed:
Test Case:
On a laptop with a touchscreen, login and tap the "Show Applications" button
at the bottom of the dock to open the list of applications.
- Actual result
- The list of applications opens and closes immediately
+ Actual result
+ The list of applications op
Public bug reported:
Test Case:
On a laptop with a touchscreen, login and tap the "Show Applications" button at
the bottom of the dock to open the list of applications.
Actual result
The list of applications opens and closes immediately
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gno
Public bug reported:
Test Case:
1. On a 2 in 1 in tablet mode, launch the installer and proceed to the user
setup step (Who are you)
2. With the OSK, enter the username, login, hostname and password then proceed
zith the rest of the installation
Actual result
The OSK hides when the password fie
Public bug reported:
Test Case:
1. On a 2 in 1 laptop, use it in table mode
2. Start the installer and proceed to the WiFi step
3. Connect to an authenticated network
4. Type the password and authenticate
Actual result
The OSK is not displayed and the user cannot enter his password
ProblemType:
This issue still exists on Cosmic Desktop 20181011 with casper 1.397. I
reproduced it on bare metal in legacy mode with an installation from the
live session.
** Changed in: casper (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of
output of efibootmgr -v:
BootCurrent: 0017
Timeout: 0 seconds
BootOrder: 0002,0003,0004,0005,0006,0017,0018
Boot* ubuntu
HD(5,MBR,0x39a7181f,0x0,0x0)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* ubuntu
HD(2,MBR,0x39a7181f,0xe6717fe,0xd8b6002)/HD(1,MBR,0x0,0xe671800,0x100800)/File(\E
** Description changed:
Ubuntu Cosmic Desktop 20181005
Test Case:
1. Boot in BIOS mode and install on entire disk
=> Verify that the system boots
2. Boot in UEFI and perform a new installation alongside previous one
=> Verify that you can boot to the new system
Actual result
-
On this machine there is a boot setting to select the boot mode UEFI or
Legacy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796260
Title:
UEFI installation alongside BIOS installation: System fail
This is on bare metal, DELL Inspiron 13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796260
Title:
UEFI installation alongside BIOS installation: System fails to boot
with cannot find a valid bo
- I see this behaviour on bare metal in BIOS and UEFI mode when installing from
the live session.
- when pressing alt-arrow 5 times, I see the purple screen with the Ubuntu logo
and the message "Please remove the installation medium, then press ENTER:"
--
You received this bug notification beca
This file is in /pool/restricted/b/bcmwl/bcmwl-kernel-
source_6.30.223.271+bdcom-0ubuntu4_amd64.deb
Is it not installed when you select "Restricted Add-ons"?
What is the output of "ubuntu-drivers list" on this machine?
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Incomplete
--
You
** Description changed:
Test Case:
1. Boot desktop image to the live session and wait.
+
+
+ https://errors.ubuntu.com/problem/70a7581dd245188e74367f2c31a505b664b972c9
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: xdg-desktop-portal 1.0.2-1
ProcVersionSignature: Ubuntu 4
*** This bug is a duplicate of bug 1796383 ***
https://bugs.launchpad.net/bugs/1796383
** This bug has been marked a duplicate of bug 1796383
xdg-desktop-portal crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796383
Title:
xdg-desktop-portal crashed with SIGSEGV in
export_portal_implementation -> on_bus_ac
Yes, this is known, Ubuntu Desktop requires at least 1.5G of memory to
be installed in a VM. There used to be a resource checking page in the
installer that has been removed a while ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
how much memory did you allocate to the VM?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796037
Title:
[QEMU] When loading partman step, GNOME Shell vanishes, no more
decoration and installer UI
** Description changed:
Ubuntu Cos;ic Desktop 20191005
Test Case:
1. Boot in BIOS mode and install on entire disk
=> Verify that the system boots
2. Boot in UEFI and perform a new installation alongside previous one
=> Verify that you can boot to the new system
Actual result
** Description changed:
Ubuntu Cos;ic Desktop 20191005
Test Case:
1. Boot in BIOS mode and install on entire disk
=> Verify that the system boots
2. Boot in UEFI and perform a new installation alongside previous one
=> Verify that you can boot to the new system
Actual result
Public bug reported:
Ubuntu Cos;ic Desktop 20191005
Test Case:
1. Boot in BIOS mode and install on entire disk
=> Verify that the system boots
2. Boot in UEFI and perform a new installation alongside previous one
=> Verify that you can boot to the new system
Actual result
It fails immediately on
apparently so
/usr/sbin/squid (enforce)1934 ?Ss 0:00 /usr/sbin/squid -sYC
/usr/sbin/squid (enforce) 32043 ?S 0:04 \_ (squid-1) --kid
squid-1 -sYC
/usr/sbin/squid (enforce) 32062 ?S 0:00 \_
(logfile-daemon) /var/log/squid/access.log
** Description changed:
Cosmic Desktop 20181003
After installation the message to remove the installation media and
reboot is not always displayed. Instead there is a black page with a
blinking cursor on the top left. The message can be displayed by
pressing alt-right_arrow 5 times.
+
** Description changed:
Cosmic Desktop 20181003
After installation the message to remove the installation media and
reboot is not always displayed. Instead there is a black page with a
blinking cursor on the top left. The message can be displayed by
- pressing alt-right_arrow 4 times.
+
Here is the journal with records from September 23rd. The crash happened
again yesterday.
** Attachment added: "journal.log.gz"
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1794553/+attachment/5197120/+files/journal.log.gz
--
You received this bug notification because you are a membe
I'm also running squid-deb-proxy but it's the main squid that crashed.
Here is the cache.log from the time of the crash. The access file for
the same time is empty (I don't use squid on this machine at the moment)
** Attachment added: "cache.log.1"
https://bugs.launchpad.net/ubuntu/+source/squ
Thanks for your report.
According to the stack trace, the Ubiquity crash is a consequence of the
NM crash because the service disappeared from the bus.
Oct 3 18:38:06 ubuntu ubiquity[3468]: Exception in GTK frontend (invoking
crash handler):
Oct 3 18:38:06 ubuntu ubiquity[3468]: Traceback (mos
Public bug reported:
Cosmic Desktop 20181003
After installation the message to remove the installation media and
reboot is not always displayed. Instead there is a black page with a
blinking cursor on the top left. The message can be displayed by
pressing alt-right_arrow 4 times.
ProblemType: Bu
** Description changed:
- nothing
+ errors.u.c
+ https://errors.ubuntu.com/problem/cfe6699cf6c2996d3524baf4cd65b73a4c35dc41
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: cups-pk-helper 0.2.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.
** Changed in: cups-pk-helper (Ubuntu)
Importance: Medium => High
** Tags added: rls-cc-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290533
Title:
cups-pk-helper-mechanism crashed wit
** Changed in: grub-installer (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/1795806
Title:
1
To manage notifications about this bug go to:
https://bugs.launch
If the policy is to wait for the release to be stable to update hplip, it means
that hplip will always be one release off and won't work on the latest release
until the changes are SRUed.
Besides SRUing large set of changes is huge and much more work than releasing a
new version to the developme
*** This bug is a duplicate of bug 1759388 ***
https://bugs.launchpad.net/bugs/1759388
** This bug has been marked a duplicate of bug 1759388
Unable to install to a luks device that is itself partitioned
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Test Case
1. Boot to a live session, start an installation and proceed to the
partitioning step.
2. Select LVM (no encryption) and continue
Result
This crash
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity 18.10.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-gener
Still happening in Cosmic 20181002
** Information type changed from Private to Public
** Changed in: ubiquity (Ubuntu)
Importance: Medium => Critical
** Tags added: rls-cc-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1794292 ***
https://bugs.launchpad.net/bugs/1794292
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769241
Tit
** Summary changed:
- Xorg assert failure: Xorg: ../../../../dix/privates.c:384:
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
+ Cosmic Desktop fails to boot in vbox: Xorg assert failure: Xorg:
../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion
`!global_ke
** Changed in: xorg (Ubuntu Cosmic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794280
Title:
gdm doesn't start on a fresh installation of Cosmic Desktop
To
** Description changed:
- On a system with hardware requiring proprietary drivers (eg nVidia graphics
card), when the user selects to install restricted add-on and proprietary
driver, ubuntu-drivers runs immediately the the installer exists the prepare
step.
- Doing so it installs the drivers o
Public bug reported:
lubuntu cosmic i386 20180927
Default installation in French from the live session, the installer
crashes with:
2018-09-27 - 18:42:22 [6]: Python Error:
File "/usr/lib/i386-linux-gnu/calamares/modules/automirror/main.py", line 124,
in run
country = getcountry()
** Tags added: rls-cc-incoming
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794280
Title:
gdm doesn't start on a fresh installation
1001 - 1100 of 33249 matches
Mail list logo
