Disabling advanced tiling isn't exactly a solution. More of a work-
around. The features of ET sound great. I'd love to use them, but this
resizing bug is way more annoying, so at the moment I can't.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Definitely not mawk related. I have other programs (e.g. tar) failing
under fakeroot/fakechroot as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052392
Title:
Noble variant=fakechroot fails
I'm running qemu-arm version 4.2.1 (Debian 1:4.2-3ubuntu6.17) on Ubuntu
20.04.03, but I seem to still be affected by this (or something very
much like it). In my case it is armhf exim4 crashing while creating a
chroot on an amd64 host. The final command run from deeply within
exim4's postinst is:
Actually, I was wrong about arm-linux-gnueabihf-gcc! It *also* doesn't
find /usr/include/asm, instead correctly finding /usr/arm-linux-
gnueabihf/include/asm!
So actually, as far as I can tell *nothing* uses /usr/include/asm.
--
You received this bug notification because you are a member of
Can someone please explain why /usr/include/asm is needed? It seems to
me neither gcc -m32 nor gcc -m64 use it (both finding the ones in
/usr/include/i386-linux-gnu and /usr/include/x86_64-linux-gnu instead).
arm-linux-gnueabihf-gcc finds it which is not correct, but can be fixed
easily enough by
In fact, I can confirm that hirsute package cleanly installs in focal
and (almost) fixes the issue.
Almost because the Address is set to the string "172.25.117.104 (DHCP4)"
which is not very useful. Expecting scripts to parse that string and
take it apart makes a farce of passing all that
Any idea whether this fix can be back-ported to focal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
networkd-dispatcher gives corrupted information
To manage notifications about
Never mind. The scripts were in the wrong directory. /lib instead of
/usr/lib.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772137
Title:
networkd-dispatcher starts too late to take effect on
It appears this has been "unfixed" in focal?
root@ttde-kvm6:~# systemctl cat networkd-dispatcher.service
# /lib/systemd/system/networkd-dispatcher.service
[Unit]
Description=Dispatcher daemon for systemd-networkd
[Service]
Type=notify
ExecStart=/usr/bin/networkd-dispatcher
Any idea whether this fix can be back-ported to focal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
networkd-dispatcher gives corrupted information
To manage notifications about
Oh, that's good news. Let us know when it is uploaded and I give it a
spin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
networkd-dispatcher gives corrupted information
To manage
They were not. Adding a [global] before each include (since sections
opened in an include file stay open in the parent) makes them work as
expected!
Thanks so much Christian for your work on this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
LOL, I would call that a bit more than "suspicious". More like a smoking
gun?!
Thanks for putting time into this Christian. Does this bring us any
closer to fixing it? Does it need to be raised upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ok, after a few starting hiccups, I managed to get our management system
to support groovy and install a VM. I have only tested the behaviour of
the workgroup setting with smbclient -L localhost since it does not rely
on any external servers etc.
I can confirm that the behaviour is unchanged in
@Paride: Good catch. The second file's contents are:
# Global ttde samba config. Do not edit.
[global]
workgroup = TEL
include=/etc/samba/dhcp.conf
encrypt passwords = true
# ICT don't like us to rebroadcast printers all over the shop
load printers=no
show add printer wizard=no
disable spools=yes
I have tried including
[global]
client min protocol = NT1
in the top-level file both before and after all the includes. In all
cases it worked. This seems to indicate that a section can be re-opened
and the problem is likely in the include mechanism itself.
--
You received this bug
Public bug reported:
Hi, since upgrading to Ubuntu 20.04 I cannot gio mount or otherwise
connect to my companies' samba shares due to them requiring the NT1
protocol. Adding client min protocol = NT1 to ~/.smb/smb.conf works, but
I need to deploy this to a largish number of managed machines. The
I should clarify that it works when I put it in the [global] section in
/usr/share/samba/smb.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed to mount Windows share:
I tried to apply the work-around given here (min client protocol), but
am having trouble. It works if I put it into ~/.smb/smb.conf or
/etc/samba/smb.conf. However, for various reasons neither file is really
appropriate in my case. Instead, I would like to add it to a file that
is included from
Looks like the secondary problem is here is the same as
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1880305
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872286
Title:
gio - cifs mount
So does this silence mean people have tried to reproduce this but
couldn't or that they could and are working on it or that nobody has
tried?
I would have thought this kind of corruption is hinting at a possibility
of there being some possibility that this could be exploited and get a
bit more
Ok, it looks like the networkd crash & error message about enslaving a
bridge to a bridge was caused by the fact that the network file for one
of the bridge ports had a Match on MACAddress and came before the
bridge's own network file. Therefore, on restarting networkd matched the
port network
Public bug reported:
I just reinstalled my RPI3 router from Eoan to Focal but a lot of things
about networkd broke. I'm not sure whether they are related or not.
The first thing I noticed was, that I did not get my upstream DNS
servers. I use a dispatcher script to extract the information from
Same issue on Raspberry PI running Eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879559
Title:
net/bpfilter: remove superfluous testing message
To manage notifications about this bug go to:
Ok, this is interesting. I just downgraded to bionic (18.04) and now the
dongle is working! So something went wrong somewhere along the way but
the H/W is definitely good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The title kind of says it all.
libfakechroot:amd64 is the same version in 20.04 as it was in 19.10, but
libfakechroot:i386 is missing from the repo.
** Affects: fakechroot (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
BUT, if I manually download the versions that do work together from the
PPA, then kexec works!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840941
Title:
kdump fails to start with secure boot
And the PPA mentioned above now holds a set of packages with broken
dependencies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840941
Title:
kdump fails to start with secure boot enabled
To
Still an issue with 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840941
Title:
kdump fails to start with secure boot enabled
To manage notifications about this bug go to:
Ok, I tried again but changed the command with the version above to:
make SUBLEVEL=0 EXTRAVERSION=-46-generic modules_prepare
Now I get in dmesg:
[ 7851.540982] usb 10-1: new full-speed USB device number 4 using xhci_hcd
[ 7851.788016] usb 10-1: New USB device found, idVendor=0a12,
Here are the steps I followed (all on Eoan):
sudo apt install kernel-package linux-source flex bison libssl-dev libelf-dev
tar xf /usr/src/linux-source-5.3.0.tar.bz2
cd linux-source-5.3.0
make mrproper
cp /usr/lib/modules/5.3.0-46-generic/build/{.config,Module.symvers} .
make oldconfig
patch -p1
Gave it another try with linux-image-unsigned-5.7.0-999-generic on Eoan,
same behaviour.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873718
Title:
CSR8510 based BTA-402 Bluetooth device cannot
Sorry for the delay. I have just installed 20.04 to try but the
behaviour is the same.
Dmesg log when I plug in the dongle:
[ 230.119651] usb 10-1: new full-speed USB device number 3 using xhci_hcd
[ 230.375357] usb 10-1: New USB device found, idVendor=0a12, idProduct=0001,
bcdDevice=88.91
[
Public bug reported:
In the GUI, I can go to the Bluetooth settings and it shows BT to be
off. I turn on the little switch at the top but nothing else changes. If
I navigate away from this page and then back, the switch is off again.
If I try to reset the device on the command line I get:
Public bug reported:
I'm trying to report a bug about my Bluetooth dongle. I googled and was
directed to
https://help.ubuntu.com/stable/ubuntu-help/report-ubuntu-bug.html.en
for direction on how to do so. I followed the instructions on that page,
but they do not work:
1. I run ubuntu-bug
It looks as though this has been fixed in Ubuntu somewhere between
Bionic and Eoan. Shouldn't this bug be updated accordingly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599459
Title:
cannot
It seems it never made it from bionic-proposed to bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565448
Title:
[needs-packaging] User-mode-linux package missing in Ubuntu
To manage
Any chance to have this fixed in Bionic?
** Also affects: gcab (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gcab (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried to add gcab (to point out that the bug is, apparently, in
libgcab) for bionic, but I can't seem to select a particular release as
a target. So I removed it again since it probably didn't add any new
information.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Background:
Upon configuration the postinst maintainer script checks to see whether it
needs to convert the debconf variable install_devices from the old device name
format to the new 'by-id' format. It bases this decision on a version
comparison against the "previously
Is it really this hard to get 885 lines of code promoted into main?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776818
Title:
[MIR] vde2
To manage notifications about this bug go to:
I just logged into my system, the update-manager popped up and said
there where a number of updates. When I told it to install them it went
ahead, but in the middle of the update it reported that Ubuntu had
experienced a problem (the update went on though) and when I reported it
it offered me a
Also observed with 4.4.0-1054-raspi2. I'm now back on 4.4.0-1038-raspi2.
I think that one was ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade
Can somebody at least comment on whether this is expected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647298
Title:
kexec does not appear to work
To manage notifications about this bug go to:
For every-body who has this issue, the following command works around it
until the package maintainers find a solution:
sudo dpkg-divert --divert /lib/firmware/brcm/brcmfmac43430-sdio-2.bin
--package linux-firmware-raspi2 --rename --add
/lib/firmware/brcm/brcmfmac43430-sdio.bin
Please note that
linux-raspi2 version 4.4.0.1055.56 that is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To manage notifications about this bug go
This is still an issue in the current linux-raspi2 version. Where those
changes ported to that kernel?
** Also affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually it wasn't stuck. It has now tried to install 1.157.10 and
failed as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691729
Title:
linux-firmware-raspi2 conflicts with linux-firmware
I went ahead and raised a separate issue (1691729) in any case, just to
be sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578745
Title:
Update firmware for Raspberry Pi 3 support
To manage
Public bug reported:
I just tried to do a fresh install of xenial on a raspberry pi (I'm not
using a pre-made image but rather create a full install from scratch
using debootstrap etc) and it failed because it couldn't install linux-
firmware-raspi2 (1.20161020-0ubuntu1~0.2~rpi3) because the file
I'm not sure whether this is the right place for this, but I just tried
to do a fresh install of xenial on a raspberry pi (I'm not using a pre-
made image but rather create a full install from scratch using
debootstrap etc) and it failed because it couldn't install linux-
firmware-raspi2
Thanks Andy, that makes sense. I'm not aware of any other hooks having
problems. I have also neither checked apt-auto-remove nor noticed the
issue recently. So I'll take you word for it that the hook itself has
been fixed in which case we can close this one as Not-A-Bug or whatever
seems
Why doesn't linux-image-extra's postrm simply run update-initramfs. That
seems the more sensible thing to do as it is the same as with any other
package that wants to put things into the initrd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm also affected by this. The attached patch fixes the problem using
only posix shell mechanisms.
Please note that the paths in the diff are absolute to patch the problem
in-system.
** Patch added: "functions.diff"
I believe this happens because unattended-upgrades gets and releases the
lock a couple times (such as between installing upgrades and then
removing now no longer required automatically installed packages) and
dies if it cannot re-aquire the lock (rather than gracefully handling
it).
The high
Interesting. At the very least then the man page is inconsistent since
>From man resolv.conf, search option:
Resolver queries having fewer than ndots dots (default is 1) in them
will be attempted using each component of the search path in turn until
a match is found.
However, I believe the
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841173/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841175/+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/1674273
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841174/+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/1674273
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841176/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841169/+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/1674273
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841172/+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/1674273
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841168/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841167/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841170/+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/1674273
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841171/+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/1674273
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1674273/+attachment/4841166/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674273
Title:
apport information
** Tags added: apport-collected xenial
** Description changed:
This is a re-report of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/401202 since that
one was apparently closed as no-fix simply because it was too old.
This still occurs in xenial.
I don't think this is a recent regression. I have seen the symptoms for
a while and have only gotten around to investigating it yesterday. Also
see the linked bug which describes exactly this issue and which was
raised in 2009.
However, I am inclined to believe that this is more a glibc rather
As requested, I have filed
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/401202
Title:
Resolver ignores ndots option
To manage
Public bug reported:
This is a re-report of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/401202 since that
one was apparently closed as no-fix simply because it was too old.
This still occurs in xenial.
Original description:
Regardless of ndots option in /etc/resolv.conf, when NXDOMAIN
As a note: I believe this also affects the armhf kernel
4.4.0-1040-raspi2 for the Raspberry Pi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to
In addition this problem causes already installed machines to REMOVE
some packages on upgrade (when done using apt-get dist-upgrade)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661460
Title:
Public bug reported:
The latest xenial backports version of appstream has a breaks: gnome-
software (<< 3.22.5-1) in its control file, but there is no version of
gnome-software > 3.22 available in any xenial repos.
This causes the installation process to break when backports are
enabled.
**
Example excerpt of a debian installer log:
Feb 3 00:31:15 pkgsel: starting tasksel
Feb 3 00:31:19 in-target: debconf: unable to initialize frontend: Passthrough
Feb 3 00:31:19 in-target: debconf: (Failed to open fd 3: Bad file descriptor
at (eval 19) line 3.)
Feb 3 00:31:19 in-target:
Public bug reported:
I have been using kexec for quite some time on desktop and server Ubuntu
installations. Recently I've started using Raspberry Pi 3's for some of
the server tasks. Unfortunately I can't seem to get kexec working. I
have searched but found no mention of similar problems nor any
Honestly? I'm running (or trying to) Ubuntu server off of Raspberry Pis.
I don't need or want LXD. At least provide another task (minimal-server)
or something that we can use that pulls only in what is truly needed.
Right now the only choice I have is to try and figure out for each
package that
Dustin, this is assigned to you. Are you actually working on this?
** Changed in: ubuntu-meta (Ubuntu)
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563026
This was marked as a duplicate of #1250109, but it is not. This one is
about grub itself registering a trigger on its hook directory.
** This bug is no longer a duplicate of bug 1250109
Please use dpkg-triggers
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is still an issue in xenial. Any chance to get this fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409280
Title:
Graphviz's sfdp is seriuosly crippled without a triangulation library
Still an issue in xenial! I've added package 'linux' since that's the
source package that has the problem and I'm not sure how else to show
that this is a problem in trusty AND xenial (and probably everything in-
between).
** Also affects: linux (Ubuntu)
Importance: Undecided
Status:
Is there anything else I can do to get this fixed?
We have now gone through a couple of kernel versions all of which have
this bug. One of them had a problem which meant I couldn't use it and
this bug meant I couldn't just reboot into the previous kernel (because
it had been auto-removed).
I
I have attached an (untested) patch to fix this issue hoping that that
will prod it along a bit. The patch is against the sources of
`linux_3.13.0-67.110` as downloaded by an `apt-get source
linux=3.13.0-67.110` on 14.04.3.
Cheers,
Seb
** Patch added: "Change the image-extra post* maintainer
Same here. Could not reproduce the issue on 3.13.0-66.108 any more.
Cheers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501345
Title:
linux-image-3.13.0-65-generic breaks serial communication
To
Changed the package name to linux-lts-trusty as that what I've seen used
in other bug reports against the kernel for trusty even though the
source package for e.g. linux-image-extra-3.13.0-65-generic is listed in
apt-cache as linux. Feel free to change back if this is inappropriate.
** Package
Am I understanding this right that with the above proposed fix to
urllib3, python itself will go back up to version 3.4.3? I.e. the
archive revert is reverted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please note that not all people are "beached". I manage some 56 machines
and they regularly run apt-get update dist-upgrade and are pinned to
versions from a local mirror of the archive.
Those machines all downgraded python after the revert which broke a
large number of apps amongst them apport,
Looks like I can attach only one crash report per comment?!
** Attachment added:
"_usr_share_unattended-upgrades_unattended-upgrade-shutdown.0.crash"
Public bug reported:
Hi,
The postrm maintainer script in the binary packages linux-image-
extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of
those in /etc/kernel/postrm.d.
This can have all sorts of undesirable consequences depending on what
other packages add to those
Forgot to mention: I noticed it in 14.04.3 trusty kernel version
3.13.0-63.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501884
Title:
linux-image-extra-*-generic postrm script runs install
Brad, what's to diagnose? I've done all the diagnosis for you already.
Anyway, here's the relevant snippet from the dpkg log with the
problematic line highlighted:
(Reading database ... 149768 files and directories currently installed.)
Removing linux-headers-3.13.0-63-generic (3.13.0-63.103) ...
Sorry Brad. I didn't notice the 'Automatic Script' bit.
** 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/1501884
Title:
Interestingly it only happens the first time I run apt-get dist-upgrade
after running apt-get update:
seb@ws3559:~$ sudo apt-get update
Fetched 1,581 kB in 9s (167 kB/s)
seb@ws3559:~$ sudo apt-get dist-upgrade
Reading package lists... Done
This just started happening for me here. I'm on 14.04.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404783
Title:
warnings from apt: W: Unknown Multi-Arch type 'no' for package
'compiz-core'
I had icedtea-netx:i386 installed on my Ubuntu 14.04.2 amd64 system.
Trying to install icedtea-plugin failed due to a package conflict
between icedtea-netx:amd64 and icedtea-netx:i386 over the file
/usr/bin/policyeditor.
--
You received this bug notification because you are a member of Ubuntu
I'm seeing this on trusty 14.04:
root@ws3264:~# dpkg-reconfigure nvidia-331
Removing all DKMS Modules
/usr/sbin/dkms: line 1909: echo: write error: Broken pipe
/usr/sbin/dkms: line 1911: echo: write error: Broken pipe
Done.
update-initramfs: deferring update (trigger activated)
update-initramfs:
Public bug reported:
This is related to #396381 but probably slightly more specific.
Currently if any packages install or update files in /etc/grub.d, they
need to arrange for update-grub to be run via their postinst or similar.
I think the appropriate way would be for grub to register a trigger
What's the status on this? I've been wanting this for some time now too
and the comments left here are not very clear as to what the actual
stumbling block is for why this isn't fixed yet.
Connecting n VMs together without connecting them to the host and without being
root is possible in only
What's the status on this? I've been wanting this for some time now too
and the comments left here are not very clear as to what the actual
stumbling block is for why this isn't fixed yet.
Connecting n VMs together without connecting them to the host and without being
root is possible in only
Public bug reported:
I noticed that with Ubuntu Server 13.10 when I press the power button,
it flashes acpid exiting on the console and then does an immediate
hard poweroff. Filesystems are not umounted and require recovery on
restart.
Upon further investigation I found that apparently both
1 - 100 of 122 matches
Mail list logo
