Pressing any key quickly enough starts the boot process successfully.
In win10, PC Health Check now qualifies the OS as ok to upgrade to
win11.
Please close this case.
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
I created a new VM; installed win10 with TPM2.0, secure boot, and SATA
CDROM enabled from the start.
I got the same boot error.
Any suggestions?
P.S. The ISO file was downloaded from Microsoft and verified for SHA
sum.
--
You received this bug notification because you are a member of Ubuntu
Package ovmf is version 2022.02-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971509
Title:
qemu/kvm win10 client cannot upgrade to win11
To manage notifications about this bug go to:
win10 boot error with SATA CDROM 1 boot option selected
** Attachment added: "win10 boot error with SATA CDROM 1 boot option selected"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5590113/+files/Screenshot%20from%202022-05-16%2013-47-57.png
** Changed in: qemu
Hi Lena,
Package ovmf is already installed. It was probably installed by virt-
manager.
You will find attached 2 screenshots of ovmf and OVMF folders in the
system.
I added SATA CDROM 1 to the boot options as suggested.
I still get the win10 boot error (see attached).
Please bear in mind
OVMF system folder
** Attachment added: "OVMF system folder"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5590112/+files/Screenshot%20from%202022-05-16%2013-27-04.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>provide a more complete description of the problem
What is missing from the description of the problem?
You have the precise steps required to reproduce this problem. It
occurs on every attempt.
Whether "bug" or "configuration", the product does not work.
Please provide a fix.
** Changed
The "boot error" is reproducible.
1. start Virtual Machine Manager
2. click on Open
3. this opens a window called win10 on QEMU/KVM
4. in this window (3.), click on Power on the virtual machine (black triangle
pointing right)
5. you get the "boot error" in window (3.)
As for executing *.efi,
To clarify the previous comment:
First, TPM settings were added to the windows VM. They worked fine.
Second, Secure Boot code was added to the xml. It caused the windows
boot error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I implemented your 2 code additions separately.
First, TPM code was added to the xml. It worked fine.
Second, Secure Boot was added to the xml. It caused the windows boot
error.
Hope this help.
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
--
You received this bug
Here is the xml screenshot.
** Attachment added: "xml screenshot"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5587940/+files/Screenshot%20from%202022-05-09%2011-55-58.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I get the following Windows boot error.
Note the extra line in the section that cannot be deleted.
** Attachment added: "windows boot error"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5587939/+files/Screenshot%20from%202022-05-09%2011-46-36.png
--
You
** Attachment added: "screen7: NIC"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5587034/+files/Screenshot%20from%202022-05-05%2011-37-03.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As best as I can recall, you only need to input CPU (8), RAM (8192 MiB),
and disk (50 GiB).
The windows ISO file is read as is.
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "screen5: SATA disk 1"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5587032/+files/Screenshot%20from%202022-05-05%2011-35-42.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "screen6: SATA CDROM 1"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5587033/+files/Screenshot%20from%202022-05-05%2011-36-56.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "screen4: boot options"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5587030/+files/Screenshot%20from%202022-05-05%2011-35-33.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "screen3: memory"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5587029/+files/Screenshot%20from%202022-05-05%2011-35-25.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "screen2: CPUs"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5587028/+files/Screenshot%20from%202022-05-05%2011-35-15.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Setup is done by clicking on "Create a new virtual machine" in Virtual
Machine Manager and filling in the requested info.
You will find attached 7 screenshots of configuration details.
** Attachment added: "screen1: overview"
Here is windows health check screen 2.
** Attachment added: "windows health check screen2"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1971509/+attachment/5586425/+files/Screenshot%20from%202022-05-03%2018-31-19.png
--
You received this bug notification because you are a member of
Public bug reported:
Windows health check claims the following shortcomings:
- PC does not support secure boot
- PC does not support TPM 2.0
- CPU has 1 core
The PC is a brand new Dell Optiplex 7090.
8 of 16 CPU cores are allocated to the win10 VM.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Public bug reported:
***
*** Please change the package to the appropriate one
***
In Ubuntu 22.04, the "Show Applications" icon at the bottom of the
launcher gives the apps in undesired order.
This needs to be sorted in ascending order.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package:
Public bug reported:
***
*** Please change package to the appropriate one
***
In Ubuntu 22.04, the "Show Applications" icon at the bottom of the
launcher gives the apps in undesired order.
This needs to be sorted in ascending order.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gedit
>What do you mean exactly by "Sandisk claims that both drives are
defective"
Based on my answers to a battery of their questions, Sandisk concluded
both flash drives are defective and have agreed to replace them.
>if the drives are truly defective, do we agree there is no bug here,
and the popup
Sandisk claims that both drives are defective.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953523
Title:
KDE problem mounting Sandisk USB
To manage notifications about this bug go to:
During the course of further Kubuntu 21.10 testing today to answer
Sandisk support questions, the following new behaviours appeared:
- the Sandisk Extreme Pro 256 GB USB stick no longer triggers the error popup
window
- the mount popup window no longer appears
- the dolphin file manager does
You will find attached the log of the requested commands.
If the USB device's failure was so imminent, why is it working fine
daily with rsync on Ubuntu 20.04 since it was purchased a few weeks ago?
** Attachment added: "log of requested commands"
Public bug reported:
A Dell Optiplex 7060 with Kubuntu 21.10 has problems mounting a Sandisk
Extreme Pro USB 256GB stick.
See attached for popup error message.
However, when you run the following, everything is ok.
xxx@yyy:~$ sudo smartctl --health /dev/sda1
smartctl 7.2 2020-12-30 r5155
Public bug reported:
***
*** Please change package from gedit to the correct one
***
Ubuntu Software 3.38.1 cannot update snapd 2.49.2
(see screenshot)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gedit 3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
During a run of Software Updater, got this error.
Ubuntu 20.04 fully patched once daily.
Linux kernel updated from 5.4 to 5.8 in this run of Software Updater.
VirtualBox was NOT a product being updated according to the list in
Software Updater.
When asked to restart, the system took abnormally
There is no "Yahoo Finance" source in 5.0.8
No "Yahoo" either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729709
Title:
Quote updates fail
To manage notifications about this bug go to:
Best viewed in Image Viewer 3.34.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864539
Title:
screenshot tool inserts corrupt border area
To manage notifications about this bug go to:
Public bug reported:
Screenshot tool inserts corrupt border area.
This also applies to Ubuntu 20.04 daily build.
See attached screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-screenshot 3.33.90-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux
You will find attached the journalctl log for the corrupted session.
It has been anonymized.
** Attachment added: "anonymized journalctl log"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1850001/+attachment/5300891/+files/jrnl_log_anonymized
** Changed in: nautilus (Ubuntu)
>So the hang issue went away
Yes, the reboot wiped everything clean.
>Can you still add the journalctl log from the session where you had the issue
There is a lot of private information in the log, computer name, file names,
paths, that should not be publicly posted.
There are also a lot of
>Do you mean it hangs on a specific file
No, any file.
>give details on the file/location
~/Downloads
I had to end the nautilus process in System Monitor.
The power down button in the upper right corner of the desktop did not
work. No response at all.
I had to issue the reboot command from
Public bug reported:
Nautilus hangs when deleting a file. The file does not get deleted.
This applies to the DELETE key, the SHIFT+DELETE keys, and the RIGHT-
CLICK attempt at deleting.
This is reproducible in this boot session.
This has never happened since the install of the OS.
Public bug reported:
Search for ufraw in synaptic points to darktable.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ufraw 0.22-4
ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
On a prior OS (16.04 or 18.04, cannot remember which) the following
rsync -v -a -r -W -p -o -g -t --delete --stats ~/Pictures /media/$USER
/USB-128GB-1/ >bkp_log
would only send differences on subsequent runs with a fat32 USB key.
Your test above seems to indicate that subsequent runs on 19.04
I have run 2 test scenarios.
A trivial folder containing 3 text files as source.
A real world case of ~/ as source.
Both cases work as expected on an LUKS encrypted ext4 USB key.
I will do some more testing on fat32 and report back.
--
You received this bug notification because you are a
I frequently rebuild USB keys.
If memory serves me correctly, the USB device was LUKS encrypted ext4.
** Changed in: rsync (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The following
rsync -v -a -r -W -p -o -g -t --delete --stats
--exclude=".*"
--exclude="/snap*"
~
/media/$USER/USB-128GB-3/
>bkp_log
copies all contents of home folder each time it is run.
The expectation is that only changed files will be copied and replaced
on the target.
This is
Public bug reported:
Repeated runs of rsync from PC to USB key send everything, not just the
changes.
This is reproducible.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: rsync 3.1.3-6
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
When I log in to my (regular user) account early morning, the Switch
User menu item is not present.
When I log out late in the evening, the Switch User menu item is
present.
This is reproducible day in, day out.
This is the case even on days when there are no system updates or
upgrades at all.
*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790
The following 3 packages get installed automatically by the updater
process:
gnome-control-center
gnome-control-center-data
gnome-control-center-faces
--
You received this bug notification because you
*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790
What about the 3 packages for
gnome-control-center
gnome-control-center-data
gnome-control-center-faces
Do they also need to be locked (see screenshot)?
** Attachment added: "lock all 5 ?"
After today's system update and upgrade, the fix from comment #8 has
disappeared.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825544
Title:
Switch User menu item gone after upgrade to Ubuntu
For info only:
There are ripple effects from this bug. See Bug #1825544 for a user
switching problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu login screen never
THE GOOD NEWS:
edit /etc/gdm3/custom.conf and uncomment the line:
#WaylandEnable=false
Then reboot. This solves the problem.
THE BAD NEWS:
With WaylandEnable=false active in /etc/gdm3/custom.conf, the system
monitor does not launch.
--
You received this bug notification because you are
With WaylandEnable=false active in /etc/gdm3/custom.conf, the system
monitor does not launch.
Is there a workaround for that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu
*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790
from Bug #1798790:
>The specific steps or actions you took that caused you to encounter the
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
installed.
I have never installed proprietary
>Daniel van Vugt (vanvugt) : Try this as a workaround: edit
/etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false Then
reboot.
Yes, this works. Is this edit of custom.conf considered stable enough
for serious work, or testing only?
--
You received this bug notification because
Note that the updates and upgrades on the test machine are not current.
Obviously.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831514
Title:
Ubuntu 19.04 system update causes boot failure
To
Prior to submitting this bug, this discussion started:
https://answers.launchpad.net/ubuntu/+question/681215
There may be some details that might help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>Try to force reboot/power down earlier during the boot
Not possible.
This is the boot process:
1. push power button
2. type in decryption password
3. hit enter
4. you immediately receive the Ubuntu splash screen
5. more and more (but not all) red dots appear
6. system hangs at 3 or 4 red dots
>If you have a failed boot then the next start should automatically open
the grub menu
The next boot hangs on the Ubuntu splash screen. This is reproducible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>Do you mean that after applying those updates you don't get to the login
>screen anymore?
correct
>Can you reproduce after a new install and upgrading again?
The boot failure occurs on step 5. This is reproducible.
>Can you boot to a command line using the recovery option
I tried to boot
The system update is performed as follows:
1- software updater
2- reboot
3- repeat steps 1-2 until there are no more updates
4- synaptic package upgrader
5- reboot
The boot failure occurs on step 5. This is reproducible.
Here is a screenshot of the synaptic upgrader candidates. One or more
of
Public bug reported:
***
*** Please reassign bug to proper package
***
On Jun 3 2019, the system update corrupts the system. It will not boot.
It hangs on the 3rd red dot of the Ubuntu splash screen. The remaining
2 dots are white. You never get the terminal screen with green [ ok]
status
In reply to
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829536/comments/2
please see the attached screenshot.
As for journalctl, I have 4 different versions. Which one do you want
to see?
** Attachment added: "switch_user_option_missing.png"
Public bug reported:
***
*** Please attribute this bug to the correct package
***
On an admin account, the Switch User option is not available in the drop
down choice list.
On a regular account, the Switch User option does not give a screen
with the list of users. Instead, you get a
Public bug reported:
Procedure to reproduce this bug:
- odt file resides on desktop
- double click to edit
- save
- many but not all desktop icons vanish
- click X to close writer window
- vanished desktop icons reappear
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libreoffice-core
If you do this from a nautilus window, you get the expected permanent
delete.
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825415
shift + delete on a desktop text file
text file moves to trash
this is reproducible
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825415
Title:
shift+delete sends to trash
To manage notifications
Public bug reported:
It should permanently delete the file or folder.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Workaround: drag/drop to desktop entirely within Nautilus.
You get a copy and not a move when you do this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825408
Title:
drag/drop to desktop fails
Public bug reported:
Workaround: drag/drop to desktop entirely within Nautilus.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
When the issue occurs, there may not be any system response at all.
Based on the size of the file, I assume it is cumulative over several
boots.
I am including this file now in the hopes you can successfully mine it
for your desired info.
This hang issue occurred recently.
Hope this helps.
On Ubuntu 16.04.5, I still get the problem.
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667505
Title:
Files and Trash hang
To
Public bug reported:
On Fri, Dec 21 2018 04:30:23 AM, calc properly parsed a csv file on this
pc.
It can no longer do this (see screenshot).
Input test.csv file is attached.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial4
Input test.csv file is attached.
** Attachment added: "input test.csv file"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1809558/+attachment/5224394/+files/test.csv
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I did some tests with 18.10 but the problem did not occur.
Since the bug is intermittent, these tests may not be significant.
Please leave this case open to future updates.
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Status:
Testing for intermittent bugs is always challenging.
Would testing on 18.10 be ok? This is how my test machine is
configured.
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug
Daniel,
When I was running 16.04.0 with the same mods described in comment 3 and
with the same monitor BUT with an older computer, I never got this
problem.
When I installed 16.04.5 (new install, erasing everything) on a newer
computer BUT with the same monitor, I started getting this issue.
The bug just happened again, this time with a text document.
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1805715
The problem has just occurred in a Chrome browser gmail window while
composing a new mail.
In mid composition, I left my computer to attend to other matters.
When I came back, the screen was locked.
Typing the password clearly revealed the plain text in the body of the
email, minus the first
Cannot reproduce this problem since reporting it.
That said, it has been festering for a while.
Please leave this open for others, just in case, given the seriousness.
By the way, the screensaver does not always kick in.
--
You received this bug notification because you are a member of Ubuntu
The bug was reproducible yesterday and was experienced previously.
Today, after booting from last night's shutdown, the problem is no
longer manifesting itself.
Note that Unity has been removed in favour of Gnome3 as per the
following procedure:
sudo apt-get install gdm3
sudo dpkg-reconfigure
bellajohsan (bellajohsan),
I am booting from a USB key into RAM. That boot fails as per
screenshots.
Power source and storage are immaterial.
This is not an Acer issue.
To all, could it be UEFI related? I tried to disable this in BIOS, but
that option is not available.
--
You received this
Joseph Salisbury (jsalisbury),
If you can direct me to an ISO download distribution containing your
proposed kernel, then yes, I can test.
Else, out of luck, sorry.
The PC does not boot at all.
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug
Since the laptop cannot be booted, apport cannot be run.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788686
Title:
Acer
Paul White (paulw2u),
I have not experienced this bug recently.
Please close this case.
Could you please assign this Bug #1788686 to the correct package.
Hopefully, it will be addressed in less than 3 years.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Ubuntu 18.04.1 LTS gives the same boot failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788686
Title:
Acer laptop does not boot Ubuntu 16.04.5
To manage notifications about this bug go to:
screen photo 2 is attached
** Attachment added: "ubuntu 16.04.5 boot fail - photo 2"
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1788686/+attachment/5179880/+files/20180823_150400.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Acer laptop model is A315-41-R001
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788686
Title:
Acer laptop does not boot Ubuntu 16.04.5
To manage notifications about this bug go to:
Public bug reported:
***
*** Please change package to the appropriate one
***
Trying to boot Acer laptop () from USB2 key on USB3 port with Ubuntu
16.04.5 LTS fails as per attached screenshots.
This is reproducible.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
This bug was reported about 8 years ago.
It is no longer a problem.
Please close this case.
** Changed in: firefox (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Issue #82 opened on https://gitlab.gnome.org/GNOME/gnome-system-
monitor/issues/82
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778361
Title:
The Processes tab only displays the current user's
This bug happens with a stock Ubuntu 18.04 install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778361
Title:
The Processes tab only displays the current user's processes
To manage
Power down, boot, another execution of Software Updater solves the
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778359
Title:
Software Updater hangs on "Waiting for packagekitd to exit"
Public bug reported:
***
*** Please attribute this bug to the correct package.
***
ubuntu-bug -w failed.
The "All Processes" option only displays the current user's processes.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gedit 3.28.1-1ubuntu1
ProcVersionSignature: Ubuntu
Public bug reported:
Software Updater not used in about 2 months on this test machine.
See screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: update-manager 1:18.04.11
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion:
Not upgrade, fresh install as per best practices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726919
Title:
Ubuntu 17.10 desktops corrupted
To manage notifications about this bug go to:
As per comment #9, I can no longer test this issue.
If you can reproduce this bug report by changing login options and then
"fix" by changing those options back, then please close this case.
Otherwise, wait for others to trip over this "bug" and enlist their
help.
--
You received this bug
This bug is no longer present in the final release of Ubuntu 18.04 LTS.
** Changed in: gedit (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/1756610
Title:
I burned to USB the current daily build of 18.04 and booted successfully
3 times.
The machine that was booted had 18.04 beta installed on the hard drive.
Grub (and everything else) has changed in the 6 years since this bug
report.
This bug has been fixed.
** Changed in: ubiquity (Ubuntu)
My test machine that had 17.10 has been overwritten with 18.04 beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726919
Title:
Ubuntu 17.10 desktops corrupted
To manage notifications about this
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726919
Title:
Ubuntu 17.10 desktops corrupted
To manage notifications about this
Public bug reported:
rename command pops up a dialog box instead of allowing inline editing.
See attached screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.2-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
1 - 100 of 929 matches
Mail list logo
