No replication of this bug possible.
Tested by installing a clean VM and then installing AICCU package,
debconf asks for password. Then install it again, and debconf does not
ask for it, as the username/password are stored in debconf and
aiccu.conf.
** Changed in: aiccu (Ubuntu)
Status:
One also has to go to the website for this, little the package can make
clearer.
** Changed in: aiccu (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797268
Saw a bunch of at-spi2 errors in .xsession-errors. Reinstalled at-
spi2-core, and those errors went away. Still no desktop. Deleting
.config/dconf/user did the trick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
sudo cp /opt/google/chrome-beta/libwidevinecdm* /usr/lib/chromium-
browser/
Installed your ppa, upgraded, no effect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371274
Title:
Unable to use the
After another reboot this effect seems to have gone away. So I still
don't have my native resolution available by default, but at least I can
get it back by defining it with xrandr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hurray, the problem just got a little worse!
After the upgrade to kernel 3.19.0-14.14, when I define my monitor's
native resolution using xrandr, I get the right *resolution* but still
not the right number of *pixels*. So I'm getting (as far as I can see)
one logical pixel per physical pixel on
Correction: that last upgrade was *from* 3.19.0-14.14, not *to* it. It
was the upgrade to 3.19.0-15.15.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer
Janne, good point. There's another possible workaround in certain
circumstances. You can also clear the auditd rules which should allow
you to continue working on a running system. This would be done by
issuing an auditctl -D, after which you should be able to use the
running system, albeit
I found a driver on debian: https://wiki.debian.org/alx#Installation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383184
Title:
Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
Public bug reported:
When removing the headphones while listening to music it pauses, as
intended. Yet after I receive a phone call any time later, music starts
playing on speaker immediately after ending the call. This also happens
when the call is not answered.
Phone: BQ Aquaris E4.5 OS
Did you stop AICCU? Or otherwise terminate it?
As that code path would sigsegv when there is a race in the shutdown
where the tun_reader thread is still going and g_aiccu is set to NULL as
the process is shutting down.
More details on the events surrounding would be useful.
More importantly:
So to be clear: my desktop is still utterly broken, but the one on an
installer disc for the same version is not. Hopefully there is a simple
configuration problem. I haven't done anything very special, I thought.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After some searching, I found a comment suggesting that resetting my ATI
graphics driver using aticonfig --initial might help. I did that, and
now I get slightly further.
Now when I log in I get the basic file management functionality on the
desktop: icons and a context menu. But no Unity
A piece of good news: I did get a working desktop when booting from the
14.10 installer, for the same architecture.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437765
Title:
No desktop after
While the system is in this state, ps does show a compiz process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437765
Title:
No desktop after upgrade to 14.10
To manage notifications about this
Public bug reported:
After upgrading my desktop machine from 14.04 to 14.10, I no longer have
a desktop. The login screen works, but after logging in, I get just the
backdrop image and a mouse pointer. Nothing else.
The pointer responds to mouse movements, and I can switch to a text
console
Well, I did some bisecting but the results are disappointing. Actually
I ended up trisecting. On Saucy, kernel...
3.11.0-12 was OK. Recognised my full native resolution and enabled it
by default. Wonderful.
3.11.0-13 to 3.11.0.24 inclusive were completely messed up. They booted
in some
Public bug reported:
Trying to install this on a 15.04 system, together with the generic
kernel image, in order to see if it makes a regression since 14.04 go
away (bug 1300557).
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fwts-efi-runtime-dkms 15.03.00-0ubuntu1
Trying 13.11.0-17. There was a problem while installing linux-headers
though... fwts-efi-runtime-dkmis 15.03.00-0ubuntu1: fwts-efi-runtime-
dkms kernel module failed to build. Somewhere along the way it said:
run-parts: executing /etc/kernel/postinst.d/dkms 3.11.0-17-generic
Okay, I got a seemingly successful install of the last Saucy kernel.
But it's not working very well: I get a super-low-res login screen, and
the system doesn't respond to keyboard or mouse. (It does notice the
power button, so it's not frozen). This happens both with the default
boot on that
I could temporarily swap out the hard drive and install Saucy on the
spare. More after the weekend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
The latest upstream version I found there was v4.0-rc4-vivid. It boots,
but it doesn't fix the problem.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.0-rc4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The version that was installed on March 31 was 3.13.0.20.24. The
version I uninstalled right after that was 3.13.0.18.38.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen
According to the dpkg.log for that date, quite a lot: libc-bin for
amd64. Also gcc-4.8, gcc-4.9, along with g++, cpp, libgcc1, libstdc++6
etc, for amd64 and i386; and libitm1, libgomp1, libgfortran3, libasan0,
libatomic1, libtsan0, libquadmath0, libthumbnailer0, apport, apport-gtk,
Something happened to this bug's conversation: the message asking me to
upgrade the BIOS has been removed/hidden.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no
I first upgraded to 14.10; that didn't change anything. Trying 15.04
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notifications
No change in 15.04. I can add the resolution with xrandr, and after
that I can use it. But after reboot, I have to do it again.
The upgrade got stuck with a black screen and no networking, but I
eventually got out of it with the apt-get dist-upgrade dance from the
console. I hope that hasn't
I'm trying the BIOS upgrade as per those instructions. The only
applicable option was the flashrom one, which seems to have hosed my
BIOS. It's still on now, but I won't be able to boot it again. Kindly
mark this bug New again to give me time to recover and retry!
--
You received this bug
Okay, I got out of that situation with the help of the flashrom people.
My BIOS is now updated.
It helped a bit in that I can now define and add my resolution again
using xrandr. It won't stay added though: I need to define and add it
every time I boot. Otherwise, the resolution is not in the
Public bug reported:
Rhythmbox freezes when i seek forward in a m4a file.
It stops at the timestamp i forward it to.
Ubuntu version: 14.04
Rhythmbox Version: 3.0.2-0ubuntu2+grilo
I expected it to seek forward in the song.
What happened instead was that it froze Rhythmbox.
** Affects:
I'm still having this problem after updating to 14.10.
This issue exclusively arises if I suspend my laptop when connected to
the power cord, then unplug it during suspend and wake it up on battery.
It does not happen every time, maybe once in seven times.
The scaling_governor keeps all cores at
Running 3.13.0-40-generic triggering this as well:
kernel: [ 11.095358] nvidia: module license 'NVIDIA' taints kernel.
kernel: [ 11.095361] Disabling lock debugging due to kernel taint
kernel: [ 11.100122] nvidia: module verification failed: signature and/or
required key missing -
** Changed in: maas
Status: In Progress = Fix Committed
** Changed in: maas (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas
Status: In Progress = Fix Committed
** Changed in: maas (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373261
Title:
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas
Status: Triaged = In Progress
** Branch linked: lp:~jtv/maas/bug-1373261
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas
Status: Triaged = In Progress
** Branch linked: lp:~jtv/maas/bug-1373261
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
- Reconfiguring between an IPv4-based and an IPv6-based MAAS_URL broke the
- ‘generator’ setting in my pserv.yaml: it ended up being the full IPv4
- netloc, with most of the IPv6 netloc tacked onto it.
+ Reconfiguring when the existing MAAS_URL used an IPv6 host address
** Description changed:
- Reconfiguring between an IPv4-based and an IPv6-based MAAS_URL broke the
- ‘generator’ setting in my pserv.yaml: it ended up being the full IPv4
- netloc, with most of the IPv6 netloc tacked onto it.
+ Reconfiguring when the existing MAAS_URL used an IPv6 host address
now contains...
generator: http://10.9.9.1:caf5:2922:8b1f::1]/MAAS/api/1.0/pxeconfig/
Note how the first part of the netloc, up to the first colon, is
replaced with the new address — but the rest of the netloc is still
there.
** Changed in: maas
Assignee: Jeroen T. Vermeulen (jtv
now contains...
generator: http://10.9.9.1:caf5:2922:8b1f::1]/MAAS/api/1.0/pxeconfig/
Note how the first part of the netloc, up to the first colon, is
replaced with the new address — but the rest of the netloc is still
there.
** Changed in: maas
Assignee: Jeroen T. Vermeulen (jtv
There doesn't seem to be any need to install with the C locale;
en_US.UTF-8 works just as well. As does installing the language pack(s)
to match the session's locale settings. The real problem is that we
have no hook for doing either before apt installs our dependencies: it
installs the
I agree: this is a clear-cut case for the request-an-address API, but we
still lack a request-a-hostname API.
Out of curiosity, how did the existing setup(s) obtain these generated
hostnames in the first place? To my knowledge they were neither exposed
nor documented. MAAS never had much
Ah, I see that using the IP address is not an option in this case. So
we'll have to add a way to manage DNS entries.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1382190
Title:
Ah, I see that using the IP address is not an option in this case. So
we'll have to add a way to manage DNS entries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382190
Title:
LXCs assigned IPs
I agree: this is a clear-cut case for the request-an-address API, but we
still lack a request-a-hostname API.
Out of curiosity, how did the existing setup(s) obtain these generated
hostnames in the first place? To my knowledge they were neither exposed
nor documented. MAAS never had much
MAAS trunk no longer includes Avahi, so closing this bug there.
** Changed in: maas
Status: Triaged = 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/1251257
Title:
[SRU] avahi
To compile nfdump with PCAP support (tested on Trisquel 7.0):
$ apt-get source nfdump
- cd to the directory nfdump-1.6.8p1 (or whatever your version number may be)
- change debian/rules to add an extra configure option --enable-readpcap:
DEB_CONFIGURE_EXTRA_FLAGS += --enable-readpcap
- change
traffic or change
DNS can break the TIC procedure already, in a same way they can perform
that attack on the actual tunnel.
Note that the actual tunnels are also in clear text. If the adversary
can redirect/intercept traffic, they can better target that.
Greets,
Jeroen
--
You received this bug
Public bug reported:
When I “make package” (with trunk r3227 and packaging r317) I get this
error:
«
patching file contrib/maas_local_settings.py
Hunk #2 FAILED at 81.
1 out of 2 hunks FAILED
dpkg-source: info: fuzz is not allowed when applying patches
dpkg-source: info: if patch
Public bug reported:
When I “make package” (with trunk r3227 and packaging r317) I get this
error:
«
patching file contrib/maas_local_settings.py
Hunk #2 FAILED at 81.
1 out of 2 hunks FAILED
dpkg-source: info: fuzz is not allowed when applying patches
dpkg-source: info: if patch
Public bug reported:
There is an option 'disable touchpad when typing' in the mouse settings
menu. However setting this options has no effect on my HP ProBook 6560b
running Ubuntu 14.04 LTS, and as a result the cursor/focus moves
frequently to other controls/windows while typing which is quite
This problem persists in 14.04 for me as well. One of the two Google
accounts I add will fail even during the same session with the
authorisation required error.
I have stopped using Empathy and the Online Accounts configurator
completely due to this bug, although I give it a go whenever I move
Could this be bug 1186662? The main packaging branch has a workaround
for that which is worth a try.
It's a matter of adding this line to /etc/apparmor.d/dhcpd.d/maas:
capability dac_override,
...and then reloading the apparmor config.
--
You received this bug notification because you
Could this be bug 1186662? The main packaging branch has a workaround
for that which is worth a try.
It's a matter of adding this line to /etc/apparmor.d/dhcpd.d/maas:
capability dac_override,
...and then reloading the apparmor config.
--
You received this bug notification because you
The first time it takes 60 seconds to log in, and it seems that
networking is broken during that time.
Subsequent logins take only three seconds, and also see almost no
downtime in networking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes, it takes roughly 60 seconds before networking is started.
Hibernation would not be an option for us, the hardware is capable of
resuming, and the subsequent attempts show that it should be able to do
so quickly.
Attached is a log again of login, suspend, and resume cycles.
16:02:27 the
Just a note, I'm not 100% certain that it was completely broken before
the bios update. It could very well be that it had the same 60 second
delay. Then again, that long a delay means broken in my eyes anyway. No
user is going to wait that long to log back in every time his system
suspends.
--
We have upgraded the BIOS of the machine:
# sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
A18
04/30/2014
We now find that after a reboot, the first suspend and resume cycle
takes long: after pressing enter in the password screen it takes about
60 seconds to either log that
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352379/+attachment/4169576/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
Title:
Public bug reported:
We use Dell Optiplex 7010 machines in our student lab. These machines
are capable of suspending and resuming, so that we don't waste power
during the night. In our lab we also use LDAP authentication for the
students. The problem is that networking is disabled once the
apport information
** Tags added: apport-collected trusty
** Description changed:
We use Dell Optiplex 7010 machines in our student lab. These machines
are capable of suspending and resuming, so that we don't waste power
during the night. In our lab we also use LDAP authentication for the
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169655/+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/1352379
Title:
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169653/+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/1352379
Title:
Network
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169662/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169659/+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: ProcModules.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169660/+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/1352379
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169658/+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/1352379
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169654/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169657/+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/1352379
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169661/+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/1352379
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169663/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169651/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1352379/+attachment/4169656/+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/1352379
Title:
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
Title:
Network broken after resume
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722377
Title:
[Dell Latitude E6400] Switch display Fn+F8 not working
To manage
This problem has not been solved yet it appears. I can confirm it is not
working on a Dell Latitude E5440 with Ubuntu 12.04 LTS, kernel
3.11.0-24-generic. The FN-F8 key is still not working correctly. I get
similar key scan codes as JeffH posted:
I pressed FN-F8 twice here, and then FN-Arrow up
I'm sure after all this time the problem no longer exists. Nor does the
system it happened on.
** Changed in: libburn (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
First line of /etc/init/network-interface-container.conf in 14.04
states:
# network-interface-container - woarkound for missing events in
container
This should be:
# network-interface-container - workaround for missing events in
container
** Affects: ifupdown (Ubuntu)
No, my hypothesis doesn't look correct. We don't see anything that
would make prepare() jump into the reactor thread.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1308069
Title:
New hypothesis: the code in DatabaseLock opens, and closes, a cursor for
each locking/unlocking command. Do we actually know that these cursors
will be in the same database session? If the command failed, do we know
that we would see an error?
--
You received this bug notification because you
No, my hypothesis doesn't look correct. We don't see anything that
would make prepare() jump into the reactor thread.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308069
Title:
New hypothesis: the code in DatabaseLock opens, and closes, a cursor for
each locking/unlocking command. Do we actually know that these cursors
will be in the same database session? If the command failed, do we know
that we would see an error?
--
You received this bug notification because you
It happened again. I suspect that it may be a matter of ordering of
decorators: RegionAdvertisingService.prepare is decorated as
@synchronous, and *then* as taking two locks.
Given decorators' wrapping behaviour, which reverses the order of
entrance, I understand that to mean: grab these two
It happened again. I suspect that it may be a matter of ordering of
decorators: RegionAdvertisingService.prepare is decorated as
@synchronous, and *then* as taking two locks.
Given decorators' wrapping behaviour, which reverses the order of
entrance, I understand that to mean: grab these two
The issue is likely caused by an attempt to remove Evolution from my
system (I wouldn't expect the system panel got weed out by removing
Evolution though). I faced the same problem on another machine where I
removed Evolution from the standard Ubuntu install. This issue can
therefore be closed as
Public bug reported:
When I open the System Settings panel most of the regular settings are gone.
The only things left are Language, Security, Printers, Firewall (added by
gufw), Landscape services, Software and Updates.
See attached image.
After a reboot I have the same and other accounts
ppa's from Chrome and Dropbox, and used
Grive in the past.
Regards,
Jeroen
On 23 May 2014 11:18, Iain Lane i...@orangesquash.org.uk wrote:
Hello Jeroen,
The desktop System Settings is called unity-control-center, not
ubuntu-system-settings, so I've reassigned this bug there.
It sounds like
Quick fix: change user angent to:
UCCAPI/15.0.4481.1000 OC/15.0.4481.1000 (Microsoft Lync)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950790
Title:
Pidgin-sipe connection error after upgrade to
Public bug reported:
Breakage during installation, on a fresh (near-pristine) amd64 14.04
system.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libclang1-3.5 1:3.5~svn201651-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
** Branch linked: lp:~jtv/maas/revert-bug-1311433
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
** Branch linked: lp:~jtv/maas/1.5-revert-bug-1311433
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
*** This bug is a security vulnerability ***
Public security bug reported:
Users of which the home folder is encrypted using the CLI (unfortunately
there is no GUI option for this, see
https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1279766), and for which the 'login without
** Branch linked: lp:~jtv/maas/revert-bug-1311433
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
attribute '__module__'
** Branch linked: lp:~jtv/maas/1.5-revert-bug-1311433
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
attribute
** Description changed:
+ [Test Case]
+ No test case; the code that's being patched is only a test and does not
actually appear in the package.
+
+
+ [Description of the problem]
+
This happened when trying to land a documentation-only branch:
** Description changed:
+ [Test Case]
+ No test case; the code that's being patched is only a test and does not
actually appear in the package.
+
+
+ [Description of the problem]
+
This happened when trying to land a documentation-only branch:
Public bug reported:
I just upgraded a desktop system from 13.10 to 14.04, and to my horror
found that the monitor's native resolution was no longer supported: the
best setting offered was 1024×768 or somesuch.
Turns out the upgrade deleted xorg.conf. There were two backups: one
with the date
Also, I don't know if these are related, but window menus now appear not
only at the top of the screen or in the window's title bar (depending on
the new configuration setting in 14.04), but also in the classic pre-
Unity location: right below the window's title bar.
--
You received this bug
201 - 300 of 1329 matches
Mail list logo
