Public bug reported:
Issue:
After switching to a VT it is only usable for a few seconds and then it blanks
out (goes completely black) but I can still write to it. Switching back to VT 7
(X11) and back to the VT I was using makes it usable again for a few seconds
before it blanks out again.
We would also like to see a backport to Trusty. Should we open a new bug
to request this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890784
Title:
Gnome-terminal continues to show outline cursor
Upstream bug report:
http://permalink.gmane.org/gmane.linux.usb.general/142154
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582759
Title:
Unexpected
Sure. I'll freshly image a HP EliteBook 840 with Xenial, run apport-
collect on it once all the updates are installed and then try the newest
mainline kernel.
** Tags added: apport-collected
** Description changed:
We are hitting an unexpected low write rate with Lexar JumpDrive P20
64GB
I'm happy to run apport-collect on a freshly installed machine if
necessary. If it is needed please let me know if you want the data from
a fresh Trusty, Xenial or Yaketi install.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because
Alberto, is there any update on the backport to Trusty?
We are particularly interested in the nvidia-340 backport as older
NVIDIA hardware doesn't work with newer drivers and albeit replacements
are steady we will still be stuck with that driver version for a while.
--
You received this bug
Awesome. Thanks, Alberto.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361207
Title:
nvidia-graphics-drivers-* should recommend nvidia-modprobe
To manage notifications about this bug go to:
@Alberto: Thanks. Will this also be backported to the long-term
supported 340 and 352 driver series?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361207
Title:
nvidia-graphics-drivers-* should
** This bug is no longer a duplicate of private bug 1300219
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300638
Title:
compiz crashed with SIGABRT in
__gnu_cxx::__verbose_terminate_handler()
Sorry. This one fell through my inbox cracks.
Yes, the proposed package works for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335017
Title:
Precise to Trusty dist-upgrade failure -
Public bug reported:
There has been some change between Precise and Trusty that lets this code
snippet behave differently:
Precise:
$ unset f ; f=abcd ; first_char=${f[@]:0:1} ; echo $first_char
a
Trusty
$ unset f ; f=abcd ; first_char=${f[@]:0:1} ; echo $first_char
\001
The solution is to
Public bug reported:
WPA supplicant version 2.2 has been released 4 months ago.
** Affects: wpa (Ubuntu)
Importance: Undecided
Status: New
** Tags: utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI: I've opened http:://pad.lv/1378884 to also update WPA supplicant to
2.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1351977
Title:
New upstream release 0.9.10.0
To manage notifications
Public bug reported:
nvidia-modprobe allows non-root users to load NVIDIA kernel modules and it
creates the respective device entries. This is important for CUDA users as they
would otherwise have to run a workaround script to load the kernel modules and
create the device entries. This is
Public bug reported:
Utopic uses the outdated Network Manager version 0.9.8.8.
Please update the version to 0.9.10.0 or at least 0.9.8.10.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: utopic
** Package changed: network-manager-applet (Ubuntu) =
Thank you, Rico.
Btw... Is there some checklist you usually follow to test if a release works?
If yes, where can I find it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336746
Title:
Thanks for the explantion about the 'linux-hwe-generic' package. It being
outdated explains why I was confused about it. ;-)
Just to make sure...
Is it correct that 'linux-hwe-generic' should then always depend on the latest
supported 'linux-generic-lts-*' package?
Also will 'open-vm-dkms-hwe'
Public bug reported:
I've encountered this issue during a Precise to Trusty dist-upgrade if
the package libticables-dev is installed.
Error message:
Unpacking libticables2-6:amd64 (1.3.4+dfsg-3) ...
dpkg: error processing archive
/var/cache/apt/archives/libticables2-6_1.3.4+dfsg-3_amd64.deb
apport information
** Tags added: apport-collected
** Description changed:
Hi everyone,
During a dist-upgrade from Precise to Trusty I'm hitting this issue:
Unpacking aide (0.16~a2.git20130520-2) over (0.15.1-5) ...
dpkg: error processing archive
Public bug reported:
I've encountered this issue during a Precise to Trusty dist-upgrade.
Error message:
Unpacking moreutils (0.50) over (0.45) ...
dpkg: error processing archive /var/cache/apt/archives/moreutils_0.50_amd64.deb
(--unpack):
trying to overwrite '/usr/bin/errno', which is also in
Public bug reported:
A Precise to Trusty dist-upgrade fails if the packages kdesdk-scripts
and subversion-tools are installed.
Error:
Unpacking kdesdk-scripts (4:4.13.0-0ubuntu1) over (4:4.8.5-0ubuntu0.1) ...
dpkg: error processing archive
Details:
Package: kdesdk-scripts
Installed version: 4:4.8.5-0ubuntu0.1
Candidate version: 4:4.13.0-0ubuntu1
Package: subversion-tools
Installed version: 1.8.8-1ubuntu3
Candidate version: 1.8.8-1ubuntu3
Conflicting files:
'/usr/bin/svn-clean'
So only one binary conflicts between these packages.
This also breaks dist-upgrades from Precise to Trusty if libltdl-
dev:amd64 and libltdl-dev:i386 are installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313958
Title:
Can't install i386
Public bug reported:
Hi everyone,
During a dist-upgrade from Precise to Trusty I'm hitting this issue:
Unpacking aide (0.16~a2.git20130520-2) over (0.15.1-5) ...
dpkg: error processing archive
/var/cache/apt/archives/aide_0.16~a2.git20130520-2_amd64.deb (--unpack):
trying to overwrite
I'm seeing this issue when I do a dist-upgrade via python-apt from
Precise to Trusty. Can the fix be backported to Precise?
Log snippet:
2014-04-25 11:34:17 INFO: apt: Processing package kdesdk-scripts (0.2040%)
2014-04-25 11:34:17DEBUG: dpkg: Unpacking kdesdk-scripts
(4:4.13.0-0ubuntu1)
Public bug reported:
During a dist-upgrade (via python-apt) from Precise to Trusty there is a
file conflict between kdesdk-scripts and pkg-kde-tools.
Log snippet:
Processing package kdesdk-scripts (0.2040%)
Unpacking kdesdk-scripts (4:4.13.0-0ubuntu1) over (4:4.8.5-0ubuntu0.1) ...
dpkg: error
Public bug reported:
Hi everyone,
On Trusty the dpkg error message trying to overwrite 'file' , which
is also in package pkg is not multi-arch compliant because it lacks
the architecture of foreign packages.
Current/faulty output from an amd64 install:
Preparing to unpack
Dimitri, I've found the issue! The installation of the libselinux1
package during the dist-upgrade from Precise to Trusty causes this
issue!
Here are the details from a freshly installed Ubuntu 12.04.4 amd64 VM:
$ sudo apt-get update -qq sudo apt-get dist-upgrade -qqy
no output; no updates
$
Workaround:
Before doing the dist-upgrade update the upstart package. Trusty's upstart
package has no issues with Trusty's libselinux1 package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303891
Friendly ping to Dimitri.
Dimitri, should I open a new bug for the new issue I've reported in comment #5
and #8?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303891
Title:
new initctl should
I've tested the new packages and I'm hitting a new issue:
$ sudo initctl reload dbus ; echo exit code: $?
initctl: Not running
exit code: 1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303891
Sorry for being impatient but when can I expect the fixed package to be
available?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303891
Title:
new initctl should fallback to old reload signal
Then I'll test it on Monday.
Thanks for fixing it so quickly. ;-)
Wish you a nice weekend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303891
Title:
new initctl should fallback to old reload
Thank you, Robie.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1301919
Title:
package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to
install/upgrade: trying to
Thank you, Robie.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301919
Title:
package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to
install/upgrade: trying to overwrite
Hi Robie,
I'm hitting this issue with a Python upgrade script that utilizes
python-apt and manual apt/dpkg calls if needed.
As test VM I'm using this setup:
1) Installed Ubuntu 12.04.0
(http://old-releases.ubuntu.com/releases/12.04.0/ubuntu-12.04-desktop-amd64.iso)
under VMware Workstation 10
Hi Robie,
I'm hitting this issue with a Python upgrade script that utilizes
python-apt and manual apt/dpkg calls if needed.
As test VM I'm using this setup:
1) Installed Ubuntu 12.04.0
(http://old-releases.ubuntu.com/releases/12.04.0/ubuntu-12.04-desktop-amd64.iso)
under VMware Workstation 10
New Upstart bug: https://bugs.launchpad.net/upstart/+bug/1303891
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301962
Title:
package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10
# initctl reload-configuration
# start bluetooth
start: Job failed to start
A simple reload of the Upstart config isn't enough. Upstart should do
this anyway as it gets notified via inotify.
# find /etc/init | xargs grep bluetooth -sl
/etc/init/bluetooth.conf
No Upstart jobs that use
And another round. This time I can really confirm that the missing
reload of the dbus service is the issue at hand.
Initial state:
# pidof bluetoothd
630
# dpkg --configure bluez
Setting up bluez (4.101-0ubuntu11) ...
reload: Method Reload with signature on interface
Public bug reported:
package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to
install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware-
user.desktop', which is also in package open-vm-toolbox
2011.12.20-562307-0ubuntu1
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package:
Public bug reported:
package whoopsie-preferences 0.11 failed to install/upgrade: trying to
overwrite
'/usr/share/polkit-1/actions/com.ubuntu.whoopsiepreferences.policy',
which is also in package activity-log-manager-control-center
0.9.4-0ubuntu3.2
ProblemType: Package
DistroRelease: Ubuntu
Public bug reported:
package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to
install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware-
user.desktop', which is also in package open-vm-toolbox
2011.12.20-562307-0ubuntu1
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package:
Public bug reported:
During an upgrade of a vanilla Precise install to Trusty I've
encountered already twice this issue:
$ sudo dpkg --configure bluez
Setting up bluez (4.101-0ubuntu10) ...
reload: Method Reload with signature on interface
com.ubuntu.Upstart0_6.Instance doesn't exist
The problematic part is in the bluez postinst script:
# Automatically added by dh_installinit
if [ -x /etc/init.d/bluetooth ] || [ -e /etc/init/bluetooth.conf ]; then
if [ ! -e /etc/init/bluetooth.conf ]; then
update-rc.d bluetooth defaults /dev/null
fi
So it's definitely not only touching the bluetooth Upstart job
configuration. 'console output' didn't give me much either. 'console
log' gave me this: Can't open RFCOMM control socket: Address family not
supported by protocol
--
You received this bug notification because you are a member of
Public bug reported:
Hi Mathieu,
Please include this upstream patch for Network Manager 0.9.8.8 in Trusty
to fix wrong IP6 addresses in dispatcher script environment:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-8id=3655e07f79c2b5fdb99fde6d4b9b185fd84cf11f
The
Workaround / Fix:
$ sudo sed -i 's|{stop|{ stop|g' /etc/init/cgroup-lite.conf
$ sudo dpkg --configure cgroup-lite
Setting up cgroup-lite (1.1.4) ...
cgroup-lite start/running
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
48 matches
Mail list logo
