I'm gdisk's upstream author. I'm pretty busy with other things right
now, so I don't really have the time to invest in implementing floating-
point support in gdisk's inputs. Done poorly, that's the sort of thing
that could create additional bugs. Thus, I don't recommend holding off
on implementing
I've reset this from "Won't Fix" to "Confirmed" because I believe
Filofel's analysis merits another look at the issue.
** Changed in: ubiquity (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I've tried to reproduce this problem in a VirtualBox VM, with no
succcess. My suspicion is that there's been a regression somewhere (most
likely in GRUB 2 or the Linux kernel) that's causing partial
incompatibility with the older UEFI version used on your motherboard,
Michael. I say "partial incomp
This problem disappeared for me when I upgraded my kernel from
5.15.0-22-generic to 5.15.0-23-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965302
Title:
Text-mode console is unavailable i
Public bug reported:
I recently updated a system from Focal to Jammy pre-release, and I've
found that the text-mode console (obtained by hitting Ctrl+Alt+F1) is
blank. It still seems to accept keyboard input; I can log in "blind" and
enter commands that have effects, but I see nothing on the scree
Public bug reported:
running script "apl-sof-setup-audio" to setup SOF audio on laptop.
During the script, received an error "dpkg-deb: error: paste subprocess
was killed by signal." and the bug report dialog appeared immediately
after.
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: fi
Public bug reported:
Trying to install gnome-shell-extension-gsconnect on Ubuntu 20.04 resulted in
GNOME crashing.
Upgraded to Ubuntu 21.04, then this message comes up (every time) in syslog on
logging on:
gnome-shell[3026]: JS ERROR: Extension gsconn...@andyholmes.github.io:
ImportError: No JS
I've now released GPT fdisk version 1.0.8, which incorporates this bug
fix, as well as a new feature in gdisk and sgdisk that enables
correcting partition names that have already been corrupted by the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I'm the author of GPT fdisk, and I intend to release a version 1.0.8
with this fix within a day or two. The only major change since 1.0.7 is
the MR linked by Christian above. If patching earlier versions of GPT
fdisk, then the following commit should be included, too:
https://sourceforge.net/p/gpt
I can confirm that the PPA described in post #2, above, works on a
MacBook Air 6,2. Please get this fixed prior to Hirsute's final release!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909369
Title:
Public bug reported:
I own a MacBook Air 6,2 on which I've installed several versions of
Ubuntu. I recently updated to the hirsute (21.04) pre-release, but WiFi
has stopped working. Some web searching suggested re-installing the
bcmwl-kernel-source package, which produced the following output:
$
my
Gigabit MB being faulty, I have installed a nVidia Quatro K2200, and it
seems to be working fine now.
Sorry for the false positive.
Rod Hutchinson
ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: grub-efi-amd64-signed 1.158+2.04-1ubuntu37
ProcVersionSignature: Ubuntu 5.8.0-36.40
I'm the original bug reporter, and in that context (of MAAS
deployments), this fix does nothing helpful -- it literally does not
change the original observed problem in any way. Thus, I'm marking this
verification-failed-focal. (I've not tested under other Ubuntu
versions.)
** Tags added: verifica
I may have installed it incorrectly, but what I've got is not working.
It boots fine with Secure Boot disabled, but it shuts down with the same
message about a compromised system as the stock GRUB. What I did to
test:
1) Installed grub-efi-amd64-signed (version
1.142.10+2.04-1ubuntu26.8)
2) Cop
I agree with Seth Arnold; assuming that the user won't make a mistake is
a recipe for disaster.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466150
Title:
grub-install breaks when ESP is on raid
@Georg Sauthoff wrote:
> Can you name _one_ UEFI implementation that actually does write to an
ESP?
Offhand, I don't know of an EFI that will write to the ESP
automatically; HOWEVER, there are cases when it can happen because of
user actions and/or EFI applications' operation. For instance:
* Th
*** This bug is a duplicate of bug 1900668 ***
https://bugs.launchpad.net/bugs/1900668
It turns out that "normal" does work, although I could swear it didn't
work earlier. Perhaps I mis-typed the command. In any event, I'm marking
this bug report as a duplicate now.
** This bug has been marke
Ah, I thought the fact that "net_bootps" returned a different error
meant this was a different bug; but if that's a typo, then perhaps not.
Also, typing "normal" (as in comment #5 there) doesn't work. Still, it
does look like it's likely a duplicate.
--
You received this bug notification because
** Attachment added: "Diagnostics at the "grub>" prompt"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+attachment/5435180/+files/iKVM_capture%20%281%29.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
On SOME (but not all) boots via MAAS, GRUB hangs at the "grub>" prompt.
This happens about 10% or 20% of the time on affected servers (at least
ostwald and meitner, two Supermicro servers).
The MAAS rackd.log file shows that the node has requested and received
GRUB:
2020-11-
** Changed in: checkbox-support (Ubuntu)
Status: In Progress => 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/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not bein
FWIW, I tried a deployment on an AMD64-architecture server using an
ASRock MT-C224 motherboard (one of the experimental Orange Box v3 nodes
in 18T), and it failed. I can provide additional logs if required. I
have not attempted to install any of the branches associated with this
bug report. (I'm no
Joe - I'm glad to hear that it is working and that Debian has also
updated their code. I'm glad that it helped others!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876286
Title:
Evolution reports
@Joe, I’m glad to hear that it works! FYI, Ubuntu rolls out updates slowly
starting with 10% of users, increasing 10% every 6 hours if there are no
problems. This may explain why it took some time before you saw the update.
Everyone should have been able to apply the updates on Sunday. Detai
@seb128 just checking to make sure that your not waiting for something
on my end. If I understand it correctly it looks like Focal is done
since you re-ran the systemd test and now all tests have passed, and I
verified that the fix worked. Should the tag be updated to
verification-done-focal? I’
Joe, It's still in the proposed repo and hasn't made it to updates yet. Did
you try the instuctions here:
https://wiki.ubuntu.com/Testing/EnableProposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
@magnum6 glad to hear yahoo is working. Did you try using gnutls-cli to
connect to bestweb.net? You didn't specify the full name and port so I
can't try it here. If you try on your end and see a message about
simple client mode towards the end of the output then you have passed
the handshake par
I'm able to confirm the focal-proposed updates/3.6.13-2ubuntu1.2 worked for pop
connections to pop.verizon.net on port 995. I started with a fresh install of
Ubuntu 20.04 and applied all updates except proposed. In order to make GnuTLS
3.6 use an older version of TLS I created the file /etc/gnut
I'm able to confirm the xenial-proposed updates/3.4.10-4ubuntu1.8 worked
for pop connections to pop.verizon.net on port 995. I started with a
fresh install of Ubuntu 16.04 and applied all updates except proposed.
As expected gnutls-cli and evolution returned the error. After
installing the proposed
@seb128 - Awesome! I will check back after work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876286
Title:
Evolution reports "Error performing TLS handshake: Internal error in
memory allocatio
@seb128 can you double check my thinking? It looks like the regressions on
Bionic with glib-networking/2.56.0-1 are related to newer versions of GnuTLS
reporting GNUTLS_CERT_INSECURE_ALGORITHM on the test certificates. Michael
Catanzaro posted a patch on 2018-04-11 on comment 3 at:
https://bug
@smnbldwn it looks like the Xenial fix was also built for powerpc and
ppc64el
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876286
Title:
Evolution reports "Error performing TLS handshake: Internal
@@stephenholden both of these have to be updated. This is where the
code change was made:
ii libgnutls30:amd64 3.5.18-1ubuntu1.3
amd64GNU TLS library - main
runtime library
ii libgnutls30:i386
@sil2100 - I'm able to confirm the bionic-proposed updates worked for
pop connections to pop.verizon.net on port 995. I started with a fresh
install of Ubuntu 18.04 and applied all updates except proposed. As
expected gnutls-cli and evolution returned the error. After installing
the proposed ver
@stephenholden could you provide:
1) details on your connection type (pop/imap), server and port (in my
case this was pop to pop.verizon.net on port 995).
2) output of "dpkg -l | grep gnutls"
3) test my server using "gnutls-cli pop.verizon.net:995" (you may need
to install the gnutls-bin package
Cool! I updated the description. Let me know what you think.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876286
Title:
Evolution reports "Error performing TLS handshake: Internal error in
mem
** Description changed:
[Impact]
Evolution and Claws email clients stopped connecting to Yahoo, AOL,
Verizon, AT&T, Bell South, etc email servers which are run by the same
- group. Users are unable to get to their email.
+ group. Users are unable to get to their email.
+
+ The underlyin
Patch for Ubuntu 16.04/3.4.10 attached.
Note: testing with gnutls-cli worked with the following command:
gnutls-cli -p 995 pop.verizon.net
** Patch added: "Patch for Ubuntu 16.04/3.4.10"
https://bugs.launchpad.net/ubuntu/focal/+source/gnutls28/+bug/1876286/+attachment/5384839/+files/51_allow_
@seb128 - Excellent, thank you! Other users have reported the same
issue against different versions of Ubuntu. I believe that Eoan and
Xenial are the other two supported versions. I would be willing to
looking into those versions and see what changes are necessary. Would
those be separate SRU’s
Patch for Ubuntu 18.04/3.5.18 attached.
Note: testing with gnutls-cli worked with the following command:
gnutls-cli pop.verizon.net:995
** Patch added: "Patch for Ubuntu 18.04/3.5.18 attached."
https://bugs.launchpad.net/ubuntu/focal/+source/gnutls28/+bug/1876286/+attachment/5384231/+files/50
Patch for Ubuntu 18.04/3.5.18 attached.
Note: testing with gnutls-cli worked with the following command:
gnutls-cli pop.verizon.net:995
** Patch added: "Patch for Ubuntu 18.04/3.5.18 attached."
https://bugs.launchpad.net/ubuntu/focal/+source/gnutls28/+bug/1876286/+attachment/5384230/+files/50
u has in the current
repo.
Thanks again,
Rod
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876286
Title:
Evolution reports "Error performing TLS handshake: Internal error in
memor
d the description with the first cut at an
impact statement. I'm not sure what to put for the [Regression
Potential] section. Any help that you can provide will be greatly
appreciated!
Thanks,
Rod
** Description changed:
+ [Impact]
+
+ Evolution and Claws email clients stopped connecti
Big shout out to Daiki Ueno and Andreas Metzler of the GnuTLS project
and everyone on this thread for helping out! Testing with Debian
Bullseye and Ubuntu Groovy + proposed repo was successful. Both
included version 3.6.13-4 of GnuTLS. Hopefully it won't be much longer
before this fix is pushed
As I said, the EFI/foo/grubx64.efi is taken from MAAS. It's presumably
netboot-enabled, but can't seem to find its config file, hence the need
for the manual entry in steps 9-11. Note that I'm not a MAAS developer,
so my understanding of its internals is limited.
--
You received this bug notifica
FWIW, I'm having this problem, too, specifically with the icons files,
as noted in comment #12, on my mirror running on Ubuntu 18.04. Oddly,
some installations using my mirror are fine with this, whereas others
complain. Applying the patch linked in comment #12 fixed it for me.
--
You received th
I've managed to create a procedure that duplicates this problem without
the involvement of MAAS, except for one file pulled from MAAS. The
procedure is awkward, but it reproduces the problem. Here's the
procedure:
1) Ensure that Secure Boot is enabled.
2) Install Ubuntu. (I used 20.04 LTS server.)
Unfortunately, capella in 1SS is not currently accessible by our team.
You can test on jehan in 18T, though; I'm sending you an e-mail with
details.
I don't know what you mean by "remote artifacts" and "local artifacts."
The steps to reproduce the problem is simply to enable Secure Boot and
attemp
** Bug watch added: Red Hat Bugzilla #1838187
https://bugzilla.redhat.com/show_bug.cgi?id=1838187
** Also affects: gnutls28 (CentOS) via
https://bugzilla.redhat.com/show_bug.cgi?id=1838187
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Daiki Ueno from the GnuTLS accepted my merge request (1260) that fixes this
problem. Can Ubuntu backport the changes to 18.04 and 16.04?
https://gitlab.com/gnutls/gnutls/-/merge_requests/1260
** Changed in: gnutls28 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification
The issue appears to be in /usr/lib/x86_64-linux-
gnu/libgnutls.so.30.14.10 with the function
_gnutls_recv_new_session_ticket around line 758 of session_ticket.c.
The code reads two bytes and assigns the result to the variable
ticket_len. Unfortunately this value is zero. A few lines later when
t
I used the built in backup on the file menu, "Backup Evolution Data
...". The following output appeared:
evolution-backup-Message: 18:00:36.504: dconf dump
/org/gnome/evolution-data-server/
>/home/user/.local/share/evolution/backup-restore-dconf-eds.ini
evolution-backup-Message: 18:00:36.537: dco
I looked into upgrading from Ubuntu 18.04 to 20.04 but evidently that isn't an
option until sometime in July. I tried to install the flatpack version and was
able to get to all my email accounts again. Before trying this make sure to
backup your current evolution data (File, Backup Evolution d
that was mentioned in the Linux Mint
forum.
Rod
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876286
Title:
Evolution reports "Error performing TLS handshake: Internal error in
memory alloca
This problem still exists in Ubuntu 20.04 Desktop. Selecting either
"primary" or "logical" partition types works fine, but the distinction
is meaningless for GPT, and asking for the partition type could be
confusing to users who aren't expecting it -- they might not understand
the difference or the
and keys.
Rod
** Attachment added: "EvolutionVerizonHandshakeFailure.zip"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+attachment/5367101/+files/EvolutionVerizonHandshakeFailure.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs
Thanks for your help with this Sebastien. I suspected it was something
like this but didn't know how to find it. If its an old, unmaintained
feature then no need to pursue it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Hmm, doing the reset caused the computer to freeze, I had to switch to a
tty and reboot. Ran the reset again in the background with just a
terminal open and it succeeded. The problem has gone away. I've saved
the config before and after (attached) but the suspicious item is
org.gnome.nautilus.prefe
** Attachment added: "Nautilus with reset config"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+attachment/5366215/+files/after-config.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I haven't knowingly changed anything recently but my original
installation was 15.04 and I've upgraded progressively so may have set
something in the past. I didn't have the problem with 18.04 though. I've
tried with a different user and the problem doesn't appear to be present
so it looks like it
It seems that on clicking an item the focus is temporarily set to a
different item further up the page before setting it to the selected
item. This can cause the page to scroll up to display the temporarily
focused item before scrolling down to show the selected item. Hence the
jump.
--
You recei
I haven't been able to get the pop3 debug logging to work. Maybe one of
the developers could try to add another account with a pop connection to
verizon from a fully patched 18.04 machine? The verizon.net settings
are:
Server: pop.verizon.net
Port: 995
Encryption method:
Public bug reported:
When Evolution checks my verizon.net account it displays the message
"Error performing TLS handshake: Internal error in memory allocation"
and doesn't download any new email messages. This started happening two
days ago shortly after updates were applied. Normally it would d
I can't see an error in the log but I'm no expert at reading these, I've
attached a copy of today's entries in case you can see something.
Its not specific to the directory, other than it has to have more entries than
can fit in the window.
The zoom setting makes no difference except to make the
I'm not sure if this is relevant but I had installed gnome-sushi. I've
since uninstalled it in case it has changed something but the problem
persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875
Here's a screencast.
** Attachment added: "Nautilus Bug.mp4"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+attachment/5361614/+files/Nautilus%20Bug.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Here is a screenshot prior to clicking on the document Magic Books.pdf
** Attachment added: "Before clicking"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+attachment/5361605/+files/Screenshot%20from%202020-04-27%2013-07-10.png
--
You received this bug notification because
And here is a screenshot after clicking on Magic Books.pdf. Note that
the selected document has been scrolled to the bottom of the window.
** Attachment added: "After clicking"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+attachment/5361606/+files/Screenshot%20from%202020-0
Public bug reported:
Ubuntu: 20.04LTS
Nautilus: 1:3.36.1.1-1ubuntu2
Double clicking an item in Nautilus should open the item but this
doesn't happen in all cases because the display is scrolled.
When items are displayed in icon view (as opposed to list view) and there are
more items than can b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328497/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328508/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328494/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
Unit
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328505/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328500/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/186
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328490/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328503/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "upstart.unity-panel-service.log.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328507/+files/upstart.unity-panel-service.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328492/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Ti
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328498/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328504/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328496/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328499/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328489/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328509/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328510/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328491/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Tags added: apport-collected focal third-party-packages ubuntu
** Description changed:
My system has been upgraded through several Ubuntu versions, and I'm now
(15 Feb 2020) on a pre-release version of Ubuntu 20.04 (Focal Fossa).
I've been using Unity on this system s
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328502/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
Un
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328493/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
Unit
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328501/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328495/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328506/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
Un
Public bug reported:
My system has been upgraded through several Ubuntu versions, and I'm now
(15 Feb 2020) on a pre-release version of Ubuntu 20.04 (Focal Fossa).
I've been using Unity on this system since Ubuntu's installation years
ago, and it's worked fine, including when I first installed the
Public bug reported:
Permissions problem creating file in /tmp. I worked around it by
temporarily removing the sticky bit on /tmp; this enabled the package to
install, but is obviously unacceptable in a release package.
This occurred on upgrading a MythTV frontend box from Eoan to Focal
developme
If this is the same fix that Colin posted earlier and that I tested,
then it's fine; I reported my test results in post #11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851316
Title:
Failures of
Public bug reported:
I installed ZFS using the 19.10 installer and ran into some severe load
caused by /etc/zfs/zed.d/history_event-zfs-list-cacher.sh
Microk8s, due to the way containerd manages container filesystems,
causes numerous zevents and can easily overwhelm the above script.
I filed a t
I've tested the PPA in the application that originally prompted my bug
report, and it's working fine. Will this be merged into Ubuntu's version
of lshw before 20.04 is released?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I managed to check the PPA version just now, and it's working fine.
Thanks for the quick fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848556
Title:
qemu-img check failing on remote image in E
I tried qemu from git, but I get an "unknown protocol" error when I try
to access an image via HTTP:
$ ./qemu-img check http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img
qemu-img: Could not open
'http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img': Unknown protocol
'http'
Is ther
Public bug reported:
On a fresh Ubuntu 18.04 server installation, running sosreport creates
root-owned files in ~/.config. Specifically, I'm using the following
command:
sudo sosreport --batch --tmp-dir /tmp/
Prior to running this command, ~/.config did not exist. After running
the command, ~/.c
1 - 100 of 604 matches
Mail list logo
