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
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/+
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 transitio
*** 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
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.ubun
"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
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
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 a
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 Ubun
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:
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 a
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/
** 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
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
*** 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
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
n
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
c
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 --msgbo
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",
19 matches
Mail list logo
