Public bug reported:
Jammy Jellyfish 22.04. When opening a PDF document with an external link
in it, clicking the link doesn't do anything. However, stderr says "env:
‘/snap/bin/firefox’: Permission denied"
How to reproduce:
Open example PDF file. Click link.
Expected: firefox opens link.
** Attachment added: "Example gz-file to demonstrate."
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1968548/+attachment/5579278/+files/file.html.gz
** Description changed:
- Due to Firefox being contained and not being able to read in ~/.cache/,
- html-files from an archive cannot
Public bug reported:
Due to Firefox Snap being contained and not being able to read in
~/.cache/, html-files from an archive cannot be read with Firefox.
Ubuntu 22.04 Jammy Jellyfish
Steps to reproduce:
- open, with file-roller, an archive containing a HTML-file;
- double click (i.e. open) the
I'm running Jammy, upgraded from Focal, and this bug bites me:
(evince:56279): dbind-WARNING **: 12:05:26.897: Couldn't connect to
accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus:
Permission denied
... then /var/log/syslog:
[...] audit: type=1400
*** This bug is a duplicate of bug 1794064 ***
https://bugs.launchpad.net/bugs/1794064
Evince spits an error message:
(evince:56279): dbind-WARNING **: 12:05:26.897: Couldn't connect to
accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus:
Permission denied
env:
Francisco: the "diversion" is the giveaway. "oem-release" is a package that
will lock the release number to the original (oem installed) version number. I
don't know why - but I found out yesterday, one of my customers upgraded his
Dell 20.04 to 21.04, only to end up with a recurring "21.04 is
SMB shares still do not work - for Libreoffice 6.4 that is. The the apt-
get installed version for LibreOffice6.4 does work for SMB shares.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729821
So far, no more lockups. (And I'm almost sorry to say that, as I realize
that it's not much we have here in this bug report - and it seems to
only affect me...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Done so. (FYI: upgrade came from 2.5, IIRC) 2:4.7.6+dfsg~ubuntu-
0ubuntu2.7 installed now. I'll report what happens - if anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824615
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1824615/+attachment/5255420/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "SmbLog.txt"
https://bugs.launchpad.net/bugs/1824615/+attachment/5255423/+files/SmbLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824615
Title:
apport information
** Attachment added: "SambaInstalledVersions.txt"
https://bugs.launchpad.net/bugs/1824615/+attachment/5255422/+files/SambaInstalledVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1824615/+attachment/5255421/+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/1824615
apport information
** Tags added: apport-collected bionic
** Description changed:
Since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9 / Ubuntu 18.04.1 LTS, smbd
locks up sometimes. We are unsure why. No messages in the log.smbd.
Symptoms: clients (a few, about 5 to 10, OSX and Linux machines)
Public bug reported:
Since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9 / Ubuntu 18.04.1 LTS, smbd
locks up sometimes. We are unsure why. No messages in the log.smbd.
Symptoms: clients (a few, about 5 to 10, OSX and Linux machines)
sometimes just cannot connect to Samba anymore. They call us, "the
The bug is somewhat worse than in the original report: grub-install will
remove anything that has "Ubuntu" (case INsensitive!) in it's name. In a
test, both "RAID Ubuntu /dev/sdc", "Ubuntu /dev/sdc" were removed by
grub-install. A label "RAID fallback /dev/sdc" would survive a call to
Thanks for the = 1.10 addition.
Still, if you install ntfs-3g but not attr, then the ntfs_test FAILS -
not skips - with an error ./grub-fs-tester: line 895: setfattr: command not
found. It probably tests the availability of mkfs.ntfs somewhere without
testing setfattr. You could argue that this
Fair enough. (The reason I'm building it anyway is that grub2_2.02~beta2-7
wouldn't install - so I could not get past the install phase - hence no
accounts; hence build as root :-S
So thanks again for beta2-8 - it makes things much easier :-)
--
You received this bug notification because you
Thanks - I'll recheck my build - problems after automake1.10 could be
due to wrong language settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299041
Title:
grub2-2.02 has wrong build-deps
Further research shows:
- a simple install with sda1 = fat32 EFI, sda2 = 100Gb ext4 does work
- an install with /dev/md0 formatted as ext4 root-fs fails
- an install with /dev/sda2 as LVM pv, with root as a volume within, fails too.
Both md and lvm installs initially seem to complain that
apport information
** Tags added: apport-collected trusty
** Description changed:
after apt-get build-dep grub-efi-amd64, many packages are missing. The ones
I tracked so far:
automake1.10 (another automake is probably somewhere in the dependencies, but
building complained that 1.10 is
Jörg, I don't think the ProcEnviron.txt is the information you were
looking for. However, apt-get install apport; apt-get install python-
apport; apport-collect 1299041 did just that (on 14.04).
Now on a freshly installed 14.04, I ran the following:
# apt-get build-dep grub; apt-get build-dep
# create a file /boot/grub/x86_64-efi/load.cfg with
search.fs_uuid 2ff0dd02-use-blkid-to-get-the-number-40cda0eb468d root
set prefix=($root)/boot/grub
# then use
chattr +i /boot/grub/x86_64-efi/load.cfg
# to make load.cfg write-protected (on an ext4 filesystem)
I'm still getting an error after
Public bug reported:
after apt-get build-dep grub-efi-amd64, many packages are missing. The ones I
tracked so far:
automake1.10 (another automake is probably somewhere in the dependencies, but
building complained that 1.10 is needed); to be able to run the tests,
dependencies seem to be: lzop;
That's why apt-get build-dep grub matters. Grub (not grub2) has a
Build-Depends: debhelper (= 4.0.0), automake1.9. Thus, automake1.9
gets installed. Grub2 doesn't even have a build-depend on automake -
there might be a lower dependency on automake but I did not check that.
So it's not a system
s/grub2/grub2-2.02/ - the version that was added to 14.04 recently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299041
Title:
grub2-2.02 has wrong build-deps
To manage notifications about this
... also, build-depends of grub2-2.02 are not right, see bug #1299041
Required for building, but not in build-depends: lzop hfsplus squashfs-tools
attr reiserfsprogs automake1.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
During installation of Trusty on a RAID6/LVM system, the installation fails
during the configure phase of grub-efi-amd64. The installer message says
GRUB installation failed
The 'grub-efi-amd64-signed' package failed to install into /target/. Without
the GRUB boot loader,
This new bug
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1298399 is also on
trusty, with grub 2.02~beta2-7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
2.02~beta2 requires
Unfortunately, no, that doesn't seem to work either. I managed to
compile qemu-kvm-1.0+noroms (required a few minor changes, linking with
librt and a documentation difference) and the supporting bios and pxe
files on Trusty. Migration now seems to work (Completed 100 %), but then
the target
Unfortunately, no, that doesn't seem to work either. I managed to
compile qemu-kvm-1.0+noroms (required a few minor changes, linking with
librt and a documentation difference) and the supporting bios and pxe
files on Trusty. Migration now seems to work (Completed 100 %), but then
the target
Ok, I understand. Please note that this was also an issue for 10.04 - 12.04,
so it's definitely a good idea to have it fixed for future upgrades (aka
trusty specific machine type).
I'm not sure about the extra qemu. The next action after migration would be to
install the real qemu, right? After
Otoh, now we're facing a non-migrateable 12.04 in general, because you cannot
move your VMs out of the way :-(
Anyway, proper documentation is helpful in any case. Finally: there is no real
workaround now, or is there? What would you do, having several 12.04 host
machines? Just migrate
Ok, I understand. Please note that this was also an issue for 10.04 - 12.04,
so it's definitely a good idea to have it fixed for future upgrades (aka
trusty specific machine type).
I'm not sure about the extra qemu. The next action after migration would be to
install the real qemu, right? After
Otoh, now we're facing a non-migrateable 12.04 in general, because you cannot
move your VMs out of the way :-(
Anyway, proper documentation is helpful in any case. Finally: there is no real
workaround now, or is there? What would you do, having several 12.04 host
machines? Just migrate
Hi,
Adding qemu:commandline tags needs a namespace. What you do is:
12.04~# virsh edit machine
Now add the namespace. The resulting first line of the domain xml-file should
read:
domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'
After that, adding qemu:commandline tags
Please note my comment #5: removing the vga adapter showed up a new
mismatch, this time for the virtio network adapter. I did not look into
that but you might want to check if there's more memory mismatches that
should be addressed before you start adding code.
--
You received this bug
Please note my comment #5: removing the vga adapter showed up a new
mismatch, this time for the virtio network adapter. I did not look into
that but you might want to check if there's more memory mismatches that
should be addressed before you start adding code.
--
You received this bug
Hi,
Adding qemu:commandline tags needs a namespace. What you do is:
12.04~# virsh edit machine
Now add the namespace. The resulting first line of the domain xml-file should
read:
domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'
After that, adding qemu:commandline tags
Hi, is there anything I can do to help this bug's status?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and 14.04 Trusty
To
When you add a machine with virt-manager, the display setting is model
type='cirrus' vram='9216' heads='1'/. I tried to set it to 10240 (which
is 10mb) but that didn't help - the error is the same.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
BTW, that last test was with the regular qemu-kvm in trusty, which is
1.7.0+dfsg-3ubuntu6. I upgraded to the ppa-version again and ... it
seems to do something. BRB.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
error: Unable to read from monitor: Connection reset by peer and the machine
crashed :-(
Next try, same as always: Length mismatch: vga.vram: 100 in != 80
That's a weird side effect, sometimes not only migration fails, but the machine
on the source host crashes, too. Did you reproduce
Hi, is there anything I can do to help this bug's status?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and 14.04 Trusty
To manage
When you add a machine with virt-manager, the display setting is model
type='cirrus' vram='9216' heads='1'/. I tried to set it to 10240 (which
is 10mb) but that didn't help - the error is the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
BTW, that last test was with the regular qemu-kvm in trusty, which is
1.7.0+dfsg-3ubuntu6. I upgraded to the ppa-version again and ... it
seems to do something. BRB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
error: Unable to read from monitor: Connection reset by peer and the machine
crashed :-(
Next try, same as always: Length mismatch: vga.vram: 100 in != 80
That's a weird side effect, sometimes not only migration fails, but the machine
on the source host crashes, too. Did you reproduce
Hi,
Installed qemu-common qemu-keymaps qemu-kvm qemu-system-common
qemu-system-x86 qemu-utils from the ppa, same error:
source (12.04): # error: operation failed: migration job: unexpectedly
failed
Log file on target (14.04, log_level = 1) says:
2014-03-13 07:03:56.550+: starting up
The 100 comes from vga.h in the source for qemu-kvm-1.0+noroms: #define
VGA_RAM_SIZE (16 * 1024 * 1024)
I could not find the 80 value - as far as I can see, vga ram size is not
fixed anymore in the qemu-1.7.0+dfsg source - but I did not fully understand
the code.
Anyway, I tried
Hi,
Installed qemu-common qemu-keymaps qemu-kvm qemu-system-common
qemu-system-x86 qemu-utils from the ppa, same error:
source (12.04): # error: operation failed: migration job: unexpectedly
failed
Log file on target (14.04, log_level = 1) says:
2014-03-13 07:03:56.550+: starting up
The 100 comes from vga.h in the source for qemu-kvm-1.0+noroms: #define
VGA_RAM_SIZE (16 * 1024 * 1024)
I could not find the 80 value - as far as I can see, vga ram size is not
fixed anymore in the qemu-1.7.0+dfsg source - but I did not fully understand
the code.
Anyway, I tried
Public bug reported:
We're trying to live migrate machine fhdhvalentijn to a server named ranja.
This used to work perfectly when both systems ran 12.04 Precise. After
upgrading the target machine (ranja) to Trusty, migration fails; sometimes,
migration results in shutting down the VM.
Yes, that's possible. Should I install the ppa on source, target or
both?
V.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and
Public bug reported:
We're trying to live migrate machine fhdhvalentijn to a server named ranja.
This used to work perfectly when both systems ran 12.04 Precise. After
upgrading the target machine (ranja) to Trusty, migration fails; sometimes,
migration results in shutting down the VM.
Yes, that's possible. Should I install the ppa on source, target or
both?
V.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and 14.04 Trusty
To
Hmm. I can reproduce the issue by putting the following line in
/etc/thunderbird/syspref.js:
pref(toolkit.telemetry.prompted, true);
However, if I set this in prefs.js in the user's profile, after a restart
Thunderbird has changed this into
user_pref(toolkit.telemetry.prompted, 2);
Changing
This is the related mozilla bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=807848, and
https://bugzilla.mozilla.org/show_bug.cgi?id=842073 provides background
information and -noise.
** Bug watch added: Mozilla Bugzilla #807848
https://bugzilla.mozilla.org/show_bug.cgi?id=807848
** Bug
On my 64 bit system nscd still seems to work. Have you tried to invalidate the
nscd caches?
nscd -i group; nscd -i passwd; nscd -i services
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085957
This could be just a manifestation of bug #435719. Not sure though,
because the original report does not mention if /home is mounted on NFS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585209
This could be just a manifestation of bug #435719. Not sure though,
because the original report does not mention if /home is mounted on NFS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/384852
The bug clearly states: When doing this with the OOo from 8.04LTS, or
with the official version from Openoffice.org, autodetection does it's
job.
Hence, this is NOT an upstream issue. It is a bug introduced by the
Ubuntu 10.04 packages.
--
You received this bug notification because you are a
I don't understand the intended behaviour part. I don't think I should
file a bug in OpenOffice.org because autodetection does work correctly
there, or should I? ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a security vulnerability ***
Public security bug reported:
The current pam profiles mostly seem to say:
auth[success=$skipnum default=ignore]
This means that pam will happily try to validate your password against
all the modules there are; in fact, it ignores wrong
Ignoring everything, except success is the security issue.
I don't have anything against trying all modules, nor do I think that the one
succeeding module is a security issue per se. But ignoring blatant errors,
locked out users, wrong and/or expired passwords, that is a security issue.
May I
This file crashes a Panasonic DP-C265, when printed under Maverick with
either Acroread, Evince or gtklp, print queue running on Lucid with
modifications as described earlier, to avoid PDF workflow. Will try to
fetch the PS file that is sent to the printer shortly.
** Attachment added: Crashes a
Is there a way in which I can send a PS file (as made from the
instructions at #18) to the printer, manually, through the IPP backend?
To double check if this still crashes the printer?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Done as suggested in comment #18:
added FileDevice True
cp /etc/cups/ppd/kleurenkopieerapparaat.ppd /tmp/pana.ppd
lpadmin -p printtofile -E -v file:/tmp/spoolfile.ps -P /tmp/pana.ppd
lp -d printtofile /tmp/Printcheck_DenHaag_week03.pdf
The resulting Postscript file is attached.
** Attachment
Thanks. I verified, that printing
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/691130/+attachment/1791098/+files/spoolfile.ps
on this Panasonic printer crashes the printer - although the printer does not
restart, it says Machine Error - Call TEL. 0736402888 - which is the local
service
Printing the file does *not* work with these changes. That is: if you
have these changes, and try to print non-duplex, the printer will
freeze. Printing duplex does work. Regarding the printer model: I'll get
back to you with the specific model, because, actually, it strikes me as
a bit odd that
Ahem. I did not read your comment too well. I will check your changes,
*then* get back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/691130
Title:
PDF workflow flawed, crashes printers
--
BTW, is there a possibility to intercept the final PS stream that is
sent to the printer? Having an intermediate PDF that crashes in some
situations, but prints in other, is helpful, but a bit complicated as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi,
Op 07-01-11 20:47, georgeliu schreef:
Yes, you can create a print-to-file queue using the same PPD file.
I'll implement that next week.
[...]
In my previous posting (#14), I didn't want you to try anything new, I just
want to know how to reproduce the problem.
Do I need to do the
I now have a verifyable PDF, straight from the print queue, that crashes
a certain Ricoh printer - a Ricoh Aficio AP4510 PS, which isn't exactly
your entry-level small printer - it's rated 45K pages per month.
The printer crash *only* happens when:
- we print the original document (a PDF) from
(I removed the previous attachment; sorry for the fuzz; I simply
couldn't reproduce the issue yesterday while I was at the customer's
premises, so I suspect a luser reporting nonsense).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh well. Please forget about this attachment. Never trust your end users
to tell you if anything did or did not work; as far as I can see, the
attached PDF just works (might have been a bit slower under 10.04, I'm
not sure). I still do have a PDF that crashes the printer - only if
printed from
http://ubuntuforums.org/showthread.php?t=1646526 seems to suggest that
this is Inotify-related. That would mean that this is another
manifestation of the problem described in Bug #383118 (which is, in it's
own, a bit misguided as it's probably not Gamin, but the kernel that is
at fault, but I'm
The bug is not present in the upstream 3.2.0 version (when installing
that on Ubuntu, that is), so it's an Ubuntu ( Debian?) specific bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/561703
Title:
Unfortunately, with a Maverick installation, the long delay in printing
persists. Please note that this is not a live CD, but an installed
machine. On the other hand, the install is pretty basic and printing is
done through the network, so there is nothing the local Cups is doing.
Our *hacked*
[...] will output a certain PDF [...]
than 15 minutes). I'm currently investigating if this PPD is public
That should read: if this PDF (the document I'm trying to print) is
public.
So, to summarize: a) printing from a Maverick machine to a Lucid server with
hacked-up printing path: 4 minutes
The attached PDF (which is public) will not print or print very slowly
(30 minutes) on the above printer with the Lucid/Maverick default print
path. With a hacked workflow as described, all pages print within 4
minutes.
** Attachment added: PDF that will not print with the new PDF workflow
I don't think I understand the Capturing print job data part of
DebuggingPrintingProblems. As far as I can see, disabling the printer
will stop the print queue handling *before* filtering jobs. So all I am
getting is the PDF that I already attached above. Am I doing something
wrong?
--
You
That is what I did. (Hence my confusion when the captured file came out
identical to the original file ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/691130
Title:
PDF workflow flawed, crashes
Public bug reported:
Binary package hint: cups
Under Ubuntu Lucid, the new PDF workflow in CUPS poses various problems
for various printers: jobs will either not print (and may crash the
printer) or print very slowly. These are reports from various
customers.
We have seen a bunch of Ricoh
Op 16-12-10 19:07, Till Kamppeter schreef:
Your suggestion of modifiying the cost factors of the CUPS filters we
have already applied in Maverick. Our implementation is a little
different, we have only set
application/postscript application/vnd.cups-postscript 65 pstops
I know. (See below).
** Changed in: simple-scan (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/575191
Title:
simple-scan doesn't scan from HP M1522nf (MFP), while xsane
*** This bug is a duplicate of bug 575191 ***
https://bugs.launchpad.net/bugs/575191
** This bug has been marked a duplicate of bug 575191
simple-scan doesn't scan from HP M1522nf (MFP), while xsane works
* You can subscribe to bug 575191 by following this link:
Same problem in Maverick with a HP LaserJet M2727nf MFP. The last lines
of ltrace scanimage 21 | grep sane_ read:
sane_start(0x84ec568, 0x804d7a0, 0, 0xbfc8bb54, 0) = 0
sane_get_parameters(0x84ec568, 0xbfc8bb24, 0, 0xbfc8bb54, 0) = 0
sane_read(0x84ec568, 0x851ad08, 32768, 0xbfc8bb50, 0) = 2
Hmm. If libvirt shuts down the virtual machines it monitors, then these
virtual machines will also be shut down when updating libvirt.
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
The proposals in this report (mine, John Morrissey's) all have a pre-
stop shutdown of virtual machines in their Upstart conf-file.
When you update libvirt-bin, dpkg will stop libvirt-bin before
upgrading. As a result — if you have implemented the pre-stop shutdown —
your virtual machines will
Hmm. If libvirt shuts down the virtual machines it monitors, then these
virtual machines will also be shut down when updating libvirt.
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Bugs,
The proposals in this report (mine, John Morrissey's) all have a pre-
stop shutdown of virtual machines in their Upstart conf-file.
When you update libvirt-bin, dpkg will stop libvirt-bin before
upgrading. As a result — if you have implemented the pre-stop shutdown —
your virtual machines will
When using the -W (--wide) option, the addresses are readable.
However, the wide option is not available under Ubuntu 8.04 LTS. It is
available under Ubuntu 10.04 LTS.
--
netstat doesn't display ipv6 addresses correctly (they are truncated)
https://bugs.launchpad.net/bugs/511401
You received
In Maverick, the rewrite of /etc/hosts causes the idmapd daemon to
think that the current domain is localdomain.
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
... no, that's not the only thing; does Network Manager set the hostname
to localhost.localdomain? Because fixing /etc/hosts with chattr +i
when running networkmanager will still cause idmapd to think that it's
current domain is localdomain.
--
hostname -f does not return a proper FQDN
Public bug reported:
Binary package hint: joystick
Since kernel 2.6.26, there's a zhenhua kernel module that supports the
Zhen Hua joystick. Inputattach does not support this kernel module,
although there's a patch ready for inclusion.
Please note, that the patch was made originally by the
** Patch added: support Zhen Hua protocol in inputattach
https://bugs.launchpad.net/bugs/648945/+attachment/1643963/+files/inputattach-revised.patch
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/648945/+attachment/1643964/+files/Dependencies.txt
--
zhen-hua
... forgot the utils/serio-ids.h part of the patch; here is the correct
update-inputattach.patch.
** Patch added: now with serio-ids.h included
https://bugs.launchpad.net/ubuntu/+source/joystick/+bug/648945/+attachment/1643988/+files/update-inputattach.patch
--
zhen-hua protocol not
While there's many solutions now to shutdown VM's, here's my 2 cents. Instead
of a libvirt-bin.conf script, I made a separate script
(/usr/local/sbin/shutdown-libvirt-hosts.sh). This script waits 120 seconds for
all VM's to shut down. Then I'm running this script from two places; in
I might have overlooked it, but I could not find the PID of the
sendsigs-revised.sh script itself as an omit PID inside the script.
I.e. isn't there a possibility the script kills itself now? Or did I
miss something?
--
sendsigs can kill upstart scripts' child processes
While there's many solutions now to shutdown VM's, here's my 2 cents. Instead
of a libvirt-bin.conf script, I made a separate script
(/usr/local/sbin/shutdown-libvirt-hosts.sh). This script waits 120 seconds for
all VM's to shut down. Then I'm running this script from two places; in
1 - 100 of 181 matches
Mail list logo
