** Description changed:
Saw this on 162 and 163
MX4
+ also on krillin and mako
Get the update and reboot to install, open the greeter, there is a blank
screen with just the bottom edge hint
touch the screen and it displays the scope contents immediately
- Also reproduces
** Branch linked: lp:ubuntu-cdimage
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1363482
Title:
ubuntu-keyring includes 1024D keys
Status in Ubuntu CD Images:
Peter: Manually modifying the file per comment #9's fix worked for me on
14.04. But I am still having lots of problems with the GPUs on my
laptop. Also had to use xorg-edgers ppa to get hardware acceleration
back, otherwise X complained about unknown chipset. Also, the newest
kernel versions (like
@Pat
We might want to hotfix this once we come to fully understand it( and I
think we're getting close ).
While working with tvoss a fixes to location-services, we realized that
by default, the get-all-match.py script only outputs warnings. While
reviewing a test run from tvoss, I didn't see
Stephane,
Juju doesn't decide what images to use directly. It uses ubuntu-cloudimg-query
for that.
So this utility will need to be changed. It is in the cloud-image-utils package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Bug #1515463 reveals that this change broke Juju. Marking as
verification failed.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer
Opening a task on systemd as well for this.
When called early in boot, mount.nfs may fail because of any number of
problems with the network. In this case, it appears it's being called
by systemd before /etc/resolv.conf has been set up, resulting in a
temporary DNS failure. There is no way for
I can confirm that this bug is eliminated in 15.10.
Unfortunately another old bug reappeared (random disconnect).
I will look into this in more detail.
For me it is solved.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Iain,
This 'bug has been around for a long time now and the information that
is on or comes back from the forum is inadequate and in one instance
rendered my computer unbootable.
In the end I moved back to Windows 7 for all my serious work and now use
Ubuntu 14.04 for anything that I'm
On 11 November 2015 at 19:36, Ian Bruntlett
wrote:
> To test this PC I reinstalled lubuntu 15.10 64-bit and used Synaptic
> Package manager to install a few bits and pieces.
>
> The PC is behaving much better now and graphics are OK.
>
PC graphics are still misbehaving.
Hello Stéphane, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package coreutils - 8.23-3ubuntu1.1
---
coreutils (8.23-3ubuntu1.1) vivid; urgency=medium
* Add support for correctly processing /proc/self/mountinfo.
* Fix df to prioritize mounts of the root of a device over bind mounts.
(LP: #1432871)
-- Dave
This bug was fixed in the package ido - 13.10.0+14.04.20151021-0ubuntu1
---
ido (13.10.0+14.04.20151021-0ubuntu1) trusty; urgency=medium
* IdoCalendarMenuItem: add crash guard on
ido_calendar_menu_item_key_press (LP: #1350821)
-- Marco Trevisan (Treviño)
Hello Daniel, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: pcsc-lite (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1515318
Title:
package pcscd 1.8.14-1ubuntu1 failed to
Hello Brian, or anyone else affected,
Accepted whoopsie into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/whoopsie/0.2.47.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Brian, or anyone else affected,
Accepted whoopsie into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/whoopsie/0.2.24.6ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello dann, or anyone else affected,
Accepted libffi into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libffi/3.1~rc1+r3.0.13-12ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The bug affects me too and in my case it is serious because my wifi
connection is unstable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1448555
Title:
Hi,
To test this PC I reinstalled lubuntu 15.10 64-bit and used Synaptic
Package manager to install a few bits and pieces.
The PC is behaving much better now and graphics are OK.
Just in time to be given away to a friend who's PC's hard drives has failed
:)
BW,
Ian
--
-- ACCU -
Public bug reported:
When rsyslog is managed by the init script, it symlinks its PID to
/run/sendsigs.omit.d so that we can capture logs very late during the
shutdown sequence:
sendsigs_omit() {
OMITDIR=/run/sendsigs.omit.d
mkdir -p $OMITDIR
ln -sf $PIDFILE $OMITDIR/rsyslog
}
When rsyslog
** Branch linked: lp:ubuntu/trusty/modemmanager
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded modems
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity8 (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
The verification of the Stable Release Update for ido has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for coreutils has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
apt-cache policy qtdeclarative5-qtmir-plugin
qtdeclarative5-qtmir-plugin:
Installed: 0.4.6+15.04.20151110-0ubuntu1
Candidate: 0.4.6+15.04.20151110-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
In the upstart case, simply removing the "stop on runlevel [06]" clause
is enough to capture the log output of the shutdown sequence.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libffi in Ubuntu.
https://bugs.launchpad.net/bugs/1513958
Title:
arm64: failure with small objects
This one has annoyed me for quite a while now (well before 15.x). Having
to disable/enable wifi to get network manager applet to see the wifi
ssid (or wait quit a while) is a bit of a pain and shouldn't be
necessary for a modern OS. Also, the fact that there is no way anywhere,
either in
the full computer model that I found is: Samsung np-r540-ja07pl
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1512454
Title:
Refresh change colours
Status in xorg package
A simplification of this workaround is:
echo "stop on never-dies" >> /etc/init/rsyslog.override
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1515379
Title:
rsyslog
Subscribing sponsors and sru team, as both are still necessary for
Trusty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1432871
Title:
`df` shows bind mounts instead
OK, verified that Pat didn't see this on 161, i flashed on MX4 and i didn't see
either.
all the qtmir/qtubuntu updates were already in 161 so i updated and witnessed
the problem
here were the list of updates
The following packages will be upgraded:
coreutils dialer-app indicator-sound
This bug was fixed in the package dialer-app -
0.1+16.04.2015.1-0ubuntu1
---
dialer-app (0.1+16.04.2015.1-0ubuntu1) xenial; urgency=medium
* Make sure the account label is selected on the live call. (LP:
#1515012)
-- Gustavo Pichorim Boiko
** Summary changed:
- rsyslog not omitted by sendsigs when managed by upstart/systemd
+ rsyslog stopped too early during shutdown/reboot
** Description changed:
+ The upstart job managing rsyslog includes a "stop on runlevel [06]"
+ clause that makes it terminate very early during the
scratch that - retested fresh 161 and i see the issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1515356
Title:
After a boot the dash doesn't display until touched
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Happening for me with the latest 5.4.3 in Wily.. off to hunt for an
upstream bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1452004
Title:
Pulseaudio network
This LTS Enablement Stack scares me a lot; I do not want to screw my
system. So if I understand you correctly, I should return to my
previous state with the following command, right?
sudo apt-get remove linux-generic-lts-vivid xserver-xorg-core-lts-vivid
xserver-xorg-lts-vivid
arnett@UbunutuLinuxLTS-Gateway-NE56R41u-NE56R:~$ sudo apt-get --purge
autoremove[sudo] password for arnett:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
4 not fully installed or
Just tested with Xenial server, with no additional packages installed.
vim is the last thing keeping libpython2.7 on the server image. Verify
with `apt-get purge python2.7 libpython2.7`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
from fresh install of 15.10
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: python3-apport 2.19.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CrashReports:
I tried the Live version of Ubuntu 16.04 and installed the DisplayLink
driver. But I couldn't even select the third monitor which is plugged in
through DisplayLink. So I can't tell if the problem exists there too as
the driver for the video output via DisplayLink seems not to work. At
least I
201 - 244 of 244 matches
Mail list logo