So the device management issues in kde were unrelated to upower 0.99,
which leaves the suspend issues with upstart where I'm working on a fix.
** Package changed: kde4libs (Ubuntu) = kde-workspace (Ubuntu)
** Changed in: kde-workspace (Ubuntu)
Status: New = In Progress
--
You received
Fixed in upstream git
** Changed in: kde-workspace (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
Public bug reported:
From an utopic - vivid upgurade. The package can now be neither removed
nor upgraded:
Preparing to unpack .../libdb5.3-java_5.3.28-7_all.deb ...
dpkg-maintscript-helper: error: original symlink target is not an absolute path
dpkg: error processing archive
Nvm, dpkg was not upgraded before libdb5.3-java which caused the
failure.
** Changed in: db5.3 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to db5.3 in Ubuntu.
** Description changed:
upower 0.99 needs uploading for gnome 3.12. This bug tracks the
transition.
A transition is required as some features were removed and the SONAME
was changed
Some packages are staged in
https://launchpad.net/~noskcaj/+archive/upower/+packages
Public bug reported:
Probably a dup of #1430675
After upgrading to vivid with systemd my network bridge isn't configured
on boot:
$ systemctl --all |grep ifup
● ifup-wait-all-auto.service
loadedfailed
** Changed in: apport (Ubuntu)
Importance: Undecided = Medium
** Changed in: apport (Ubuntu)
Milestone: None = ubuntu-15.04
** Tags added: kubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
I tried again on current vivid, br0 is still not auto-starting. Here's
the logs
** Attachment added: iflogs.log
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+attachment/4358701/+files/iflogs.log
--
You received this bug notification because you are a member of Ubuntu
Touch
** Tags added: kubuntu
** Project changed: apport = apport (Ubuntu)
** Changed in: apport (Ubuntu)
Milestone: None = ubuntu-15.04
** Changed in: apport (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags added: kubuntu
** Changed in: apport (Ubuntu)
Importance: Undecided = Medium
** Changed in: apport (Ubuntu)
Milestone: None = ubuntu-15.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** Changed in: akonadi (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1440501
Title:
Can not load mysql-akonadi
** Tags added: kubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in ubuntu session when using nvidia drivers via
nvidia-prime
David Edmundson pointed out that this was also discussed by the kde developers
suggesting to switch back to UXA from SNA on intel
https://mail.kde.org/pipermail/kde-distro-packagers/2015-August/88.html
the freedesktop bug also seems to have a workaround attached to it
** Tags added: kubuntu
So it turns out that is already known upstream..
** Bug watch added: freedesktop.org Bugzilla #86281
https://bugs.freedesktop.org/show_bug.cgi?id=86281
** Changed in: mesa
Importance: Undecided => Unknown
** Changed in: mesa
Status: New => Unknown
** Changed in: mesa
Remote
Public bug reported:
I have an nvidia optimus notebook, and since yesterdays updates X
crashes on the nvidia driver, so I switched to intel. But now, every
couple minutes plasmashell crashes with
Thread 1 (Thread 0x7f7b245c6800 (LWP 5307)):
[KCrash Handler]
#6 brw_meta_fast_clear
Ok, after adding mesa 11.0.0 I haven't seen this crash for 2 days now.
So I guess the patch helps as I had this crash several times per day
before that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Changed in: kaccounts-providers (Ubuntu)
Milestone: xenial-updates => ubuntu-16.04
** Changed in: ktp-accounts-kcm (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-16.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: kaccounts-integration (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kaccounts-integration (Ubuntu)
Importance: Undecided => Critical
** Changed in: kaccounts-integration (Ubuntu)
Status: New => In Progress
** Changed in: kaccounts-integration
** Changed in: gcr (Ubuntu)
Milestone: None => ubuntu-16.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcr in Ubuntu.
https://bugs.launchpad.net/bugs/1561778
Title:
Kubuntu 14.04 -> 16.04 freezes kvm
Status in
Public bug reported:
I did 2 attempts to upgrade Kubuntu 14.04 to 16.04 during the Beta2 tests in
KVM and both runs froze the VM once the upgrader reached
Configuring libgck-1-0 (amd64)
I'll see if I can find any more information about this
** Affects: gcr (Ubuntu)
Importance: Undecided
The network-manager 1.2 package seems to cause different symbol exposure in
networkmanager-qt which caused the broken 15.08.0-0ubuntu1.2 package in bug
#1569674
I'm still investigation where that exactly comes from, but building
networkmanager-qt against xenial-release works fine.
--
You
@Aron: No, it doesn't. But now I found out that it's not NM's fault but
caused by a strict "1.2.0" version check in nmqt which is supposed to
remove some API for 1.2, but ofc. didn't catch 1.1.93. I'm talking to
upstream how to resolve that, but this bug can proceed fine.
--
You received this
This sounds like it's related to the move of the icons from the
applications to the icon theme, and the applications not having any
safety measures for making sure one is actually installed. Lets see if
we can figure something out for yakkety (and xenial)
** Tags added: xenial yakkety
** Changed
I did manage to reproduce this after all.
First thing: 234-2ubuntu10 indeed solves the problem in my manual test
at least.
All you need to do to reproduce this is start an artful container:
docker run -ti ubuntu:artful bash
then install systemd in it:
Setting up systemd (234-2ubuntu9) ...
ln:
For clarification, the environment the containers run with is:
privileged: false,
cap_add: ['SYS_ADMIN'],
security_opts: ['apparmor:unconfined']
(see https://git.launchpad.net/~kubuntu-ci-admins/kubuntu-ci/+git
/pangea-tooling/tree/kci/imager.rb)
what's not helpful is that running debootstrap
25 matches
Mail list logo
