Hello. I'm a beginner who are getting started learning Openstack and SDN. I'd
wanna implement OpenStack based Cloud over SDN networks, and I noticed that a
Plugin which connects Neutron with OpenFlow Controller. I've found a few
open-software OF controllers provide such Plugin, e.g., NEC Plugin
This bug was fixed in the package logcheck - 1.3.17
---
logcheck (1.3.17) unstable; urgency=low
[ Hannes von Haugwitz ]
* debian/control:
- dropped obsolete Replaces fields
- removed 'deprecated' notice from logtail's short description
- bumped to Standards-Version
** Patch added: untested
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1381537/+attachment/4244576/+files/dovcot12-sslv3-disable.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
Made a quick patch for this package, tested it in following way:
* Install package
* Start dovecot
* Connect with: openssl s_client -connect -ssl3 localhost:995
Getting error that I can't connect on SSLv3.
Please review.
** Patch removed: untested
** Patch removed: dovecot12-sslv3-disable.diff
https://bugs.launchpad.net/ubuntu/precise/+source/dovecot/+bug/1381537/+attachment/4244579/+files/dovecot12-sslv3-disable.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot
Made a quick patch for this package, tested it in following way:
* Install package
* Start dovecot
* Connect with: openssl s_client -connect -ssl3 localhost:995
Getting error that I can't connect on SSLv3, assumed this resolved the
issue.
** Patch added: dovecot12-sslv3-disable.diff
I guess this issue might be a manifestation of bug 1370570
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384109
Title:
Mechanism driver 'l2population' failed in
This bug was fixed in the package screen - 4.2.1-3
---
screen (4.2.1-3) unstable; urgency=low
* Cherry-pick 7d8fd3ad from upstream to fix segfaults with full screen
text-mode applications and altscreen on (Closes: #681572)
* Cherry-pick 8ffd5f46 from upstream to fix
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: open-vm-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
Public bug reported:
I home you can get more information out of this than I can. I was
trying to install either Rosegarden or Musescore with some if their add-
ons.
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: kfind 4:4.14.1-0ubuntu1
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 1367017 ***
https://bugs.launchpad.net/bugs/1367017
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1367017, so is being marked as such.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385584
Title:
package kfind 4:4.14.1-0ubuntu1 failed to install/upgrade: package is
in a very bad inconsistent
This bug was fixed in the package sl-modem - 2.9.11~20110321-11
---
sl-modem (2.9.11~20110321-11) unstable; urgency=medium
* debian/sl-modem-daemon.init: Source /lib/lsb/init-functions in init
script.
* Added fix_perms.diff to fix module build failure against linux kernel
This bug was fixed in the package xfce4-quicklauncher-plugin - 1.9.4-11
Sponsored for Jackson Doak (noskcaj)
---
xfce4-quicklauncher-plugin (1.9.4-11) unstable; urgency=low
[ Evgeni Golov ]
* Correct Vcs-* URLs to point to anonscm.debian.org
[ Yves-Alexis Perez ]
*
This bug was fixed in the package xfce4-verve-plugin - 1.0.0-3
Sponsored for Jackson Doak (noskcaj)
---
xfce4-verve-plugin (1.0.0-3) unstable; urgency=low
[ Evgeni Golov ]
* Correct Vcs-* URLs to point to anonscm.debian.org
[ Yves-Alexis Perez ]
* debian/control:
-
Because of this critical bug I am downgrading to 14.04. This is the sort
of problem that should be fixed in the beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129409
Title:
Nvidia and AMD
You must install the linux-tools-generic package which provides right
packages. There's usbip and usbipd included
(http://packages.ubuntu.com/utopic/amd64/linux-
tools-3.16.0-23-generic/filelist).
@Tim Gardner: shouldn't the usbip package be removed from the repository
I met the same problem in 14.04 LTS, pidgin version 2.10.9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245666
Title:
Pidgin is creating zombies with 13.10
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Tim Gardner: could it be that there's a missing line in
debian/rules.d/3-binary-indep.mk?
after ifeq ($(do_tools_common),true), you install the usbip client,
but the usbipd daemon is missing. I think, there should be a line
install -m755 debian/tools/generic $(toolsbin)/usbipd.
--
You received
Hi,
I just wanted to mention that I could upgrade the HWE on 12.04 using the
post-release AMD driver.
Thanks a lot, best regards,
Michael
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254424
*** This bug is a duplicate of bug 1367017 ***
https://bugs.launchpad.net/bugs/1367017
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1367017, so is being marked as such.
*** This bug is a duplicate of bug 1367017 ***
https://bugs.launchpad.net/bugs/1367017
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1367017, so is being marked as such.
Utopic is released now.
** Changed in: libvdpau (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377421
Title:
FFe: Sync libvdpau 0.8-1 (main) from Debian sid
I wasn't able to build and test the rev-deps, also utopic is released
now.
** Changed in: libva (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377423
Title:
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385510
Title:
CONFIG_SOUND_OSS_CORE_PRECLAIM Flag Set to Yes
To manage notifications about this bug go to:
Hello. I'm a beginner who are getting started learning Openstack and SDN. I'd
wanna implement OpenStack based Cloud over SDN networks, and I noticed that a
Plugin which connects Neutron with OpenFlow Controller. I've found a few
open-software OF controllers provide such Plugin, e.g., NEC Plugin
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385596
Title:
package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade:
underproces installerede
Graphics ard is NVIDIA GT218 (GForce 210)
Tried changing from X. Org X driver to NVIDIA 331.89 (from 331 prop. tested).
After reboot the addiitonal drivers windows said Using the recommended driver
- however desktop display was worse: still showing the ghosting of blurred
previosu windows, and
Public bug reported:
Der opstod fejl under behandlingen:
icedtea-netx:amd64
icedtea-7-plugin:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: icedtea-netx:amd64 1.5.1-1ubuntu1
ProcVersionSignature: Ubuntu
Public bug reported:
The window title sizes in gnome-shell is just two large. This could be
fixed by setting title_vertical_pad to '1'.
/usr/share/themes/Adwaita/metacity-1/metacity-theme-3.xml
...
distance name=title_vertical_pad value=15/
ProblemType: Bug
DistroRelease: Ubuntu 14.10
This bug was fixed in the package aide - 0.16~a2.git20130520-3
---
aide (0.16~a2.git20130520-3) unstable; urgency=medium
* cron.daily/aide:
- fixed 'unbound variable' error with bash-4.3 (LP: #1323827)
* 31_aide_postfix: new
- handle files/dirs in /var/spool/postfix
** Changed in: coreutils (Debian)
Status: Won't Fix = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192239
Title:
rm shouldn't require /proc to be mounted
To manage
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
The environment variable `TMPDIR' controls the placement of temporary files
as documented in section Tuning Memory Usage of the Enblend and Enfuse
manuals.
The actual, assigned directory for the ImageCache can easily be inquired by
calling Enblend or Enfuse with the option pair `--verbose
Looks like the issue is in the implementation of the netfilter hook
kernel module, as its not recommended to use GFP_KERNEL, and cannot
sleep in netfilter hooks, since the hookos are run in interrupt context
(when the packet is received) by the net_rx_action softirq. Instead
this issue is
Public bug reported:
Upgrading from Kubuntu 14.04 to 14.10. I ran sudo do-release-upgrade -m
desktop -f DistUpgradeViewKDE and then got an error saying could not
calculate the upgrade
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received
(In reply to todventtu from comment #3)
Bug persists on Win 7 64-bit 4.3.2.2.
But on dev build there is no fill to begin with. Version: 4.4.0.0.alpha1+
Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33
The bug of it opening in
No response from bug filer for over 2 years.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981304
Title:
[i965gm mesa] GPU lockup render.IPEHR: 0x11229000
To manage notifications about this bug
No response from bug filer for 2 years.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980964
Title:
[i965gm mesa] GPU lockup render.IPEHR: 0xa80003bd
To manage notifications about this bug go to:
Bug persists on Win 7 64-bit 4.3.2.2.
But on dev build there is no fill to begin with. Version: 4.4.0.0.alpha1+
Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33
--
You received this bug notification because you are a member of
Confirmed in 3.3.0, 3.6.7, 4.3.
Version: 4.3.4.0.0+
Build ID: bea74d73f4782b17f5286327f15db60ab3ae85de
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:libreoffice-4-3, Time:
2014-10-15_05:34:17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
alt-tabbing is working here, using the awful default alt-tab plugin.
Which one are you using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981304
Title:
[i965gm mesa] GPU lockup render.IPEHR:
This happens on two of my laptops both running 14.04LTS. One laptop is a
Dell studio 1737 with 4bg ram in bios mode and the other is a Samsung
540U4E with 16gb ram and in UEFI mode. Both get the same error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package xfconf - 4.10.0-3
Sponsored for Jackson Doak (noskcaj)
---
xfconf (4.10.0-3) unstable; urgency=low
[ Evgeni Golov ]
* Correct Vcs-* URLs to point to anonscm.debian.org
[ Jackson Doak ]
* debian/control: bump standards-version to 3.9.5
*
** Changed in: xserver-xorg-video-intel
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981304
Title:
[i965gm mesa] GPU lockup render.IPEHR: 0x11229000
To
** Changed in: xserver-xorg-video-intel
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980964
Title:
[i965gm mesa] GPU lockup render.IPEHR: 0xa80003bd
To
This happens on two of my laptops both running 14.04LTS. One laptop is a
Dell studio 1737 with 4bg ram in bios mode and the other is a Samsung
540U4E with 16gb ram and in UEFI mode. Both get the same error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package libvirt-glib - 0.1.9-4
Sponsored for Jackson Doak (noskcaj)
---
libvirt-glib (0.1.9-4) unstable; urgency=medium
* [7e61158] Fix test by not running main loop twice (Closes: #765566)
-- Guido Günther a...@sigxcpu.org Fri, 17 Oct 2014 17:32:20
thanks to Julio, apt-get remove and apt-get install works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365657
Title:
package syslinux-themes-debian 12-3 failed to install/upgrade:
subprocess
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mumble (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361834
Title:
This bug was fixed in the package i7z - 0.27.2+git2013.10.12-g5023138-2
Sponsored for Jackson Doak (noskcaj)
---
i7z (0.27.2+git2013.10.12-g5023138-2) unstable; urgency=medium
* Bump Standards-Version to 3.9.6 (no changes needed).
* qmake-hardening.patch: Enable hardening flags
Public bug reported:
installation of graphicsdriver fails after updating to 14.10
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
NonfreeKernelModules: wl
plz help.
i try to instal drivers on 14.10
cp: cannot stat ‘rt2x00/*.ko’: No such file or directory
insserv: warning: script 'K01load.sh' missing LSB tags and overrides
insserv: warning: script 'load.sh' missing LSB tags and overrides
insmod: ERROR: could not load module
Public bug reported:
monitor randomly goes black for 5 seconds or so, then returns. audio
keeps playing however and nothing closes. this is only since upgrade
from 14.04 to 14.10
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu
Public bug reported:
During Upgrade process from 14.04 to 14.10
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: syslinux-themes-debian 12-3
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic i686
NonfreeKernelModules: wl
ApportVersion:
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package logcheck - 1.3.17
---
logcheck (1.3.17) unstable; urgency=low
[ Hannes von Haugwitz ]
* debian/control:
- dropped obsolete Replaces fields
- removed 'deprecated' notice from logtail's short description
- bumped to Standards-Version
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package ltspfs - 1.4-1
---
ltspfs (1.4-1) unstable; urgency=medium
* New upstream version:
- Fix filesystem size calculations. Thanks to datube for the initial
patch! (LP: #1021579).
- Mount ltspfs filesystem directly to
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
This bug was fixed in the package lilo - 1:24.1-1
---
lilo (1:24.1-1) unstable; urgency=medium
* New upstream release:
- Fix liloconfig: not included initrd.img in lilo.conf, kernel
installation/upgrading failed. Closes: #640792, #663586
LP: #703371, #774733,
Public bug reported:
Ubuntu version: Ubuntu GNOME 14.10 stable amd64
GDM version: 3.10.0.1-0ubuntu7
CPU Vendor: AMD
GPU vendor: AMD
Computer type: Laptop
After fresh installing Ubuntu GNOME 14.10, everything was fine and I
installed fglrx. However after I reboot my machine it just stuck between
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you both for your suggestions.
I am using enblend with the hugin frontend on Fedora.
enblend-4.1.1-3.fc19.i686
$ enblend -V
enblend 4.1.1
I noticed the 4.2 version in the mercurial repo appears to have more
verbose output and more documentation which would have helped a lot in
my case.
** Changed in: tla (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1186541
Title:
Documentation is non free
To manage notifications about this bug go to:
Public bug reported:
simple-scan and xsane both segfault every time I press scan in them.
The details I see from apport get reported automatically but I can't
tell how to see them locally. However, by visual inspection they look a
lot like
I do have a file
https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/204621 so maybe
that would be helpful?
In the meantime I ran it in gdb and get
(gdb) run
Starting program: /usr/bin/simple-scan
[Thread debugging using libthread_db enabled]
Using host libthread_db library
1 - 100 of 553 matches
Mail list logo
