I am having the same trouble, but during INSTALLATION, I already
installed Ubuntu 20.04 twice and I haven't access to it yet. The first
time I got black screen (with safe graphics installation) then normal
installation didn't let me to install, and I try to reinstall with safe
graphics again. I got
Public bug reported:
it failed to start streamcli first, all I know so far
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apt-clone 0.4.1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architectur
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/990275
Title:
package gettext-base 0.18.1.1-5ubuntu3 failed to install/upgrade:
gettext-base:i386 0.18.1.1-5ubuntu3 (Multi-Arch
To manage notification
Public bug reported:
Ubuntu 12.04:
Selecting previously unselected package gettext-base:i386.
dpkg: error processing
/var/cache/apt/archives/gettext-base_0.18.1.1-5ubuntu3_i386.deb (--unpack):
gettext-base:i386 0.18.1.1-5ubuntu3 (Multi-Arch: no) is not co-installable
with gettext-base:amd64 0.
*** This bug is a duplicate of bug 861584 ***
https://bugs.launchpad.net/bugs/861584
Also present in package version 10.3.183.10ubuntu5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859225
Title:
Public bug reported:
Binary package hint: ghc6
As per
http://darcs.haskell.org/ghc-6.6/packages/unix/System/Posix/DynamicLinker/Prim.hsc
and http://darcs.haskell.org/packages/unix/include/HsUnix.h, ghc6 (or is
it libghc6-unixutils-dev?) needs to be compiled with the HAVE_RTLDNEXT
flag for its dls
Public bug reported:
Binary package hint: mono
This bug is present in the mono runtime in the karmic i386 repository,
but it has been fixed in svn r147046. Any chance of backporting?
https://bugzilla.novell.com/show_bug.cgi?id=558774
** Affects: mono (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 429003 ***
https://bugs.launchpad.net/bugs/429003
oops sorry, tried to add that this affects the source package nvidia-
graphics-drivers-185 but ended up pointing to nvidia-graphics-
drivers-180 instead, which is unrelated.
** Also affects: xorg (Ubuntu)
Public bug reported:
Binary package mpeg4ip-server version 1:1.6dfsg-0.2ubuntu4 (x86_64) from
karmic/multiverse depends on libx264-65 (>= 1:0.svn20081230) but it does
not exist. Looks like that library was dropped in favor of libx264-67.
# apt-get install mpeg4ip-server
...
The following package
Architecture: amd64
CRDA:
country 98:
(2402 - 2472 @ 40), (3, 27)
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: network-manager 0.8~a~git.20090820t182117.cb60390-0ubuntu2
PackageArchitecture: amd64
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
Proc
Architecture: amd64
CRDA:
country 98:
(2402 - 2472 @ 40), (3, 27)
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: network-manager 0.8~a~git.20090820t182117.cb60390-0ubuntu2
PackageArchitecture: amd64
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
Proc
Note that since filing the initial bug report I've upgraded to karmic.
The behavior is the same though.
Also, when trying to submit the apport data as requested, apport sort of
died..
$ apport-collect 413868
Logging into Launchpad...
Downloading bug...
Bug title: NetworkManager adds incorrect rou
are the Ctrl-C and screen issues listed as separate bugs or is it really
the same problem?
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
Binary package hint: network-manager
# apt-cache policy network-manager network-manager-pptp pptp-linux ppp
network-manager:
Installed: 0.7.1~rc4.1.cf199a964-0ubuntu2
Candidate: 0.7.1-0ubuntu1ocdc3+jaunty
Version table:
0.7.1-0ubuntu1ocdc3+jaunty 0
500 http
Public bug reported:
The option "--swapsize 0" currently throws an exception -- I guess
vmbuilder tries to add a 0-sized partition to the virtual disk.
In the cli module, in its CLI class, in its set_disk_layout method, the
code says:
if vm.hypervisor.preferred_storage ==
VMBuilder.
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/29398304/Dependencies.txt
--
vmbuilder does not respect flavour option
https://bugs.launchpad.net/bugs/403144
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Public bug reported:
vmbuilder is producing VMs with the server kernel even when asked
explicitly to use the virtual kernel. For example:
$ ubuntu-vm-builder esxi jaunty --flavour virtual --arch i386 --ip 10.160.2.10
--mask 255.255.0.0 --gw 10.160.0.1 --rootsize 512 --user ubuntu --name Ubuntu
Here's a bzr diff. Sorry for the delay -- I just noticed that last
comment.
** Attachment added: "patch: no-maximize vs bzr"
http://launchpadlibrarian.net/23723523/maximus-only-maximized.bzr.patch
--
[PATCH] option to not automatically maximize new windows
https://bugs.launchpad.net/bugs/322
** Also affects: maximus
Importance: Undecided
Status: New
--
[PATCH] option to not automatically maximize new windows
https://bugs.launchpad.net/bugs/36
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Public bug reported:
Binary package hint: readahead-list
in readahead-watch.c, in watch_directory, the following code block:
/* Add a watch on the directory */
wd = inotify_add_watch (inotify_fd, queue->path,
IN_OPEN | IN_CL
Thanks for the quick reply. Here's a new patch that includes a gconf
option, /apps/maximus/no_maximize, to control the behavior. The
command-line option overrules the gconf setting in case they differ.
** Attachment added: "patch: no-maximize option via both commandline and gconf"
http://laun
** Attachment added: "patch: option to not automatically maximize new windows"
http://launchpadlibrarian.net/21707193/maximus-only-maximized.patch
--
[PATCH] option to not automatically maximize new windows
https://bugs.launchpad.net/bugs/36
You received this bug notification because you
Public bug reported:
Binary package hint: maximus
Included is a patch that gives the user the option to not maximize every
newly opened window. Windows that are opened already maximized are
still undecorated as expected.
The attached patch is against maximus version 0.4.2~ppa1 from the
netbook-
I also get a blank vt1 with that same package, but my X screen stays
blank when I switch back to vt7 -- I have to kill X (or gdm) blindly
from vt1, or blindly start a new X server (startx :1) for the display to
come back.
Are you using a console framebuffer? uvesafb?
--
Can't VT switch from X
h
24 matches
Mail list logo
