[Bug 1803275] Re: nvidia-kernel-source-390 390.87-0ubuntu2: nvidia kernel module failed to build
Same for me here using disco... update-initramfs: Generating /boot/initrd.img-4.18.0-10-generic Processing triggers for libc-bin (2.28-0ubuntu1) ... Errors were encountered while processing: nvidia-dkms-390 nvidia-driver-390 E: Sub-process /usr/bin/dpkg returned an error 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/1803275 Title: nvidia-kernel-source-390 390.87-0ubuntu2: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1803275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246347] Re: Lots of "error on subcontainer ‘ia_addr’ insert (-1)" reports in /var/log/syslog
Looks like I can't edit a comment. I found this works for me on 17.10... sudo -i cp /lib/systemd/system/snmpd.service /etc/systemd/system/snmpd.service sed -i "s|-Lsd|-LS6d|" /etc/systemd/system/snmpd.service systemctl daemon-reload systemctl restart snmpd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246347 Title: Lots of "error on subcontainer ‘ia_addr’ insert (-1)" reports in /var/log/syslog To manage notifications about this bug go to: https://bugs.launchpad.net/netsnmp/+bug/1246347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246347] Re: Lots of "error on subcontainer ‘ia_addr’ insert (-1)" reports in /var/log/syslog
FWIW I'm still getting this error in my logs on 17.10 artful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246347 Title: Lots of "error on subcontainer ‘ia_addr’ insert (-1)" reports in /var/log/syslog To manage notifications about this bug go to: https://bugs.launchpad.net/netsnmp/+bug/1246347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714626] [NEW] Installer crashed at install grub stage
Public bug reported: Ubiquity crashed at the install grub step. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.4 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CasperVersion: 1.384 Date: Sat Sep 2 13:10:09 2017 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful kubuntu ubiquity-17.10.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714626 Title: Installer crashed at install grub stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1714626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480513] [NEW] nginx-common should not depend on python
Public bug reported: None of the dependencies for nginx-common (lsb-base and init-system- helpers) require python support so the nginx-common package should not force the python package to be installed. The current python dependency should be moved to Suggests or added to the other nginx-* packages that may need python support. The nginx-light package does not need python but because of the dependency in nginx-common it forces python to be installed. ** Affects: nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1480513 Title: nginx-common should not depend on python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1480513/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1480513] [NEW] nginx-common should not depend on python
Public bug reported: None of the dependencies for nginx-common (lsb-base and init-system- helpers) require python support so the nginx-common package should not force the python package to be installed. The current python dependency should be moved to Suggests or added to the other nginx-* packages that may need python support. The nginx-light package does not need python but because of the dependency in nginx-common it forces python to be installed. ** Affects: nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480513 Title: nginx-common should not depend on python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1480513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480513] Re: nginx-common should not depend on python
Thank you for considering this request and marking it appropriately. Please kindly suggest to the Debian folks that this future ngx-conf utility should be in a separate package to isolate the need for python. I only noticed this because I routinely remove anything to do with python from my VPS and lxc containers to keep them as light as possible and I was puzzled why installing nginx(-light) tried to reinstall python-2.7. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1480513 Title: nginx-common should not depend on python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1480513/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1480513] Re: nginx-common should not depend on python
Thank you for considering this request and marking it appropriately. Please kindly suggest to the Debian folks that this future ngx-conf utility should be in a separate package to isolate the need for python. I only noticed this because I routinely remove anything to do with python from my VPS and lxc containers to keep them as light as possible and I was puzzled why installing nginx(-light) tried to reinstall python-2.7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480513 Title: nginx-common should not depend on python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1480513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429725] Re: package mariadb-server-10.0 10.0.16-2~exp1~ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
FWIW I also notice that /etc/mysql/debian.cnf contains socket = /mysqld.sock instead of socket = /var/run/mysqld/mysqld.sock and after many hours attempting to get the package installed I seem to have it running but I cannot gain root access even though I have reset the root password a dozen times in a few different ways. /etc/mysql/mariadb.conf.d/mysqld.cnf has a user = mysql setting which I think is needed to initially install the tables because doing so manually results in some root owned files/dirs (like /var/lib/mysql/mysql) but then that mysql user setting seems to disrupt further operations unless there are specific grant entries for that user and there is no hint of any attempt to setup a mysql user in the install scripts. I'd go back to mysql 5.6 but it uses a huge amount of ram by default, over 400Mb RSS compared to about 100Mb RSS for mariadb 10 and mysql 5.5. For me the only immediate solutions is to drop back to utopic and hope the mariadb 10 packages get fixed asap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429725 Title: package mariadb-server-10.0 10.0.16-2~exp1~ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1429725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377426] [NEW] Roundcube should not depend on apache
Public bug reported: Using Ubuntu 14.04 and 14.10 where nginx and php5-fpm is already installed roundcube should not depend on apache. I understand nginx may not be fully supported yet so this is a heads up that this situation will render the roundcube package uninstallable so therefor is a packaging bug. Expected situation is for roundcube to depend on a virtual httpd package with the option of the current apache auto config or allow an admin to NOT install apache'isms and configure their alternate webserver themselves (if need be). ** Affects: roundcube (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377426 Title: Roundcube should not depend on apache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/roundcube/+bug/1377426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390396] Re: About Me in System Settings throws an error when changing details
Just as a note if anyone lands here via a search for another distro. It's likely that this problem can also be solved by making sure CHFN_RESTRICT frwh includes the f in /etc/login.defs because the action of saving the user details in System Settings - About Me also updates the /etc/passwd GECOS field but that will be denied by the underlying system if the f is missing from CHFN_RESTRICT. -- About Me in System Settings throws an error when changing details https://bugs.launchpad.net/bugs/390396 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 61463] Re: Script that are using bash could be broken with the new symlink
This discussion should be heard, but apparently isn't. They don't care. Perhaps posting on the Ubuntu development discussion list, ubuntu-devel-discuss, is the right venue? Yes, please try. Personally, I have voted with my feet and just finished re-installing Debian (etch) on a couple of dozen servers. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61463] Re: Script that are using bash could be broken with the new symlink
@probono, that would be so sensible because they have total control over the scripts that they need to speed up the boot process but no control over the scripts the rest of us use for general maintenance after bootup. Then they could announce that they will enforce such a change to /bin/dash in 6 or 12 months time. In the mean time they could lead an active public campaign to enlighten upstream devs as to the folly of their ways and provide support towards the Ubuntu goal of saving the world from bashisms so they can adopt dash as their overall primary shell. However, if you have had any interaction with @sparr and the ubuntu devs then you'll notice a very blunt response that it's *your* fault for using bashisms on *your* systems so you need to fix *your* problem. This is the kind of mistake that a semi-closed commercial outfit can make where clean room techies are out of touch with the real world. The Debian and Fedora folks would have a very hard time mandating a change like this. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61463] Re: Script that are using bash could be broken with the new symlink
If every person who has posted to this bug report so far instead took the time to submit a patch to one bashism-laden project, this would be a non-problem. @sparr, you live in some kind of fairy land. There are millions of bash scripts lying around on the net written over the last 10 years expecting to be used as /bin/sh. Anyone of those scripts could be problematic for an edgy+ system for many years yet to come. Anyone reading this thread will be savvy enough to fix the problem one way or another but that excludes the 99.99% of users, that apparently this distro is aimed at, with the potential of yet another weird problem that they can't fix. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61463] Re: Script that are using bash could be broken with the new symlink
@sparr: The Ubuntu devs have done a far greater good here than with any other distro I have used in the past. Then you and the ubuntimati don't have a real world clue between you all. I manage dozens of servers with 100s of shell scripts each, some dating back 10 years, half authored by me, half not. I have a choice, do I edit all these scripts (1000s!!!), do I self maintain a hacked /bin/sh link to /bin/bash, or, do I assign my future to another distro that I can trust not to put me in this position again? I'm glad I don't manage a really large server farm currently on dapper and needing to move to apache2.2. What really gets me is the attitude of people like you that don't care about the pain this move inflicts on however many *ubuntu* users when there is no need for it... you guys could have EASILY used #/bin/dash where YOU need it and notified the community that there was a fundamental change coming in the next release... look out, beware etc. I, for one, am not going to let you people screw me over like this again. You've had your chance to encourage me to use your distro and you've blown it. My remastered distro won't be based on ubuntu as there is no way I would do this kind of thing to my clients and potential users! Another point you made is almost an insult... you say that for the time some of us here have been complaining about this that we could have spent that time interacting with upstream devs to change their ways. WTF! Ubuntu is/was my upstream provider, you folks are the ones that should be doing double duty to interact with various upstream sources to bring about a change that YOU have mandated. Not us. I'm perfectly happy with /bin/sh - /bin/bash and have no need for your pedantic POSIXisms. I have business to run and need things to just work. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61463] Re: Script that are using bash could be broken with the new symlink
What worries me about this issue is the attitude of the ubuntu developers. I no longer trust the ubuntu devs to do the right thing to help me keep the systems I make a living from up and running and am now looking at migrating everything to etch+ instead of edgy+. The overwhelming right thing to do would have been to advertise the need to change from bash to dash and put a deadline on it no less than 1/2 a year on notice, THEN make the change. Suddenly unleashing KNOWN breakage like this is unacceptable to me. Such a pity I have to forgo such a good distro in all other respects because of this stupid move by a few devs. Like I say, I no longer trust ubuntu devs not to do something like this again in the future. And yes, breaking trust is a serious bug. -- Script that are using bash could be broken with the new symlink https://launchpad.net/bugs/61463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
