[Bug 1489530] Re: Kubuntu installer fails when mounted parts, does not restart
I cannot currently test this as quickly. However since this was true for 15.10, and 16.04 is still supported, and this bug has not been triaged in the meantime, I can only assume that it is still going to be true, since not many things appear to have changed in the installer since then. (I also don't particularly consider it a good waste of time to re- evaluate bugs that are only automatically flagged as incomplete, with the good chance that they still won't be triaged further down the line). (But that's just me, and YMMV.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489530 Title: Kubuntu installer fails when mounted parts, does not restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1489530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607687] Re: various packages show as installed, but files are not present
Here is the list of packages that have incomplete files: btrfs-tools casper cifs-utils dmraid fcitx-frontend-all fcitx-frontend-gtk2 fcitx-frontend-gtk3 fcitx-frontend-qt4 fcitx-frontend-qt5 fcitx-module-cloudpinyin fcitx-module-dbus fcitx-module-kimpanel fcitx-module-lua fcitx-module-x11 fcitx-pinyin fcitx-table fcitx-ui-classic jfsutils kde-config-fcitx kpartx kpartx-boot libdmraid1.0.0.rc16 libfcitx-gclient0 libfcitx-qt0 libfcitx-qt5-1 libgeoclue0 libjavascriptcoregtk-4.0-18 liblua5.2-0 libwebkit2gtk-4.0-37 libwebkit2gtk-4.0-37-gtk2 linux-image-4.10.0-28-generic linux-signed-generic-hwe-16.04 linux-signed-image-4.10.0-28-generic linux-signed-image-generic-hwe-16.04 lupin-casper mokutil presage python3-cupshelpers reiserfsprogs ubiquity-slideshow-kubuntu user-setup xfsprogs zenity zenity-common As you can see many of these (or most of these) would get removed after install. So the problem is more that this package removal doesn't happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607687 Title: various packages show as installed, but files are not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1607687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569438] Re: Doom crashes on title screen with error DRC64:Unhandled memory reference
Changing the value for core to "simple" is not a workaround because it renders the performance non-functional. It got fixed in Debian in version 0.74-4-3, which means that this package has been broken in Ubuntu for a year and a half, or three consecutive releases. It first made its appearance in Bionic which is as of yet unreleased, but the Bionic version immediately fixes the performance issues (and otherwise crashes) and is installable without any extra dependencies on Yakkety, Zesty and Artful. You can download it here: https://packages.ubuntu.com/bionic/amd64/dosbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569438 Title: Doom crashes on title screen with error DRC64:Unhandled memory reference To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1569438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740319] [NEW] Dosbox should be 32-bit version on 64-bit
Public bug reported: 16-bit DOS games are unplayable in the 64-bit version of Dosbox. GoG.com games come with a 32-bit version of Dosbox, and this runs excellently. On Ubuntu, the 32-bit version also runs excellently. The 64-bit version lags immensely and makes games unplayable. Dosbox and its associated libraries should be made available on 32-bit always and be excempt of the no-packaging-32-bit in the future to begin with. The 64-bit version should really be removed from the repos and 32-bit Dosbox packaged as the 64-bit version, with accompanying libraries, just like libc6-i386 is factually a 64-bit package (amd64). -- Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial dosbox: Installed: 0.74-4.2 Candidate: 0.74-4.2 Version table: *** 0.74-4.2 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: dosbox (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/1740319 Title: Dosbox should be 32-bit version on 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dosbox/+bug/1740319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80900] Re: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks
I guess I am wrong about the "upstream security hole" thing. But I don't know why you would use mDNS for serious security anyway. mdns_minimal already causes a 4-second fallthrough (if AVAHI is disabled at least). So Lennart is ranting and screaming only about the [NOTFOUND=return] line? As if he decides what NSS does. His is a plugin. A plugin is a peer to other plugins; not one plugin is more important than the others; the plugin is just that, the configuration is up to the end user (or the bigger system). He acts as if /etc/nsswitch.conf now belongs to his package. His PulseAudio also configures itself in the same way as authorative with ALSA. Same idea, repeats itself. "If PulseAudio module is loaded, set it to be the ALSA default device". What? What if some other module wanted to do the same? So NSS is to Lennart just an annoyance, an archaic system that doesn't make him the most important person in the world and then he starts saying "fuck yous" to get his way. He wanted his package to be orphaned and renamed, as if he holds a trademark to "mdns". As if he holds a trademark to "libnss". Nothing about that is "Lennart". That's the least trade-markable name in the history of trademarkable names. And then he starts ranting "You don't give a fuck about people and you think it's about you". But everything is always about Lennart. What Lennart wants. What Lennart decides. What Lennart says is best. Quite remarkable that you can think "libnss-mdns" is somehow a trademarkable name. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/80900 Title: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80900] Re: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks
Apple, whose OS X Yosemite (10.10) will not even resolve DNS when
internet is down ("private networks don't exist"), simply chose the
wrong name for something that is basically only used by machines.
Their ".local" is not meant for manual use.
They could just as easily have called it ".mdns" or something -- OS X
will by default not show it anyway I'm sure.
So they have claimed something they were not entitled to and their
broken model of network computing is now the foundation of how to do
things?
* The local DNS server timeout issue is not really an issue; if you
didn't want that you shouldn't have chosen .local for mdns.
* .local leakage is no different from .home leakage and in this case
can be prevented
* redirecting local services would require upstream malicious .local
to be configured in DNS servers but is directly at odds with the
situation in which a _local_ .local DNS server is configured, so can
also be solved by only allowing .local to get out if there IS a local
.local DNS server
* The only real argument that remains is name resolution; automatic
changing of host names in cast of conflicts. RFC 6762 notes that
"Implementers MAY choose to look up such names concurrently via other
mechanisms (e.g., Unicast DNS) and coalesce the results in some
fashion. Implementers choosing to do this should be aware of the
potential for user confusion when a given name can produce different
results depending on external network conditions (such as, but not
limited to, which name lookup mechanism responds faster)."
Lennart likes to scream about people not listening to the designers; but
what does he do?
The typical use case of a merged system is when DHCP provides DNS through
supplied
hostnames, there is no resolution in that sense, at least no standard one.
The DHCP set would remain unchanged (and unresolved) while the mDNS set,
oblivious
to anything happening in unicast DNS, would produce different names where
some of them
would change, adding new ones to the total set. Those new names would only
be resolvable
through mDNS. Unless you were talking about a huge network (why would you
use multicast
in such a system?) the actual prevalence of such conflicts and confusion
must be considered
low.
I think it can be argued that discovery is a much more important aspect of
mDNS than
resolution because most hardware devices pick MAC-based names and most
operating systems
also pick randomized names by default.
Anything else reeks of configuration, and if you configure, you are
not in zeroconf.
So there aren't really any reasons that are deal-breaking, and those that
exist are caused
by mDNS' insistence to use for its automated system a human-meaningful name
such as .local,
which is a design flaw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/80900
Title:
Avahi daemon prevents resolution of FQDNs ending in ".local" due to
false negatives in the detection of ".local" networks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739832] Re: libnss-ldap default runlevels cause invoke-rc.d to fail
*** This bug is a duplicate of bug 1739833 *** https://bugs.launchpad.net/bugs/1739833 Please close this one (and delete). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739832 Title: libnss-ldap default runlevels cause invoke-rc.d to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1739832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024475] Re: libnss-ldap causes boot hang on 12.04 precise, 14.04 trusty, 16.04 xenial
I just submitted #1739833 The postinst script for libnss-ldap invokes "invoke-rc.d" but invoke- rc.d will not do anything unless the Default-Start runlevel of /etc/init.d/libnss-ldap contains runlevel 5. Because /etc/init.d/libnss-ldap comes without any default runlevels, the action does nothing and the service is not started, causing the service to also not be stopped, and nssldap-update-ignoreusers to not be run on reboot. This in turn prevents the system users from being added to the ignore list which then causes the boot to fail because it tries to source them from LDAP. This is probably of particular relevance to groups, but I don't remember, this is long ago for me. (And it still hasn't been fixed, even though I have been sending emails about this too to devel-discuss). The ostensibly newer package libnss-ldapd contains the option "ALLLOCAL" which generates this "exclusion list" automatically on boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024475 Title: libnss-ldap causes boot hang on 12.04 precise, 14.04 trusty, 16.04 xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1024475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024475] Re: libnss-ldap causes boot hang on 12.04 precise, 14.04 trusty, 16.04 xenial
Okay I don't know how to link to bugs. I guess it wants the specific short form URL: https://bugs.launchpad.net/bugs/1739833 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024475 Title: libnss-ldap causes boot hang on 12.04 precise, 14.04 trusty, 16.04 xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1024475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739833] [NEW] libnss-ldap default runlevels cause invoke-rc.d to fail
Public bug reported:
During postinst invoke-rc.d libnss-ldap start is run.
libnss-ldap comes without any Default-Start levels
On line 390 of invoke-rc.d:
### LOCAL INITSCRIPT POLICY: Enforce need of a start entry
### in either runlevel S or current runlevel to allow start
### or restart.
###
case ${ACTION} in
start|restart)
if testexec ${SLINK} ; then
RC=104
elif testexec ${KLINK} ; then
RC=101
elif testexec ${SSLINK} ; then
RC=104
else
RC=101
fi
;;
esac
Therefore, the (now generated) systemd service is not started.
This causes it to not execute its "Stop" action during shutdown, causing
the system to fail booting because nssldap-update-ignoreusers is not
run.
Possible remedies:
--- libnss-ldap.orig2016-10-06 15:42:27.991990056 +0200
+++ libnss-ldap 2016-10-06 15:45:48.921305843 +0200
@@ -6,4 +6,4 @@
# Required-Stop: mountall.sh
-# Default-Start:
-# Default-Stop: 0 1 6
+# Default-Start: 1 2 5
+# Default-Stop: 0 6
# Short-Description: Updates /etc/ldap.conf
The "5" is essential as noted above in update-rc.d.
Runlevels 1, 2 and 5 are translated to rescue, multiuser and
graphical.target
By enabling this patch and then running:
update-rc.d libnss-ldap remove
update-rc.d libnss-ldap defaults
invoke-rc.d libnss-ldap start
The systemd service is now started:
dec 22 21:55:26 ubuntu systemd[1]: Starting LSB: Updates /etc/ldap.conf...
dec 22 21:55:26 ubuntu systemd[1]: Started LSB: Updates /etc/ldap.conf.
Whereas before nothing would happen.
Alternatively a systemd service could be added, along the lines of:
[Unit]
Description=Ensure LDAP does not prevent the system from booting
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStop=/usr/sbin/nssldap-update-ignoreusers
[Install]
WantedBy=multi-user.target rescue.target
--
Description:Ubuntu 16.04.3 LTS
Release:16.04
--
libnss-ldap:
Installed: 265-3ubuntu2
Candidate: 265-3ubuntu2
Version table:
*** 265-3ubuntu2 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
--
Related to: https://bugs.launchpad.net/ubuntu/+source/libnss-
ldap/+bug/1024475
** Affects: libnss-ldap (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "libnssldap_runlevel5.diff"
https://bugs.launchpad.net/bugs/1739833/+attachment/5026196/+files/libnssldap_runlevel5.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739833
Title:
libnss-ldap default runlevels cause invoke-rc.d to fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1739833/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739832] [NEW] libnss-ldap default runlevels cause invoke-rc.d to fail
*** This bug is a duplicate of bug 1739833 ***
https://bugs.launchpad.net/bugs/1739833
Public bug reported:
During postinst invoke-rc.d libnss-ldap start is run.
libnss-ldap comes without any Default-Start levels
On line 390 of invoke-rc.d:
### LOCAL INITSCRIPT POLICY: Enforce need of a start entry
### in either runlevel S or current runlevel to allow start
### or restart.
###
case ${ACTION} in
start|restart)
if testexec ${SLINK} ; then
RC=104
elif testexec ${KLINK} ; then
RC=101
elif testexec ${SSLINK} ; then
RC=104
else
RC=101
fi
;;
esac
Therefore, the (now generated) systemd service is not started.
This causes it to not execute its "Stop" action during shutdown, causing
the system to fail booting because nssldap-update-ignoreusers is not
run.
Possible remedies:
--- libnss-ldap.orig2016-10-06 15:42:27.991990056 +0200
+++ libnss-ldap 2016-10-06 15:45:48.921305843 +0200
@@ -6,4 +6,4 @@
# Required-Stop: mountall.sh
-# Default-Start:
-# Default-Stop: 0 1 6
+# Default-Start: 1 2 5
+# Default-Stop: 0 6
# Short-Description: Updates /etc/ldap.conf
The "5" is essential as noted above in update-rc.d.
Runlevels 1, 2 and 5 are translated to rescue, multiuser and
graphical.target
By enabling this patch and then running:
update-rc.d libnss-ldap remove
update-rc.d libnss-ldap defaults
invoke-rc.d libnss-ldap start
The systemd service is now started:
dec 22 21:55:26 ubuntu systemd[1]: Starting LSB: Updates /etc/ldap.conf...
dec 22 21:55:26 ubuntu systemd[1]: Started LSB: Updates /etc/ldap.conf.
Whereas before nothing would happen.
Alternatively a systemd service could be added, along the lines of:
[Unit]
Description=Ensure LDAP does not prevent the system from booting
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStop=/usr/sbin/nssldap-update-ignoreusers
[Install]
WantedBy=multi-user.target rescue.target
--
Description:Ubuntu 16.04.3 LTS
Release:16.04
--
libnss-ldap:
Installed: 265-3ubuntu2
Candidate: 265-3ubuntu2
Version table:
*** 265-3ubuntu2 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
--
Related to: https://bugs.launchpad.net/ubuntu/+source/libnss-
ldap/+bug/1024475
** Affects: libnss-ldap (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "libnssldap_runlevel5.diff"
https://bugs.launchpad.net/bugs/1739832/+attachment/5026195/+files/libnssldap_runlevel5.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739832
Title:
libnss-ldap default runlevels cause invoke-rc.d to fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1739832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855019] Re: Automatically redirected .local domain cannot be reached
This is probably created by the mdns_minimal plugin in /etc/resolv.conf The situation is that the developers of multi-cast DNS on Linux thought they needed to claim .local for multi-cast DNS and hence won't allow any "normal" lookups as your hotel is doing. Or asking your laptop to do. If you go to /etc/resolv.conf (this is long ago I know, but I guess you could still be subscribed and might never have found the answer), you will see hosts files mdns_minimal [NOTFOUND=return] dns or something similar. The [NOTFOUND=return] is the culprit, because it is the "dns" module that would successfully have found the login page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855019 Title: Automatically redirected .local domain cannot be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/855019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731806] Re: scrollbar-slider-horizontal-overlay.png wrong name
** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/breeze-gtk/+bug/1731806/+attachment/5007962/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731806 Title: scrollbar-slider-horizontal-overlay.png wrong name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/breeze-gtk/+bug/1731806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731806] [NEW] scrollbar-slider-horizontal-overlay.png wrong name
Public bug reported: The file on my system is: /usr/share/themes/Breeze/gtk-3.0/assets/scrollbar-slider-horizontal- overlay.png But the GTK3 widget "ScrolledWindow", and probably "ScrollBar" excepts to find it at: /usr/share/themes/Breeze/gtk-3.0/assets/scrollbar-slider-overlay- horizontal.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gtk3-engines-breeze 5.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sun Nov 12 22:25:51 2017 SourcePackage: breeze-gtk UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: breeze-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731806 Title: scrollbar-slider-horizontal-overlay.png wrong name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/breeze-gtk/+bug/1731806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607687] Re: various packages show as installed, but files are not present
It happened again on an install of 16.04.3. Ubiquity leaves behind no installer log on the installed system so again I do not have any sorry. I would have to reinstall somewhere sometime and ensure that grub fails. In principle that's easy enough. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607687 Title: various packages show as installed, but files are not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1607687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 829940] Re: Inkscape will not open SVG files
** Also affects: gnome-vfs (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/829940 Title: Inkscape will not open SVG files To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/829940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728525] Re: benchmark window is not descriptive enough
I have no clue, or I had no clue whether it was destructive or not. I still don't know. Actually it seems to have just wiped my partition table. There was a GPT partition table on there and it is gone. It tells you to back up your data but that is a warning given by many programs that are not destructive in the slightest (except if you mess up). So why doesn't it just tell you it will destroy stuff? It might just as well write and then write back the original data, or actually write the original data in the first place, we can't tell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728525 Title: benchmark window is not descriptive enough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/728525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392204] Re: Huge CPU usage by mount.ntfs process
Still true today. Copying about 180 MB of smaller files (pictures) to a NTFS partition (filesystem) inside TrueCrypt. It took 20 minutes. I partition the same mapped device -- format it -- to exFAT, and it takes 26 seconds. So it took 26 seconds to write that same data at 7.2 MB/s and it took 20 minutes to write the same data at 160 kB/s. Just incredible. Just incredible for something that has been around for so long. Not eating their own dog-food, I guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/392204 Title: Huge CPU usage by mount.ntfs process To manage notifications about this bug go to: https://bugs.launchpad.net/ntfs-3g/+bug/392204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Can confirm that it is still in Debian stable as of 2016. Cannot test Ubuntu now. Installing udhcpc and uninstalling isc-dhcp-client does the trick. No need to put any package on hold. At least, when you are still using /etc/network/interfaces. I have not tested network-manager or anything else. If you only have one DHCP address (or even multiple? I cannot test) giving hostname and client is not necessary in /etc/network/interfaces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/351378 Title: dhclient fails for virtual interfaces (IP aliases) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/351378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593398] Re: cifs-utils corrupt (Kubuntu 16.04)
*** This bug is a duplicate of bug 1607687 *** https://bugs.launchpad.net/bugs/1607687 Yes, as you full well know by now (from the other bug ;-)) (because I am the same person) (but for clarity on this bug report): Indeed grub- install from the regular grub failed and I had to use my own grub version to get it to boot. But the peculiar thing is that I remember this also to be the case for the running LIVE version of Kubuntu while using that live version; ie. installed packages (in this case, only cifs-utils) also had their files missing in the LIVE session. I can't say more now, see ya. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593398 Title: cifs-utils corrupt (Kubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1593398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607687] Re: various packages show as installed, but files are not present
I never imagined that it could be this. On both Installs I used a custom setup in which I had my system directly on disk in a PV which means I had to manually install Grub using a patched Grub. I believe the installer does not allow to not install Grub, so I direct it at /dev/sda (for instance) and it will fail using the regular grub, of course. I mean that the regular grub will fail. Then I install grub manually. So yes, you are right on the money here. I have no installer log anymore (?). But I think it should be clear enough already :). Well, perhaps not. But. Oh wait, it's on another /var Not there either. I will have to redo the install some time to find out. Other system Also nothing, I assume it gets wiped? Maybe it never gets created. The regular Grub will produce this error message on my system: /usr/sbin/grub-install: error: disk `lvmid/bn8p8J-Wr6M-Qzel-E0t8-8yOV- PbQN-TgKc6P/3Xl0mm-8loM-TcZ2-7pki-oF2S-MSEt-oBcPGT' not found. Which is a bit weird, I thought it would bug out on /dev/sda. But anyway, regular patched grub will say: Installation finished. No error reported. That's currently a git version (from Savannah) but the same for the Supplied Ubuntu version. Anyway, that's irrelevant. I indeed have a failing grub at install ;-). Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607687 Title: various packages show as installed, but files are not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1607687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593398] Re: cifs-utils corrupt (Kubuntu 16.04)
Reproduced it on another Kubuntu 16.04 install. Trying to mount an fstab-mentioned share as mentioned before; not using ip= or passwd= This is the output in dmesg: [25771.049320] FS-Cache: Netfs 'cifs' registered for caching [25771.049481] Key type cifs.spnego registered [25771.049497] Key type cifs.idmap registered [25771.049954] Unable to determine destination address. After reinstall: apt install --reinstall cifs-utils. No dmesg output, the mount just succeeds. The mount output had exited my buffer, So I copied it from stackexchange: "mount: wrong fs type, bad option, bad superblock on xxx.xxx.x.x:/share, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog - try dmesg | tail or so." That question also has people reporting the same thing: http://askubuntu.com/questions/525243/why-do-i-get-wrong-fs-type-bad- option-bad-superblock-error One person mentions: I had to reinstall cifs-utils on my system for some reason, it said it was installed, but the file at /sbin/mount.cifs was missing. (May 25) I hope this is enough now. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593398 Title: cifs-utils corrupt (Kubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1593398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608522] [NEW] ntfs-clone and bzip2 parallel don't work
Public bug reported: Just reporting that of the installable 16.04 clonezilla package, both the ntfs-clone mode and the b2p modes don't work. ntfs-clone refuses to get started, and b2p will not give an indication but the thing will just fail. Bzip2 is installed so that can't be it, I think it is automatically installed. That's all I can say. Gzip-parallel works and the other clone commands also work. As far as I can see. So then what remains is xz but they don't have parallel (shame on them). Regards. ** Affects: clonezilla (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/1608522 Title: ntfs-clone and bzip2 parallel don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clonezilla/+bug/1608522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593398] Re: cifs-utils corrupt
I would need to run the Kubuntu live DVD to report exact output because I cannot reproduce it on a system on which I already fixed it. However I have now found another package for which is has happened. I will post a bug for that as well. But for convenience: package "dmraid" had all files in /usr/share/doc/dmraid missing (if not more). package "libdmraid1.0.0.rc16" had the file libdmraid.so.1.0.0.rc16 missing (if not more). Link: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1607687 ** Summary changed: - cifs-utils corrupt + cifs-utils corrupt (Kubuntu 16.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593398 Title: cifs-utils corrupt (Kubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1593398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607687] [NEW] dmraid and libdmraid missing files (Kubuntu 16.04)
Public bug reported: In addition to an earlier bug report (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1593398) I have found another package with missing files on a system that was installed per the Kubuntu 16.04 64-bit ISO. Package _dmraid_ was installed and I could display its file list with dpkg -L dmraid. dmraid/xenial,now 1.0.0.rc16-4.2ubuntu3 amd64 [installed] /. /usr /usr/share /usr/share/bug /usr/share/bug/dmraid /usr/share/bug/dmraid/script /usr/share/initramfs-tools /usr/share/initramfs-tools/hooks /usr/share/initramfs-tools/hooks/dmraid /usr/share/initramfs-tools/scripts /usr/share/initramfs-tools/scripts/local-top /usr/share/initramfs-tools/scripts/local-top/dmraid /usr/share/doc /usr/share/doc/dmraid /usr/share/doc/dmraid/README /usr/share/doc/dmraid/TODO /usr/share/doc/dmraid/CREDITS /usr/share/doc/dmraid/copyright /usr/share/doc/dmraid/KNOWN_BUGS /usr/share/man /usr/share/man/man8 /usr/share/man/man8/dmevent_tool.8.gz /usr/share/man/man8/dmraid.8.gz /lib /lib/udev /lib/udev/rules.d /lib/udev/rules.d/97-dmraid.rules /sbin /sbin/dmraid /sbin/dmraid-activate /usr/share/doc/dmraid/changelog.Debian.gz When I went to /usr/share/doc/dmraid, the directory was empty # cd /usr/share/doc/dmraid # vi README # ls # vdir total 0 I reinstall apt install --reinstall dmraid # ls changelog.Debian.gz copyright CREDITS KNOWN_BUGS README TODO Now I run dmraid -l # dmraid -l dmraid: error while loading shared libraries: libdmraid.so.1.0.0.rc16: cannot open shared object file: No such file or directory # apt-file search libdmraid.so.1.0.0.rc16 libdmraid1.0.0.rc16: /lib/libdmraid.so.1.0.0.rc16 # apt list libdmraid* Listing... Done libdmraid-dev/xenial 1.0.0.rc16-4.2ubuntu3 amd64 libdmraid1.0.0.rc16/xenial,now 1.0.0.rc16-4.2ubuntu3 amd64 [installed] # apt install --reinstall libdmraid1.0.0.rc16 # ls changelog.Debian.gz copyright CREDITS KNOWN_BUGS README TODO <-- the link previously to changelog.Debian.gz has turned white. I realize before it was broken, as it points to a file in the libdm directory. # dmraid -l asr : Adaptec HostRAID ASR (0,1,10) ddf1: SNIA DDF1 (0,1,4,5,linear) hpt37x : Highpoint HPT37X (S,0,1,10,01) hpt45x : Highpoint HPT45X (S,0,1,10) isw : Intel Software RAID (0,1,5,01) jmicron : JMicron ATARAID (S,0,1) lsi : LSI Logic MegaRAID (0,1,10) nvidia : NVidia RAID (S,0,1,10,5) pdc : Promise FastTrack (S,0,1,10) sil : Silicon Image(tm) Medley(tm) (0,1,10) via : VIA Software RAID (S,0,1,10) dos : DOS partitions on SW RAIDs # vdir total 24 lrwxrwxrwx 1 root root 42 feb 18 2014 changelog.Debian.gz -> ../libdmraid1.0.0.rc16/changelog.Debian.gz -rw-r--r-- 1 root root 8177 feb 18 2014 copyright -rw-r--r-- 1 root root 305 sep 16 2009 CREDITS -rw-r--r-- 1 root root 252 sep 16 2009 KNOWN_BUGS -rw-r--r-- 1 root root 3227 sep 16 2009 README -rw-r--r-- 1 root root 854 sep 16 2009 TODO Basically it is the same thing I have experienced with the Kubuntu 16.04 "cifs-utils" package; files were missing; or must have been missing. Upon first install, and (back then) upon load of the live DVD. There have been no actions on my system that could have wiped out the files of those packages (in isolation of anything else). Most other things just work and I have not had complaints of any other missing files, save for this one and cifs-utils, apparently. I will likely soon need to reinstall Kubuntu, so I can check the Live DVD for that. (A VirtualBox image of course would equally be possible). But I will wait with further investigation myself until I have booted that Live DVD. Regards. ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: dmraid (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/1607687 Title: dmraid and libdmraid missing files (Kubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1607687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593398] Re: cifs-utils corrupt
I experienced it both on the Kubuntu installer and on the Kubuntu installed system. On that fresh install / live Session I used: mount -t cifs //host/share /mnt -o username=xen and it would complain about not having enough parameters. It wanted to have both password and ipaddress on the command line. After doing apt reinstall cifs-utils (or equivalent) the command succeeded as normal, and it asked me for the password on a prompt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593398 Title: cifs-utils corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1593398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875343] Re: Stuck at "Saving installed packages..." when using a custom /var
It's just incredible isn't it. Something that someone could probably solve in 30 minutes, and it cost me another hour. Multiply that with all the people being affected by this, and you will realize how inefficient this system is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875343 Title: Stuck at "Saving installed packages..." when using a custom /var To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/875343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593398] [NEW] cifs-utils corrupt
Public bug reported: This isn't really a bug against ubiquity. It's just that on installs of Kubuntu 16.04, the package "cifs-utils" IS installed but it is borked. MAYBE I AM MISTAKEN AND IT IS JUST A VERSION DIFFERENCE. But after reinstalling, mount -t cifs works as normal, but before reinstalling, it requires full parameters. ie. after reinstall, it is sufficient to type : mount //host/share /mnt -t cifs -o username=bla before, it requires: IP, and password on options line. So although I cannot check now; it seems that there were files missing from that package that ought to be installed. ** Affects: ubiquity (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/1593398 Title: cifs-utils corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1593398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489530] [NEW] Kubuntu installer fails when mounted parts, does not restart
Public bug reported: When, from the Live CD you have mounted partitions resulting from manual operation prior to initiating the install (of Kubuntu) the installer will ask whether to unmount, or to continue after you have fixed the issue of mounted partitions. However, after you've unmounted the partition(s) and click continue, the installer will hang. Recently, today, it hung on "Discovering filesystems" or something of the kind -- the first step in the background installation. This has been true for 14.10 as well, it is a long-standing problem. After you have then closed the installer, it will not run again. It will not start up again. Killing /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity kde_ui will solve the problem of the installer not reappearing. I'm not attaching partman as I feel my system is personal and private. Equal for syslog. It is easy to reproduce this. The configuration uses LUKS and an LVM inside the LUKS partition, with a separate /boot on a primary partition (or currently, inside the extended partition. I don't think there is anything special about the system, that might just be me. But I have had it more often, because I always do manual partitioning with my own LUKS. I always run into this problem when I forget to unmount before starting the installation (but after fixing all the mount points). # lsb_release -rd Description:Ubuntu Wily Werewolf (development branch) Release:15.10 ** Affects: ubiquity (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/1489530 Title: Kubuntu installer fails when mounted parts, does not restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1489530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845914] Re: Failsafe boot delay causes a real delay on every boot
*** This bug is a duplicate of bug 847782 *** https://bugs.launchpad.net/bugs/847782 Introducing any kind of script to /etc/network/if-up.d/ that exits with error for eth0 (or in any case static interfaces?) will cause this script to fail, ie. introduce the 120 sec boot delay. I think it is really bad behavior to consider static network up a must for booting. Static services would already have executed (or tried to execute) from /etc/network/if-up.d/ and they failed if they came after the failing script. In other words run-parts is executed with the fail-on-fail option (the default). Should network fail really cause a boot delay? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845914 Title: Failsafe boot delay causes a real delay on every boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/845914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440295] Re: 14.10 to 15.04: Cannot handle manual dpkg --configure prompts
I started this upgrade from Muon Updater with the "Upgrade" button in the top right. After restarting that program, I am prompted with a KWallet migrate. Typically, it also currently wants me to upgrade a package for a third party internet browser. IT STILL SAYS a new version of my system is available, and I get the "Welcome to the Ubuntu 'Vivid Vervet' development release" release notes screen. I still have not rebooted. will see next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440295 Title: 14.10 to 15.04: Cannot handle manual dpkg --configure prompts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1440295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440295] [NEW] 14.10 to 15.04: Cannot handle manual dpkg --configure prompts
Public bug reported: The python script (and graphical interface) will hang when dpkg --configure (most likely, I was running dpkg --configure -a afterward) starts asking questions on how to proceed with changed config files. When there are a number of files that need to be updated, and the user has edited or changed some of them, even just a single one can cause the installer to completely hang. The button "Show Terminal" is or becomes unresponsive. After doing manual dpkg --configure -a, and rerunning the upgrader, it will say "Could not run the upgrade tool." (window title) --> "Could not run the upgrade tool. This is most likely a bug in the upgrade tool. Please report it as a bug using the command 'ubuntu-bug ubuntu-release- upgrader-core'." However, the report bug feature also fails: Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 530, in sys.exit(UserInterface.run_argv()) File "/usr/lib/python3/dist-packages/apport/ui.py", line 650, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 488, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File "/usr/share/apport/apport-kde", line 367, in ui_present_report_details desktop_info) File "/usr/share/apport/apport-kde", line 184, in __init__ self.ui.ui_update_view(self) File "/usr/share/apport/apport-kde", line 358, in ui_update_view QTreeWidgetItem(keyitem, [line]) TypeError: index 0 has type 'bytes' but 'str' is expected For good measure: this was an upgrade from KUBUNTU 14.10 Utopic Unicorn. The output of apt-cache policy ubuntu-release-upgrader-core is: ubuntu-release-upgrader-core: Installed: 1:15.04.13 Candidate: 1:15.04.13 Version table: *** 1:15.04.13 0 500 http://nl.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status But this is obviously after the upgrade. The system prior to upgrade was a regular 14.10 with a few minor tweaks. There is another error that popped up, it may be coming from muon- upgrader or that python thing at the same time as the other error (dialog) (popup) and that is that "Verifying the upgrade failed. There may be a problem with the network or with the server." (It appears as though after the dpkg --configure -a, my install is complete, ie. I have upgraded to Vivid. I have not rebooted yet though.) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: utopic vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440295 Title: 14.10 to 15.04: Cannot handle manual dpkg --configure prompts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1440295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
