This forgotten issue still exists, also in Disco.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1789022
Title:
libcaca0 still depends on old libncursesw5 and libtinfo5
S
Public bug reported:
Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet
dependencies.
Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version
is login (1:4.5-1ubuntu1).
** Affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
*
The dependencies must be corrected or newer login version must be built.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811812
Title:
Util-linux will not install - unm
** Changed in: util-linux (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811812
Title:
Util-linux_2.33.1-0.1ubuntu1 will not ins
This is definitely not an invalid bug report. It is not a support request nor
spam.
Steve wrote: "util-linux will be migratable to the disco release pocket".
This simply is not true.
This bug is for util-linux_2.33.1-0.1ubuntu1 and this package cannot be
installed (not migratable to release pocke
The newest shadow (1:4.5-1.1ubuntu1) makes the package util-linux
(2.33.1-0.1ubuntu1) installable.
** Changed in: util-linux (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util
The version 0.99.beta19-2ubuntu1 does not take this into account.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1789022
Title:
libcaca0 still depends on old libncursesw5
The bug was fixed with the 0.99.beta19-2ubuntu2 update.
** Changed in: libcaca (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/17
Public bug reported:
The newest dh-python (3.20180325ubuntu1) has an impossible dependency:
it depends on python3-distuils.
This should be python3-distutils of course.
So this update cannot be installed.
** Affects: dh-python (Ubuntu)
Importance: Undecided
Status: New
** Tags: bio
Package relationships
Depends on:
python3 (>= 3.3.2-2~)
python3-distuils
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1758969
Title:
Newest dh-python has an
Fix released: dh-python (3.20180325ubuntu2) bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1759007
Title:
Depends Typo: python3-distuils instead of python3-distut
** Changed in: dh-python (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1759007
Title:
Depends Typo: python3-distuils i
Public bug reported:
Ubuntu Cosmic switched some time ago from ncurses5 to ncurses6.
However, the package libcaca0 still depends on old libncursesw5 and libtinfo5
instead of libncursesw6 and libtinfo6.
** Affects: libcaca (Ubuntu)
Importance: Undecided
Status: New
** Tags: cosmic
I am not sure if those messages are actually errors.
However, these appear (and have done this for a long time) whenever you try to
upgrade or reinstall GTK+3 package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ub
Public bug reported:
After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the tiff
files cannot be opened any more.
For example Eye of Gnome claims the file type tiff is unknown.
Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue and
tiff's are OK.
** Af
on
gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE
# uname -a
Linux harry-ThinkPad-Edge-E430 4.1
son:
# gcc --version
gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE
# uname -a
Linux har
Public bug reported:
After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got
no network.
This is very likely a DNS issue.
As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS
work fine.
So something odd has happened between these versions.
My setu
With the systemd 233-5ubuntu1:
~$ systemd-resolve --status
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WI
Here are the warnings and messages I get when upgrading systemd
232-21-ubuntu3 => 233-5ubuntu1 with synaptic:
Job for systemd-journald.service failed because the service did not take the
steps required by its unit configuration.
See "systemctl status systemd-journald.service" and "journalctl -x
I mean particularly this.
~$ systemd-resolve --status
"Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not
found."
And as I wrote above, when upgrading to systemd 233-5ubuntu1 I get this:
"Removing obsolete conffile
/etc/dbus-1/system.d/org.freedesktop.resolve1.conf ..."
Added the tag: block-proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1615482
Title:
apt-daily timer runs at random hours of the day
Status in apt package in Ubuntu:
OK,
I have now tested this new apt (1.4.1) against the old version (1.4).
My setup is using solely systemd (with no upstart nor cgmanager installed).
I have fast SSD's, so my normal booting time is about 4 seconds.
Now after upgrading to apt 1.4.1 the booting time to GDM increased with about 5
to
Dimitri,
in my case, not even several reboots helped.
It is all the same here, though network should be up, there is no working dns.
** Summary changed:
- On artful, no network after upgrading to systemd 233-5ubuntu1
+ On artful, no working dns after upgrading to systemd 233-5ubuntu1
--
You re
Dmitri,
"I would like to see package versions of everything that is installed"
I have a fully updated artful setup with proposed enabled.
"... as per your messages it appears that systemd-resolved.service is not
running at all, when it should be."
Systemd-resolved.service works just fine with
OK,
So I got this issue fixed by installing the package bind9.
I tested several times, but dnsutils with bind9-host was not enough.
So I removed those two and installed bind9 instead.
Now I have a working dns.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Dimitri,
thank you for the information.
Now, as I am not very familiar with the systemd nor the dns setup, I
would be happy if you could give me advice how to proceed on this issue.
The status of my setup is as follows.
I have installed all the latest packages of artful aardvark, also from propos
Dimitri,
one more test I just did.
I started systemd-resolved manually:
~$ sudo service systemd-resolved restart
After that the output of systemd-resolve --status is OK:
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::
Dimitri,
My setup does not need the package bind9.
But I need to start systemd-resolved service manually.
After that the output of systemd-resolve --status is OK:
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::
20
Sosreport of my setup.
** Attachment added: "Sosreport"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+attachment/4868196/+files/sosreport-HarryKaasinen.systemd-20170426130934.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
Dimitri,
Just added a sosreport as you requested.
My setup is a nearly minimal setup, containing only the applications I
need.
The issue here is what packages are needed to get the new systemd 233-5ubuntu1
and its resolved working.
And more, exactly those packages that were not needed to get sy
** Description changed:
- After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got
no network.
+ After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got
no nameserver (dns).
This is very likely a DNS issue.
As a workaround downgrading back to system
Dimitri,
I have a question about the chosen nameservers.
When using systemd 232-21-ubuntu3 or earlier, it was like this (systemd-resolve
--status):
Link 2 (eth0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC
I can also confirm, though there is no need to, that the newest version of NM
1.4.2-3ubuntu1 does not work better either.
So this bug still remains unsolved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
This bug is now solved with the latest network-manager v. 1.4.2-3ubuntu2 in
Zesty.
Here:
https://launchpad.net/ubuntu/+source/network-manager/1.4.2-3ubuntu2
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a m
Public bug reported:
The newest alsa-lib (package libasound2) in Zesty Zepus (v. 1.1.3-1) puls in
python2.7.
Package libasound2 depends on libpython2.7 (>= 2.7).
Earlier version did not depend on python2.7, so this is a new feature.
However, the aim was to get rid of puthon2.7 (transition to pyht
** Summary changed:
- Alsa-lib 1.1.3-1 puls in python2.7 (Zepus dev)
+ Alsa-lib 1.1.3-1 puls in python2.7 (Zesty dev)
** Description changed:
- The newest alsa-lib (package libasound2) in Zesty Zepus (v. 1.1.3-1) puls in
python2.7.
+ The newest alsa-lib (package libasound2) in Zesty Zapus (v. 1
This bug is solved with the version 1.1.3-2.
** Changed in: alsa-lib (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1658606
Tit
Just to be clear and let those interested know,
my setup is working fine now with the latest systemd (in proposed now)
233-5ubuntu1.
I installed and reinstalled several packages related to systemd and the command
"systemd-resolve --status"
is OK now.
Systemd-resolved is working well now.
So this
Gnome-shell is still in universe, not in main.
That is the reason for the installation behaviour for now.
See this [MIR] report (1685870) for details:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1685870
--
You received this bug notification because you are a member of Ubuntu
Touch
First of all, I do not think that being unbound is a bug in these unbound
packages (upstart and ifupdown).
The possible bug is in the package, which should depend on them.
However, one should not remove upstart from the setup, unless certain
installations and settings is made.
First of all, for
Martin Pitt wrote:
"Right, that will switch the default init to systemd. If you want to experiment
with that, you can do either that or boot with init=/bin/systemd (you don't
need both)."
Well I did test that with my high-end setup (Intel Core i7 4790 + Asus
Z97 Sabertooth + Samsung 850 Pro SSD)
Martin,
Please note, that in my setup, the network is lost immediately after
rebooting with the new network-manager (1.4.2-2ubuntu4). Then,
downgrading back to version 1.4.2.-2ubuntu3, and rebooting, I get
network back.
In both of these versions, the network-manager creates the same kind of
file
Public bug reported:
Network-manager will make my network connection immediately lost after updating
to the newest version 1.4.2-2ubuntu4.
However, downgrading to the previous version 1.4.2-2ubuntu3 the network
connection is back again and fine. If, with this version, I remove the file
(link) /
Sebastien,
could you please give me instructions on how to install systemd-resolved?
I do have a fully working Gnome-shell DE with systemd as pid1 and no upstart
packages installed.
The network is working fine if I use network-manager (1.4.2-2ubuntu3), but not
anymore if I upgrade to the version
Martin, here is the contents of /etc/NetworkManager/NetworkManager.conf
(with the version 1.4.2-2ubuntu3) installed:
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
And here is the output of
cat /etc/resolv.conf
# Generated by NetworkManager
search dhcp.inet.fi
nameserve
Martin,
here is the failed state output of
cat /etc/resolv.conf
# Generated by NetworkManager
search dhcp.inet.fi
nameserver 127.0.1.1
So, nothing changed. And NM still generates the file /etc/resolv.conf.
I also run
journalctl -u NetworkManager.service -u systemd-resolved.service -b >
/t
Martin,
I removed the line "dns=dnsmasq"
from the conf file.
Then upgraded to NM 1.4.2-2ubuntu4
Rebooted and checked that dns=dnsmasq was absent from the conf file. It was.
However, the result was still the same = no network.
Downgraded back to NM 1.4.2-2ubuntu3, got the network back and fine.
No
Martin,
OK, here goes:
cat /etc/resolv.conf
# Generated by NetworkManager
search dhcp.inet.fi
nameserver 127.0.1.1
cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
journalctl -u NetworkManager.service -u systemd-resolved.service -b >
/tm
Martin,
The /etc/resolv.conf in my set up is really a link.
The target is (where folder "var/run" is a link to the folder "run"):
/var/run/NetworkManager/resolv.conf
However, I upgraded NM to the version 1.4.2-2ubuuntu4 and run the following 4
commands:
sudo systemctl stop NetworkManager
sud
That is simply:
"Unit resolvconf.service could not be found"
I believe there is some package(s) that I do not have installed, but I
should have?
NM 1.4.2-2ubuntu4 needs something to be installed, that NM
1.4.2-2ubuntu3 did not need.
--
You received this bug notification because you are a membe
Martin,
I installed the package resolvconf.
Now the command gives this:
"systemctl status resolvconf"
● resolvconf.service - Nameserver information manager
Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor
preset: enabled)
Active: active (exited) since Wed 2016-12-07
And a little more info:
"/etc/NetworkManager/NetworkManager.conf"
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
"/etc/resolv.conf"
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
One possible issue is the contents of the /etc/resolv.conf (or actually
/run/resolvconf/resolv.conf).
With NM 1.4.2-2ubuntu4 the /etc/resolv.conf is:
nameserver 127.0.0.53
But with NM 1.4.2-2ubuntu3 it is:
search dhcp.inet.fi
nameserver 127.0.1.1
So where did the line "search dhcp.inet.fi" g
First of all,
If NM 1.4.2-2ubuntu4 needs the package resolvconf in order to function
properly, it should depend on it.
Secondly,
NM 1.4.2-2ubuntu3 works perfectly, like all earlier versions, without the
package resolvconf.
Thirdly,
after installing resolvconf with NM 1.4.2-2ubuntu4, NM still do
I have tested this bug this way.
1) With the newest setup with all upgrades installed (Ubuntu Gnome)
there is 6-8 sec slow down when shutting down or rebooting. No delay at
start up.
2) I then downgraded the package isc-dhcp-client (4.3.3-5ubuntu9) to
isc-dhcp-client (4.3.3-5ubuunutu5). Also the
-code) since Tue 2016-04-26 10:23:21 EDT; 11min
ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 660 ExecStart=/lib/systemd/systemd-modules-load (code=exited,
status=1/FAILURE)
Main PID: 660 (code=exited, status=1/FAILURE)
Apr 26 10:23:21 harry syst
b/systemd/systemd-modules-load (code=exited,
status=0/SUCCESS)
Main PID: 264 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 512)
CGroup: /system.slice/systemd-modules-load.service
Apr 26 16:02:26 harry systemd-modules-load[264]: Inserted module 'lp'
Apr 26 16:02:26 harry systemd-m
Same here, kernel panic with v. 0.120ubuntu1
I also use intel-microcode; remiving does not solve anything.
However, intramfs.tools_0.103ubuntu16 works well.
I had to chroot to downgrade to that one.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
The correct workaround or fix for the time being is to downgrade the
version 0.120ubuntu1 to the working version 0.103ubuntu16.
You will need to chroot the root partition to do this.
I believe package intel-microcode has nothing to with this.
--
You received this bug notification because you are
I can confirm too, the PPA solved the issue.
I also have only busybox-initramfs installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1481733
Title:
Kernel panic when
Public bug reported:
I just installed (for testing) the newest systemd from Vivid proposed
repositories.
Yes, that is only a proposed package.
The version is 215-5ubuntu1. Also the new plymouth was needed to do this
(version 0.9.0-0ubuntu8).
After the installation I find that every second boot
Further info:
I use solely systemd booting.
So, I have systemd-sysv installed and upstart, systemd-shim, cgmanager,
libcgmanager0, removed.
I also use the kernel line: init=/lib/systemd/systemd
If I remove that, I get a kernel panic.
--
You received this bug notification because you are a member
** Description changed:
I just installed (for testing) the newest systemd from Vivid proposed
repositories.
Yes, that is only a proposed package.
The version is 215-5ubuntu1. Also the new plymouth was needed to do this
(version 0.9.0-0ubuntu8).
- After the installation I find that every
I downgraded systemd to the version 208 in official Vivid repos.
Now booting works perfectly and fast.
It may be worthwhile to tell that I have purged systemd-shim, cgmanager and
libcgmanager0 from my setup.
So this really is a pure systemd booting setup now.
--
You received this bug notificati
Martin, do you have upstart, systemd-shim, cgmanager and libcdmanager0
purged and are you using kernel line init=/lib/systemd/systemd ?
I cannot boot at all if I remove the kernel booting line.
Then to your questions:
1) I could not get the booting hang when "quiet" was dropped from the kernel
Hi Martin,
Here is some info.
"Well yes -- You have no package which provides /sbin/init then, so you
need to install either upstart or systemd-sysv."
I have had systemd-sysv installed all the time.
"Interesting, so mostl likely the fsck succeeded."
Mounts: sda1 is /, sdb1 is /home. They are t
Hi Martin,
True, I cannot switch between tty's. The whole system is unresponsive to
any keyboard commands.
About SysRQ (reisub): I cannot try it, because in my keyboard (Logitech K740)
there is no SysRQ button.
Usually it is the "alt-function" of the PrintScreen button, but not here.
About the
Martin,
In addition the previous post #8
I tried again booting without "quiet" in the kernel line: 10/10 boots were
successful.
Then with "quiet": 3 out of 10 did hang.
Hanging (or crash) happens right after the fsck is done.
Mostly after sda1 fsck and before sdb1 fsck.
Sometimes both sda1 and
SysRQ
My keyboard does not apparently have that button.
http://www.logitech.com/en-gb/product/illuminated-keyboard-k740
So, at least trying Alt+Print Screen R+E+I+S+U+B does nothing, even after a
successful boot.
The hang
Yes, I now have only this in kernel line: quiet init=/lib/systemd/systemd
S
Martin,
Here are the answers.
1) $ ls -l /sbin/init
Command not found
So, a little different. What is missing here?
2) Initramfs-tools v. 0.103ubuntu8
That is the latest one.
3) /boot/grub/grub.cfg
It is now attached.
** Attachment added: "Grub.cfg"
https://bugs.launchpad.net/ubuntu/+sour
My bad. A correction.
1) ls -l /sbin/init
lrwxrwxrwx 1 root root 20 marra 3 08:41 /sbin/init -> /lib/systemd/systemd
--
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/1385630
Martin,
Here are the results.
1) "gzip -cd /boot/initrd.img-3.16.0-24-generic | cpio -t | grep readlink"
gzip: /boot/initrd.img-3.16.0-24-generic: not in gzip format
cpio: arkiston ennenaikainen loppu
(arkiston ennenaikainen loppu = the archiv ended prematurely)
2) after running "sudo update-in
Here:
file /boot/initrd.img-3.16.0-24-generic
/boot/initrd.img-3.16.0-24-generic: ASCII cpio archive (SVR4 with no CRC)
--
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/138563
Martin,
My setup is fairly new, from September 2014.
I installed Ubuntu-Gnome Trusty then and upraded it first to Utopic and now to
Vivid dev.
I haven't mofified /etc/initramfs-tools/initramfs.conf in any way.
I attach this file here.
The folder /etc/initramfs-tools/conf.d/ is empty.
** Attachm
Martin,
I also attach the file /etc/intramfs-tools/update-initramfs-conf here.
** Attachment added: "update-initramfs.conf"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+attachment/4257300/+files/update-initramfs.conf
--
You received this bug notification because you are a
Here is the attachment /boot/initrd.img-*
** Attachment added: "initrd.img-3.16.0-24-generic"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+attachment/4258396/+files/initrd.img-3.16.0-24-generic
--
You received this bug notification because you are a member of Ubuntu
Touch
Martin,
The command "cpio -tv /boot/initrd.img-3.16.0-24-generic" did nothing.
Terminal just started a neverending process (but not getting stuck).
I did wait for several minutes.
The size of /boot/intitrd.img-3.16.0-24-generic is 19.2 Mb.
--
You received this bug notification because you are a
Martin,
Well the GenuineIntel.bin may come from intel-microcode package of the Vivid
multiverse repository.
This is installed because of the Intel Core i7 Haswell processor.
My motherboard Asus Sabertooth has UEFI-BIOS and it is using UEFI Secure boot,
which may have something to do with this to
Right,
yesterday when systemd (208-7ubuntu4) and sysvinit (2.88dsf-41ubuntu17) were
published in Utopic pocket release,
I upgraded my setup.
After that I installed systemd-sysv and purged upstart, upstart-bin, ureadahead
and libjson0.
I am using systemd booting and it works just fine (with no u
An update to this bug.
I haven't seen the hang described here since I upgraded GDM to the version
3.14.0-0ubuntu1.
It may or may not have anything to do with this.
However, this bug report may now be closed.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received t
Public bug reported:
This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid
branch.
When upgrading to this version, this is the warning message I get:
Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service
failed to load: No such file or directory.
Howev
More info on my setup:
I only use systemd booting with "init=/lib/systemd/systemd" kernel booting line.
I have upstart, cgmanager and systemd-shim purged.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
http
Public bug reported:
I have a completely upgraded Ubuntu Utopic development branch setup, with
proprietary nvidia drivers installed.
I have set my booting system to boot with systemd instead of the upstart one.
The newest systemd-shim (version 6-3ubuntu1) depends on cgmanager.
However, installati
I noticed that bug LP: #1342586 is solved and fix released, but this new
bug is not solved by that systemd update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1343802
Thank you Serge.
I am afraid the building procedure you asked is beyond my skills.
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1343802
T
Martin,
you mentioned your system runs fine with upstart (that is booting with upstart).
However, this bug is about not being able to boot with systemd
(init=/lib/systemd/systemd).
Can you reproduce the bug with systemd booting?
--
You received this bug notification because you are a member of U
Yes,
I can confirm that the Martin's PPA version of systemd (208-2pitti1) works fine
with the latest cgmanager (0.27-0ubuntu7) and with the package cgmanager and
latest systemd-shim (6-3ubuntu1) installed.
I think we should get the systemd 208 into the Utopic official repos
now.
--
You receive
** Description changed:
I have a completely upgraded Ubuntu Utopic development branch setup, with
proprietary nvidia drivers installed.
I have set my booting system to boot with systemd instead of the upstart one.
The newest systemd-shim (version 6-3ubuntu1) depends on cgmanager.
- However,
The new systemd (208-6ubuntu1) works fine on my setup:
fully updated Utopic (amd64) with nvidia proprietary drivers.
I tested this with systemd booting.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
Public bug reported:
I'm testing out eoan, I have a [Network] section with IPMasquerade=yes.
The system starts without complaint from systemd in the logs, but I see no
evidence of source natting going on.
I'm not sure of sub-dependencies, but I think source natting depends on
libiptc-dev, which
I can't found python script debug-helper.py in /usr/lib/NetworkManager/
--
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/1828313
Title:
wifi cannot connect to openw
sudo /usr/lib/NetworkManager/debug-helper.py --mm debug
Traceback (most recent call last):
File "/usr/lib/NetworkManager/debug-helper.py", line 10, in
mm_bus = bus.get_object('org.freedesktop.ModemManager',
'/org/freedesktop/ModemManager')
File "/usr/lib/python2.7/dist-packages/dbus/bus.p
sudo /usr/lib/NetworkManager/debug-helper.py --nm debug
Traceback (most recent call last):
File "/usr/lib/NetworkManager/debug-helper.py", line 10, in
mm_bus = bus.get_object('org.freedesktop.ModemManager',
'/org/freedesktop/ModemManager')
File "/usr/lib/python2.7/dist-packages/dbus/bus.p
Public bug reported:
Several times an hour, usually when switching focus from one window to
another, all but the mouse will stop changing for a few seconds to a
minute or so. If a video is playing the sound will proceed as if normal
but the screen will not change. The shape of the mouse will not
And... spoke too soon. It happens under xrender as well. Shorter
freezes, frequency is the same.
--
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/1811159
Title:
temporary fre
Public bug reported:
I installed xubuntu in my Windows box using the latest VBOX (6.0). It
installed perfectly however after I log in the screen kind of freezes. I
see the background however the icons and title bar do not appear. Also
mouse inputs like right click do not work. Function keys do not
comment #39 fixed it for me
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594
Title:
[regression] compiz crashes after Mesa upgrade
Status in mesa package in Ubuntu:
I'm now testing Ubuntu 15.10, which seems *even more* broken, since it
seems to have a mixed mode of Python3.4 and 3.5. there's no
python3.4-pip package, which means there is essentially no way of
getting a working pip for python 3.4.
I know I'm not a contributor, so I don't *deserve* answers, bu
Public bug reported:
Related to this bug:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1290847
It looks like 15.10 uses a mixture of Python 3.4 and 3.5 (hopefully
that's temporary?). Pip, the python package manager, is available from
"python-pip" for Python 2.7, and "python3-pip" for
1 - 100 of 143 matches
Mail list logo
