[Bug 1898891] Re: anacron cron.weekly error: AttributeError: module 'platform' has no attribute 'linux_distribution'
Adding a "me too". Upgraded from 18 to 20 (both LTS) and am now getting this same error (with identical traceback as above). It seems that /usr/share/software- center/softwarecenter/distro/__init__.py calls platform.linux_distribution(), which no longer exists. >From stackoverflow (where all of my knowledge of python resides), I find this, >at >https://stackoverflow.com/questions/63636697/error-module-platform-has-no-attribute-linux-distribution > : "Python 3.8 removed the "linux_distribution()" function from the platform module. It is replaced by the equivalent in the "distro" module (distro is not built-in to Python and must be installed via pip)." For me, since I don't believe I've ever once used the index built by apt-xapian-index, and it's only a recommendation, I've simply removed the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898891 Title: anacron cron.weekly error: AttributeError: module 'platform' has no attribute 'linux_distribution' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1898891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
I've upgraded 4 systems from 18.04 to 20.04, and only one has shown this behavior. Will attach an strace of the focal process. I ran the strace for approximately 30 seconds. ** Attachment added: "strace of the python focal process, while bug is occurring" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+attachment/5419188/+files/focal.strace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 800701] Re: init: plymouth-stop pre-start process terminated with status 1(plymouth-stop called multiple times due to race?)
as further background information on possible causes for this: the message in question will occur in the log any time upstart is told to (re)enter runlevel 2. i.e, if you type telinit 2, you'll see the result both in the output of last -x head (because wtmp records the (null) level transition) and in the output of dmesg, where the plymouth-stop pre-start scriptlet records its demise. (also note that the script /etc/init/plymouth-stop.conf is *not* consulted when the addition to dmesg occurs -- ls -lu will show you that. the pre-start segment of that script seems to be cached elsewhere. this may not be relevant, but is simply a factoid i discovered while attempting to isolate the source of the terminated with status 1 message.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/800701 Title: init: plymouth-stop pre-start process terminated with status 1 (plymouth-stop called multiple times due to race?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/800701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917520] Re: Regression: mdadm drops to initramfs shell on unregistered array
*** This bug is a duplicate of bug 942106 *** https://bugs.launchpad.net/bugs/942106 i can't tell from the initial description whether or not there was a truly degraded array on his system. perhaps not, in which case the fixes described in #942106 would help. but since the topic of this bug very precisely describes my current issue, and my issue is definitely not a duplicate, i'm commenting here. i'm running oneiric. my root fs is _not_ a RAID disk. i have a single mirrored RAID pair, which is _not_ mentioned in mdadm.conf. this pair is _always_ degraded, intentionally so. so it's clearly important for my system to boot with it in a degraded state. [rationale, for the curious: the disk stores my BackupPC backup pool, which is extremely difficult (impossible, really) to copy (for offsite purposes) with standard rsync/cp tools, due to its huge numbers of hardlinks. it could be copied using dd, but that would involve taking the disk offline for long periods. instead, i do my backups to one half of a degraded RAID. when i want a copy for offsite storage i add the missing disk, sync it (which all happens with the pair online), then (the next day, when syncing is done) briefly shut down BackupPC, unmount the RAID pair, manually fail the offsite disk, remove it, and remount the now-degraded pair.] clearly, setting BOOT_DEGRADED will fix (i hope) my problem -- i only have one RAID, and maintain it in a somewhat unusual way. but i've been thinking of using RAID for my root disk soon. if i do, i may well not want to set BOOT_DEGRADED. so i'll be stuck. here's the critical part of the original description: The complete solution will be to provide BOOT_DEGRADED on a per array basis. and, as a corollary, booting shouldn't be prevented when degradation is detected in an array that's not even configured. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917520 Title: Regression: mdadm drops to initramfs shell on unregistered array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/917520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94065] Re: init: add non-destructive means to disable a job
expected to uninstall? says who? as the original submitter of this bug, let me be the one to point out this phrase from the description: this might be to temporarily disable a serial line getty, or whatever. that doesn't sound like a reason to uninstall to me. in any case, i think this bug has been fixed for some time: you can already comment out the start line, or, apparently, add a manual line. and if the (dumb, in my opinion) requirement for using a .conf suffix (why are we trying to reinvent DOS?) is fully implemented, then renaming the file to myservice.disabled should accomplish the same thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/94065 Title: init: add non-destructive means to disable a job -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94065] Re: init: add non-destructive means to disable a job
fair enough. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/94065 Title: init: add non-destructive means to disable a job -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 402759] Re: Scripts need to be migrated from /etc/event.d to /etc/init
echoing comment #11: where are the differences between the new and old formats documented? -- Scripts need to be migrated from /etc/event.d to /etc/init https://bugs.launchpad.net/bugs/402759 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 557177] Re: init: support mandatory arguments, or prevent starting of tasks without any arguments
with all due respect to scott, it wasn't just the -- Invalid that caused this tempest. it was the somewhat dismissive sounding 'Sorry, the only response here is Don't Do That Then', which helped reinforce the impression that this was a won't fix situation. but that aside, this thread was at least the second of the day in which the marking of the (ubuntu) version of a bug invalid caused confusion. it threw me off in https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/94065/comments/6 , even _with_ scott's explanation of what was going on. if it were possible to substitute something less terminal sounding than Invalid as the disposition in cases like this (Reclassified? Moved? Wrong 'affecting'?), it might help avoid future confusion. (i realize there's probably limited control over the nomenclature choices.) -- init: support mandatory arguments, or prevent starting of tasks without any arguments https://bugs.launchpad.net/bugs/557177 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 94065] Re: init: add non-destructive means to disable a job
where can i find the upstream bug? -- init: add non-destructive means to disable a job https://bugs.launchpad.net/bugs/94065 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 94065] Re: init: add non-destructive means to disable a job
sorry. clearly i didn't parse the status change attached to comment #6 correctly. i thought it was this bug that had been marked invalid. -- init: add non-destructive means to disable a job https://bugs.launchpad.net/bugs/94065 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 94065] Re: Add non-destructive means to disable a job
is there a disable method yet? i reported this initially over a year ago. (there may be, but since there's no upstart manpage on hardy, it's hard to know. :-) -- Add non-destructive means to disable a job https://bugs.launchpad.net/bugs/94065 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 237243] Re: hardy upgrade fails: essential package would have to be removed
this worked. perhaps do-release-upgrade could grow a manpage, or at least some more text in the usage message that describes the default behavior, and why one would use -m desktop. many thanks. -- hardy upgrade fails: essential package would have to be removed https://bugs.launchpad.net/bugs/237243 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 237243] [NEW] hardy upgrade fails: essential package would have to be removed
Public bug reported: Binary package hint: update-manager i'm running gutsy 7.10 (which was upgraded from feisty which was upgraded from edgy). i ran: apt-get update apt-get upgrade apt-get dist-upgrade do-release-upgrade which gave the message: Could not calculate the upgrade A unresolvable problem occurred while calculating the upgrade. as requested further in the message, i've attached the /var/dist-upgrade directory. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- hardy upgrade fails: essential package would have to be removed https://bugs.launchpad.net/bugs/237243 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 237243] Re: hardy upgrade fails: essential package would have to be removed
** Attachment added: the contents of /var/dist-upgrade directory http://launchpadlibrarian.net/14980684/dist-upgrade.tgz -- hardy upgrade fails: essential package would have to be removed https://bugs.launchpad.net/bugs/237243 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 173428] Re: [hardy] evdev mouse driver stops working
*** This bug is a duplicate of bug 173833 *** https://bugs.launchpad.net/bugs/173833 this is a result of the xorg folks changing the configuration parameters for evdev. the new config doesn't want Name or Phys config lines. it wants a Device line, like so: Option Device /dev/input/by-id/name-of-your-keyboard-or-mouse-here -- [hardy] evdev mouse driver stops working https://bugs.launchpad.net/bugs/173428 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 41056] Re: qiv fails to start: Gdk-ERROR **: BadMatch (invalid parameter attributes)
i can reproduce this, running qiv on feisty, and displaying to a remote X11 server that's running gutsy. let me know what i can do to help. the workaround (setting XLIB_SKIP_ARGB_VISUALS before running qiv) works for me. (i'm not sure how to reopen the bug. i'm happy to do so -- it's just not obvious where in the UI i should look. paul -- qiv fails to start: Gdk-ERROR **: BadMatch (invalid parameter attributes) https://bugs.launchpad.net/bugs/41056 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 3498] Re: Curses box uses wrong characters when X cannot start
i'm running feisty, and believe i have a simpler way of reproducing this problem. i have never, to my knowledge, changed my local/language/etc. (i'm in the US.) boot the system. don't bother logging in to gdm. switch directly to a console, with control-alt-F1. log in, and run: dialog --msgbox foo 0 0 observe funky box-drawing characters: inverted L shapes, downarrows, etc. run sudo /etc/init.d/console_setup restart rerun the dialog command and observe that the dialog box output is now correct. switch to the X11 vt, with alt-control-F7. don't log in. switch back to the console screen with alt-control-F1. observe that the dialog output (which should still be on the console) has now changed to funky. re-run the dialog command. observe that fresh painting still produces funky output. -- Curses box uses wrong characters when X cannot start https://bugs.launchpad.net/bugs/3498 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122680] no way to install a custom keymap
Public bug reported: in all previous releases of ubuntu or debian on which i've tried it, it was possible to somehow make changes to boottime.kmap and have the changes stick. (in particular, this is an easy and popular way of changing capslock to control for the console.) either the map file could be replaced, or references to it could be redirected, etc. but now, assuming ckbcomp is present (which it is), then the contents of boottime.kmap[.gz] is overwritten at every boot, based on the X11 keyboard files. there should be a way to prevent this action. i see that the console-screen.sh script (now superceded) provides for remap functionality. while not optimal, this kind of feature would be better than nothing. but really what's necessary is a variable that can be set in /etc/default/console-setup that allows setting an alternate boot-time keymap file. paul ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- no way to install a custom keymap https://bugs.launchpad.net/bugs/122680 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72058] Re: Documentation about vanished /etc/inittab should be added
i was just about to submit a similar bug, so i'll just augment this one. given that upstart is now completely central to the operation of the system, the documentation really needs to be more complete. in particular: * in addition to the above inittab(5) man page (which is not for initctl, as its name implies :-), both it and the existing init(8) stub should also point at /usr/share/docs/README.debian (or perhaps the same content under a different name -- one that doesn't need decompressing in order to read it). * there should be an upstart(8) man page, which fully documents the format of the event.d entries. i couldn't find a definitive document on the system or on the wiki (and it should be on the system). * initctl(8) needs to fully explain the output of initctl list -- Documentation about vanished /etc/inittab should be added https://launchpad.net/bugs/72058 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
