[Bug 1805702] Re: dnet-common - post inst script update-rc.d has error
My officemate just ran into this while upgrading to 18.10, and changing update-rc.d decnet start\ 39\ S\ .\ \ stop\ 11\ 1\ . >/dev/null to (as I saw on my 18.04 system, where installing dnet-common *did* work) update-rc.d decnet start 39 S . stop 11 1 . >/dev/null seems to have resolved it; installation then completes as follows: Preconfiguring packages ... dnet-common: Skipping configure of DECnet Selecting previously unselected package dnet-common. (Reading database ... 1140653 files and directories currently installed.) Preparing to unpack .../dnet-common_2.65_all.deb ... Unpacking dnet-common (2.65) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10.9) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Setting up dnet-common (2.65) ... dnet-common: Skipping configure of DECnet update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start runlevel arguments (S) do not match decnet Default-Start values (2 3 4 5) update-rc.d: warning: stop runlevel arguments (1) do not match decnet Default-Stop values (0 1 6) Processing triggers for systemd (237-3ubuntu10.9) ... Processing triggers for ureadahead (0.100.0-20) ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805702 Title: dnet-common - post inst script update-rc.d has error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnprogs/+bug/1805702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791853] Re: Postfix upgrade queries about replacing /etc/postfix/makedefs.out, when it really should always do so
Note that I attempted to file a bug upstream with Debian too (since that's where this packaging choice originated), but I think I might have mucked up the reporting format as I see no indication my bug ever reached upstream. ** Description changed: When upgrading Postfix, I was surprised to be asked Configuration file '/etc/postfix/makedefs.out' - ==> Modified (by you or by a script) since installation. - ==> Package distributor has shipped an updated version. -What would you like to do about it ? Your options are: - Y or I : install the package maintainer's version - N or O : keep your currently-installed version - D : show the differences between the versions - Z : start a shell to examine the situation - The default action is to keep your current version. + ==> Modified (by you or by a script) since installation. + ==> Package distributor has shipped an updated version. + What would you like to do about it ? Your options are: + Y or I : install the package maintainer's version + N or O : keep your currently-installed version + D : show the differences between the versions + Z : start a shell to examine the situation + The default action is to keep your current version. *** makedefs.out (Y/I/N/O/D/Z) [default=N] ? - This would appear to have been added with version 3.1.4-1, specifically: - * Install /etc/postfix/makedefs.out so users can see how the package + * Install /etc/postfix/makedefs.out so users can see how the package was built which is a laudable and understandable goal. However, it seems quite unequivocal that the package-provided version of this file should always be used when installing the package, since the file itself opens with the following line: - # Do not edit -- this file documents how Postfix was built for your + # Do not edit -- this file documents how Postfix was built for your machine. There does not seem to be a valid reason for a user to have a version of that file that differs at all from the package-provided version, then; any divergence, in fact, would be misleading. Presumably then this file should be included in a way that does not require user intervention to update the makedefs.out file (ex. the /etc/ copy could just be a symlink to a copy in /usr/share/postfix/, or perhaps there's some packaging magic that could be done?). - (I suppose I should probably have filed this bug upstream with Debian, - but I don't actually have any Debian systems running Postfix at the - moment, only Ubuntu Server ones.) + Ran into this on a server running Ubuntu 18.04. ** Description changed: When upgrading Postfix, I was surprised to be asked Configuration file '/etc/postfix/makedefs.out' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** makedefs.out (Y/I/N/O/D/Z) [default=N] ? This would appear to have been added with version 3.1.4-1, specifically: * Install /etc/postfix/makedefs.out so users can see how the package was built which is a laudable and understandable goal. However, it seems quite unequivocal that the package-provided version of this file should always be used when installing the package, since the file itself opens with the following line: # Do not edit -- this file documents how Postfix was built for your machine. There does not seem to be a valid reason for a user to have a version of that file that differs at all from the package-provided version, then; any divergence, in fact, would be misleading. Presumably then this file should be included in a way that does not require user intervention to update the makedefs.out file (ex. the /etc/ copy could just be a symlink to a copy in /usr/share/postfix/, or perhaps there's some packaging magic that could be done?). - Ran into this on a server running Ubuntu 18.04. + Ran into this on a server running Ubuntu 18.04, when running upgrades + which pulled down Postfix version 3.3.0-1ubuntu0.1. ** Bug watch added: Debian Bug tracker #908545 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908545 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791853 Title: Postfix upgrade queries about replacing /etc/postfix/makedefs.out, when it really should always do so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1791853/+subscriptions -- ubuntu-bugs mailing list
[Bug 1791853] Re: Postfix upgrade queries about replacing /etc/postfix/makedefs.out, when it really should always do so
I stand corrected: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=908545 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791853 Title: Postfix upgrade queries about replacing /etc/postfix/makedefs.out, when it really should always do so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1791853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791853] [NEW] Postfix upgrade queries about replacing /etc/postfix/makedefs.out, when it really should always do so
Public bug reported: When upgrading Postfix, I was surprised to be asked Configuration file '/etc/postfix/makedefs.out' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** makedefs.out (Y/I/N/O/D/Z) [default=N] ? This would appear to have been added with version 3.1.4-1, specifically: * Install /etc/postfix/makedefs.out so users can see how the package was built which is a laudable and understandable goal. However, it seems quite unequivocal that the package-provided version of this file should always be used when installing the package, since the file itself opens with the following line: # Do not edit -- this file documents how Postfix was built for your machine. There does not seem to be a valid reason for a user to have a version of that file that differs at all from the package-provided version, then; any divergence, in fact, would be misleading. Presumably then this file should be included in a way that does not require user intervention to update the makedefs.out file (ex. the /etc/ copy could just be a symlink to a copy in /usr/share/postfix/, or perhaps there's some packaging magic that could be done?). (I suppose I should probably have filed this bug upstream with Debian, but I don't actually have any Debian systems running Postfix at the moment, only Ubuntu Server ones.) ** Affects: postfix (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/1791853 Title: Postfix upgrade queries about replacing /etc/postfix/makedefs.out, when it really should always do so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1791853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037607] Re: vmbuilder completely fails on Quantal due to kernel pae detection failure
Last time I built a VM I tried using uvtool instead of vmbuilder or using an installer ISO directly, and it seemed to go fine. From a cursory look, it seems like uvt is the current way to build VMs, and the vmbuilder script has fallen entirely by the wayside. https://help.ubuntu.com/lts/serverguide/cloud-images-and-uvtool.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037607 Title: vmbuilder completely fails on Quantal due to kernel pae detection failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1037607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial
** Tags added: i386 plasma5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547297 Title: No auto login in Ubuntu GNOME Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1547297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial
Also observed this testing the Beta iso today for Kubuntu i386, so it's not gdm specific per se. ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to sddm in Ubuntu. https://bugs.launchpad.net/bugs/1547297 Title: No auto login in Ubuntu GNOME Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1547297/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1309803] Re: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04
Unfortunately, Christopher, because other issues (hardware, actually) forced me to reinstall entirely anyways in the intervening months, I no longer have quite the same software and hardware stack I previously did and thus can no longer provide any debugging information (positively for me this means I am no longer experiencing the problem, but alas that does not help much in terms of resolving it for others). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309803 Title: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1309803] Re: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04
I had deliberately avoided closing because another person had reported having the same issue, but fair enough. On Mon, Nov 17, 2014, 14:11 Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Keith Z-G, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309803/comments/8 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1309803 Title: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ 1309803/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309803 Title: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314301] [NEW] /etc/xdg/midori/config sets homepage=file:///usr/share/ubuntu-artwork/home/index.html which isn't present in derivatives
Public bug reported: /etc/xdg/midori/config contains: [settings] homepage=file:///usr/share/ubuntu-artwork/home/index.html which naturally isn't present in derivatives, and so in for example Kubuntu (and presumably any derivative distribution that doesn't unclude the ubuntu-artwork package) you get an ugly Error opening file: No such file or directory as your default homepage. Looking at the dependencies, merely making ubuntu-artwork a dependency of midori wouldn't be good, since it pulls in a bunch of cruft that folks running other desktops wouldn't need namely a bevy of GTK theme packages). But looking upstream, Debian defaults to homepage=file:///usr/share/doc/midori/faq.html which is in fact installed by the midori package in the Ubuntu repos, and so seems like an entirely reasonable, DE-agnostic choice. ** Affects: midori (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/1314301 Title: /etc/xdg/midori/config sets homepage=file:///usr/share/ubuntu- artwork/home/index.html which isn't present in derivatives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/midori/+bug/1314301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309803] Re: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04
Seems to reappear every second reboot, perplexingly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309803 Title: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1309803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309803] [NEW] Oscillating speed (of key repeat, animations, etc) after upgrade to 14.04
Public bug reported: After my upgrade to 14.04, I rebooted and logged in again. I noticed that several aspects, including key repeating, seemed to accelerate in their speed over a short period of time, and then at the peak of speed (such that, for example, the quickest key press I could manage would nonetheless print at least 15 of the key, and the page loading animation in Chrome tabs was spinning quicker than the eye could distinguish) it would suddenly drop back down to what appears to be the base set rate. I switched to VT1 and saw this happen there too, so it wasn't merely confined to KDE or even X11. Upon rebooting again, the problem had vanished. I was encouraged on #kubuntu to submit a bug, so here we are! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Fri Apr 18 17:27:38 2014 InstallationDate: Installed on 2013-12-12 (127 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu trusty ** Package changed: xorg (Ubuntu) = ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309803 Title: Oscillating speed (of key repeat, animations, etc) after upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1309803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309803] Re: Oscillating speed (of key repeat, animations, etc) after upgrade to 14.04
Has reappeared after another reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309803 Title: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1309803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309803] Re: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04
I've further noticed that the clock has gone off by almost 40 minutes since the upgrade, so it really does seem to have something to do with (to put it somewhat philosophically) the PC's perception of time. As such I'm unsure if it might just be an unfortunately timed hardware issue. ** Summary changed: - Oscillating speed (of key repeat, animations, etc) after upgrade to 14.04 + Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309803 Title: Oscillating speed (of key repeat, animations, time, etc) after upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1309803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268652] Re: Please update libssh to 0.6.0
Yeah, this would be greatly appreciated, as it would fix https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1176970 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268652 Title: Please update libssh to 0.6.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1268652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1154405] [NEW] Inaccurate free space calculation for NTFS partition
Public bug reported: On a Windows 7 laptop (Acer Aspire 6920G) running Windows 7 64-bit, I had deleted a bunch of data from within Windows, then rebooted to install a dual-boot with the Kubuntu Raring Beta 1. However, the option to auto-resize was missing, and the installer appeared to believe that the main partition was 93% full, which sounds about what it was before I cleaned it up from within Windows. Windows and GParted, by contrast, peg the free space at ~60%. In Windows, Disk Management appears to show the disk as being Basic, presumably meaning it *isn't* under the purview of the Logical Disk Manager. A screenshot of this can be seen at http://keithzg.ca/images/utility/acer_diskmgmtmsc.png or as the attachment (not sure which is better; apologies, first time actually opening a bug!). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.13.13.1 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 CasperVersion: 1.330 Date: Wed Mar 13 02:05:02 2013 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash -- LiveMediaBuild: Kubuntu 13.04 Raring Ringtail - Alpha amd64 (20130311.1) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ubiquity-2.13.13.1 ** Attachment added: diskmgmt.msc screenshot https://bugs.launchpad.net/bugs/1154405/+attachment/3571291/+files/acer_diskmgmtmsc.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1154405 Title: Inaccurate free space calculation for NTFS partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1154405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864595] Re: 11.10-beta2 installation fails if root partition is btrfs due to lack of free space
Having the same problem at this very moment with an 11.10 netinstall. So . . . I just can't use btrfs? That's kindof silly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864595 Title: 11.10-beta2 installation fails if root partition is btrfs due to lack of free space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/864595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192382] Re: alsamixer broken in hardy - intel hda
Confirmed here, also intel, blah blah (my laptop is a generic-brand, I don't have it bootable right now but I think we know by this point the specific hardware isn't entirely important). I'm thinking users not being able to control volume levels? Umm, high importance in my opinion. -- alsamixer broken in hardy - intel hda https://bugs.launchpad.net/bugs/192382 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141418] Re: klauncher crashed with SIGSEGV in __kernel_vsyscall()
I will add the me too for the bug report, exactly the same as everyone else is reporting (to be specific about my case I mainly use KDE3, and I use KDM instead of KDM-KDE4, but I also have KDE4 installed and it was the first time I logged into GNOME (ubuntu-studio to be precise) since updating to try out Hardy). -- klauncher crashed with SIGSEGV in __kernel_vsyscall() https://bugs.launchpad.net/bugs/141418 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
