Sorry, this was a problem with my particular setup and not a general
bug. I had installed an older version of Boost. Removing that version
fixes the problem.
** Changed in: autodock-vina (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubun
Public bug reported:
In Ubuntu 14.04 one could build the source package autodock-vina by
following these instructions:
https://help.ubuntu.com/community/UpdatingADeb
In Ubuntu 15.10 he compilation fails with the following errors:
$ debuild -us -uc -i -I
dpkg-buildpackage -rfakeroot -D -us -uc
UPDATE2: No, the system hangs again during booting. I will try Ubuntu.
--
Blank screen at start of LiveCD install Mint 9 RC
https://bugs.launchpad.net/bugs/576808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
OK, left shift works to access to the GRUB menu. I think everything is
working now. Yet, this is not what I would call "user-friendly"
installation.
--
Blank screen at start of LiveCD install Mint 9 RC
https://bugs.launchpad.net/bugs/576808
You received this bug notification because you are a mem
UPDATE:
After waiting for a very long while (maybe half an hour) just with the
"nomodeset" option instead of "splash", the monitor started to display
weird things. Then, after a few minutes of showing weird stuff, finally
the desktop came up and installation was possible.
After installation, the
I have been unable to install Linux Mint 9 64-bit (final release) from
either de LiveCD or the LiveDVD edition.
First, I had the problem with the monitor being put to sleep. Replacing
the boot option "splash" with "nomodeset" prevents the monitor from
sleeping and I can see several error messages.
I have just installed Debian testing (2.6.32-trunk-amd64 SMP) with XFCE4
and all the issues are fixed:
1) No more video or audio flickering.
2) nvidia-settings reports the correct power source, either battery or
AC power.
3) Performance levels are adjusted as required, from 0 to 3, by
Powermizer
This appears to be a 64-bit specific issue.
--
Flickering when wathcing videos with Nvidia drivers in Lucid
https://bugs.launchpad.net/bugs/534047
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Reverting to the nv driver worsens the problem.
--
Flickering when wathcing videos with Nvidia drivers in Lucid
https://bugs.launchpad.net/bugs/534047
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
I guess this is not related, but, just in case, I would like to add that
nvidia settings always reports the laptop as being on battery even if on
AC power and even if the battery is absent.
--
Flickering when wathcing videos with Nvidia drivers in Lucid
https://bugs.launchpad.net/bugs/534047
You
Public bug reported:
Binary package hint: xorg
I am testing Lucid alpha 3. Fully upgraded. Since I installed the Nvidia
proprietary drivers I observe a slight flickering when watching videos.
The flickering occurs at irregular intervals (from a few seconds to
several minutes) and only last one or
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/40448954/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/40448955/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40448956/Dependencies.txt
** A
I tried Kubuntu 10.04 Alpha 3 and it works for me replacing "splash --"
with "vga=789". I have a black screen for some minutes but finally the
KDE splash screen shows up. I am sorry that this does not work for you,
but it can be useful for others.
Your problem appears to be more serious because yo
This also affects my laptop. The bug also happens installing from a USB
pen-drive.
The workaround is removing the "splash --" boot option and maybe adding
the vga mode "vga=xxx" which corresponds to your monitor (see Linux
video mode numbers in
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions). A
Public bug reported:
This bug affects Ubuntu 9.10 Karmic Koala AMD64 Alternate CD Alpha 4,
Alpha 5 and daily builds 16/09/2009.
After completing more than 70 % of the installation of the base system,
the installer requests the insertion of the installation CD. However,
the same installation CD is
The bug is fixed in Karmic Koala alpha 4 (kernel 2.26.31 RC5) and the
2.6.30 familiy is also bug-free to this respect.
Paradoxically, Koala seems faster and less bloated than Jackalope ;-)
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
A new kernel, 2.26.28-13 is available from the update repositories. Now
I guess that when someone installs Ubuntu from the CD image, the kernel
will be updated from 2.26.28-9 (which is known to be free from this bug)
to 2.26.28-13 (which I hope will be bug-free as well). So, practically
speaking, t
I cannot believe this bug is still open.
To all the people doing hardware diagnostics: This is not a hardware
issue. As far as I can tell, it affects exclusively to the Unbuntu
kernel 2.6.28-11. Any other kernel/distro I have tried (older or newer)
works perfectly. I am running 2.6.30 from kernel.
I agree that it is not acceptable to release a so called "stable"
version being aware of such a serious bug.
Fuchur:
I have compiled kernel 2.6.29.1 (2.6.29.2 is already available but I
have not tested it) a few weeks ago and I have not had any issues since
then.
You can download precompiled pac
@god-mok:
when you install a beta version you take some risks. as far as I know,
the problem only happens when you upgrade the kernel. so if you stick to
the kernel provided by the installation CD (2.6.28-9) until the problem
is solved, you should be safe. I guess this is a problem specific to the
Installing 9.04 beta (AMD) via the Live CD and then compiling the kernel
to 2.6.29.1 (before doing any other update via Aptitude/Synaptic)
renders a very stable and "performant" system.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
Hi Jon,
Thanks for your quick answer. The minor problems were bugs previously
reported (application crashes, true or false, etc.).
The problem is reproduced also with ext3. I have updated the
description.
No I have never had media issues with this laptop. I was running Ubuntu
Studio 8.10 until
** Attachment added: "lshw.log"
http://launchpadlibrarian.net/24465481/lshw.log
--
ext4 : file system corrupted and system unbootable
https://bugs.launchpad.net/bugs/350593
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Public bug reported:
I have installed the first beta version of Ubuntu 9.04 codenamed Jaunty
Jackalope (AMD64).
First I tried ext4 with a customized partition scheme. When installing
packages from Synaptic, the system starts to behave erratically. The
last thing I have the time to read, before it
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/21729448/Dependencies.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/21729449/DpkgTerminalLog.gz
--
package pulseaudio 0.9.10-2ubuntu9.3 failed to install/upgrade: subprocess
post-installat
Public bug reported:
Binary package hint: pulseaudio
during an automatic update of Ubuntu 8.10 64 bits I have received this
error message:
package pulseaudio 0.9.10-2ubuntu9.3 failed to install/upgrade:
subprocess post-installation script returned error exit status 1
this is all I know
Problem
No, I think the problem is solved with the 2.6.27 kernel. In any case,
I think that bcm43xx-fwcutter is an outdated package.
On Wed, Nov 12, 2008 at 5:36 AM, Daniel T Chen <[EMAIL PROTECTED]> wrote:
> Is this symptom still reproducible in 8.10?
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagenam
Public bug reported:
Binary package hint: linux-restricted-modules
I have an HP Pavilion dv5000 and a ASUS A6Tc. Both have the same
wireless card:
Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN
Controller (rev 02)
Using restricted drivers in Unbuntu, Debian and other syste
Public bug reported:
Binary package hint: bcm43xx-fwcutter
The newer versions of UBUNTU and DEBIAN allow to automatically download
and install firmware for several wireless cards using the (unmantained?)
package bcm43xx-fwcutter (instead of nsdiswrapper). Unsing this firmware
causes my laptop (AS
29 matches
Mail list logo
