Not so sure about it being "fixed" - I just encountered it when
attempting to (perhaps mistakenly) install apt-config-auto-update on
16.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490692
Still a problem in 16.04 LTS. Workaround is simply "aa-complain cupsd"
but that's kind of crummy...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558753
Title:
AppArmor denying CUPS
Appears to be the same bug as #1578193
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588862
Title:
legacy-only plugin does not load in Xenial
To manage notifications about this bug go to:
Public bug reported:
After installing network-manager-ssh package in 16.04 LTS, nothing new
appears in the Add Connection dialog box, but I do get this message in
the system logs:
Jun 03 09:58:40 sa1 gnome-session[27861]: ** Message: vpn:
(ssh,/etc/NetworkManager/VPN/nm-ssh-service.name) cannot
Confirming that this problem still affects 16.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages upon sudo
invocation
Ah... I had failed to notice the component from was universe. I believed,
incorrectly, that it was a Canonical-supported component.
I'll switch to SSSD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
nslcd(8) simply isn't reliable in a variety of situations.
https://bugs.launchpad.net/ubuntu/+source/nss-ldapd/+bug/227675
https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1029656
https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1374434
Public bug reported:
When using uri DNS in /etc/nslcd.conf, nslcd exits prematurely at boot
because network-manager hasn't finished configuring networking yet.
The relevant message is ONLY present in boot.log (nowhere else!), which made
troubleshooting this a pain in the butt.
CADT, anyone? As we're waiting for a fix to come out, the bug expires
because we're all waiting. I guess that's one way to solve the
problem...
** Changed in: nss-pam-ldapd (Ubuntu)
Status: Expired = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Per #54... yes, but for one thing: 14.04 LTS is still in the support
cycle for several more years, and we're just now starting to deploy
14.04 across the board for developer desktops at work.
Because I have more than one AD server, I'm using uri DNS (see
Fixed in Ubutun 14.10 (utopic).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254374
Title:
unable to install 13.10 on Intel RAID0 volume
To manage notifications about this bug go to:
Really? No-one comments on a bug for 60 days and it magically stops
being a bug? WTF, Canonical?
** Changed in: ubiquity (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
By bogus, I mean the graphical display is referencing partitions and
devices that don't/can't actually exist, and/or duplicate references to
the same partition or device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
and restoring,
which sounds equally appealing to me right now.)
--
-Adam Thompson
athom...@athompso.net
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254374
Title:
unable to install 13.10 on Intel RAID0
i have also tried numerous distro's and it so far does not work for me
in Ubuntu, Linux Mint, Zorin OS, Opensuse, Arch Linux, and Fedora (i
also have not tried any other distribution, JTLY)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Dell Precision T5400, all firmware up-to-date.
2 x 250GB HDDs, combined into a single RAID0 (striped) volume using Intel
onboard RAID.
(Note: the same system works fine if I attempt to install *without* the Intel
RAID volume configured.)
Ubiquity gets very confused with
** Attachment added: I wasn't joking about the modal dialog box title...
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+attachment/3915712/+files/Screenshot%20from%202013-11-24%2002%3A56%3A03.png
** Tags added: ubi-partman
--
You received this bug notification because you
I'd rank this problem as critical, since it utterly prevents me from
reinstalling Ubuntu on my primary workstation. There is no known workaround
(yet).
I have tried pre-partitioning the disk and pre-formatting the partitions, that
didn't make any difference. (In fact, ubiquity insists it's
That doesn't help me, as I need striping for speed, not reliability.
I see mdadm isn't present on the 13.10 live CD either, this completely
crippling my efforts to do it using md inside Linux.
Back to 12.04 I go for now, at least it mostly works.
--
You received this bug notification because
https://bugzilla.gnome.org/show_bug.cgi?id=693820
** Package changed: xserver-xorg-video-intel (Ubuntu) = nautilus
** Changed in: nautilus
Status: Invalid = New
** Project changed: nautilus = nautilus (Ubuntu)
** Bug watch added: GNOME Bug Tracker #693820
Same error. udev rules file previous modified to accomodate Brother
scanner drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952544
Title:
package libsane 1.0.22-7ubuntu1 [modified:
Public bug reported:
With a dual-monitor setup where monitor A is larger (higher-res) than B,
and A is positioned *above* B, centered;
And when the display of files on the Desktop (corresponding to ~/Desktop) is
enabled;
And the files are organized in a top-to-bottom, left-to-right direction
** Attachment added: Screenshot from 2012-08-09 00:04:10.png
https://bugs.launchpad.net/bugs/1034747/+attachment/3253975/+files/Screenshot%20from%202012-08-09%2000%3A04%3A10.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sad to say, folks, that I've been seeing this bug VERY intermittently on
multiple generations of hardware, although I think I can safely make these
assertions:
-only since GTK became widespread (this definitely did not occur back in the
Athena, Motif, OpenWindows, etc. days)
**specifically, I
** Also affects: deja-dup
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/844369
Title:
Deja-Dup backup to Ubuntu One failed
To manage notifications about
Ah, I see what you mean.
HP appears to be breaking that paradigm, however, in that they have UEFI
firmware that supports legacy mode booting, and that they seem to be shipping
systems with normal MBR-style partition tables that nonetheless have EFI boot
partitions.
My understanding of how
The EFI/BIOS distinction does apply to the Windows boot process, but it applies
ever earlier to the computer's IPL (initial program load - what the CPU
automatically starts executing after poweron). The presence or absence of an
MBR structure has no effect on whether a computer loads a legacy
pnp.ids hasn't been changed since 2009; I think it's safe to say that
part of the project is pretty much defunct. (It's sort-of maintained by
Red Hat, see http://fedorahosted.org/hwdata/.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Bryce: According to that page,
Required knowledge and tools
The rest of this page assumes that you know how to fetch a kernel from the
Ubuntu git repository, and build it, and that you have basic git skills. If you
can't do that yet, try starting with this wiki page.
So there's the
Public bug reported:
I think this is related to #749817, but perhaps a bit more specific.
Running up-to-date 11.04 as of Sat May 7 23:59:32 UTC 2011.
Using the Monitor applet, if I disable the internal display, the external
DisplayPort (DP) display also blanks and goes to sleep.
The only error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779279
Title:
Thinkpad X201 external DP monitor goes black if internal display is
disabled with Monitors applet
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 737891 ***
https://bugs.launchpad.net/bugs/737891
** This bug has been marked a duplicate of bug 737891
[Arrandale] gnome-display-properties unable to correctly enable monitors
connected to VGA
* You can subscribe to bug 737891 by following this link:
Not much to add besides me too, but I can specifically confirm that
using xrandr(1) does NOT trigger the problem, whereas using the GNOME
Monitors applet does trigger the problem. Also, the GNOME Monitors
applet produces some very bizarre geometry at times (half-height LVDS
screen, typically),
Sorry, forgot to add: this is in 2D classic mode, NOT with compiz
enabled, so I'm not hitting the 4096px problem. Nor do my two screens
together add up to 4096px anyway, so this is not merely the Arrandale
hardware limit that I'm hitting.
--
You received this bug notification because you are a
(You haven't included your email address in either of those complaints, nor
have you published your email address at your Launchpad page, which makes it
rather hard to reply directly to you. The bug tracker is not a forum for
people to simply post instructions for straightforward [and easily
I had the same issue, doing a fresh install of firebird2.1-classic on UNR10.04
(not an upgrade).
There was a defunct process with proctitle starting with
firebird2.1-something, I had to kill that *and* its companion frontend
process before synaptic would continue.
Manually running
Also confirming that with Intel BIOS LF94510J.86A, Ubuntu 9.04 (64-bit)
installs and operates correctly.
Note that even with updated BIOS, I am unable to correctly boot or operate the
8.10 OS release.
On the other hand, going WAY back to an old v6 disc I found, works fine
(presumably due to
Confirming that this problem affects me on an Intel D945GCLF2, a mini-ITX
i945/ICH7 with a dual-core Atom 330. Kernel panics *immediately* after boot
from 8.10 AMD64 install CD. (By immediately, I mean that by the time my CRT
finishes switching modes, I already have a stack trace on screeen -
Oddly enough, this works on my Mythbuntu (gutsy) system at home, but breaks on
my Ubuntu (gutsy) system at work. Obviously those two environments are
completely different, lending credence to the belief that it's dependant on
something local to the system.
I see this all the time from inside
39 matches
Mail list logo
