Public bug reported:
See attached
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15.4
ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
I can confirm that the askubuntu link on #25 worked; but shouldn't this
be in a better state now that it is no longer pre-release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550950
Title:
Public bug reported:
This occurred when trying to install the hwe-edge kernel. I believe I'll
just remove virtualbox for now. This is likely the fault of virtualbox
not supporting this kernel, but figured I'd make it known.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package:
Public bug reported:
updating from ubuntu 14 to ubuntu 16 (Server)
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: roundcube-core 1.2~beta+dfsg.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
Uname: Linux 3.13.0-52-generic x86_64
ApportVersion:
I'm getting this same issue every day
3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u4 x86_64 GNU/Linux
Guest is running under proxmox 3.4 virtio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423672
Public bug reported:
After maybe a minute copying files installation reported an error though
it didn't say any more than that.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.7
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
I'm having this problem with 12.04, which has been running and updating
quite happily for several months. I Eventually applied the workaround
described in http://www.linuxquestions.org/questions/linux-newbie-8/apt-
get-install-command-is-not-able-to-fetch-packages-from-ubuntu-
repositary-806674/,
Addendum to last comment:
For clarity, I should have said that the solution suggested in the link
was to set the DNS to 208.67.222.222, 208.67.220.220 directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I have been using Shotwell on Ubuntu 12.04 sucessfully for some time.
However from this morning it crashes each time I try to start it.
When I run it from the command line I get the following error:
I am getting FIXME: handle dialog start and FIXME: handle dialog end
as part of the (debug) console output when running a Qt GUI application
I am developing. They seem to appear in pairs and to be benign in that
they program behaves as expected and doesn't crash. It looks as though
they may
I'd certainly be willing to resolve this issue and provide patches to do
so if I knew that someone with developer access had the ability to
actually verify they are reasonable patches. I'd hate to provide a fix
for this to a bot.
--
You received this bug notification because you are a member of
I'd certainly be willing to resolve this issue and provide patches to do
so if I knew that someone with developer access had the ability to
actually verify they are reasonable patches. I'd hate to provide a fix
for this to a bot.
--
You received this bug notification because you are a member of
I agree I think its important to have for server and clustered
environments. I'd like to see this fixed and I've done some of the
fixing and gave patches. However, seems no one on the Ubuntu side
thinks its that important I guess.
Thanks,
- David Brown
On Sat, Mar 12, 2011 at 11:21 AM, Dominik
I agree I think its important to have for server and clustered
environments. I'd like to see this fixed and I've done some of the
fixing and gave patches. However, seems no one on the Ubuntu side
thinks its that important I guess.
Thanks,
- David Brown
On Sat, Mar 12, 2011 at 11:21 AM, Dominik
Any updates on this one?
--
kexec-tools 0_kdump
https://bugs.launchpad.net/bugs/609625
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
Sorry for taking a while to get back to this. So interestingly the
mainline kernel builds you posted don't have vmcoreinfo files to allow
the kdump initscript to run properly.
So, what do we do next?
--
kexec-tools 0_kdump
https://bugs.launchpad.net/bugs/609625
You received this bug
So I'm not sure how a scripting error in 0_kdump needs to be tested
with the mainline kernel vs the ubuntu provided kernel. But I can do
this if need be.
Thanks,
- David Brown
On Mon, Jul 26, 2010 at 10:18 AM, Jeremy Foshee
609...@bugs.launchpad.net wrote:
Hi David,
If you could also please
Public bug reported:
So in my effort to debug issues with suspend/resume on my dell laptop I
wanted to enable kernel kexec style crash dumps. I found some
information on the ubuntu wiki about using linux-crashdump package to
set this up.
However, my laptop has an encrypted root hard drive and
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52458612/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52458613/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52458614/BootDmesg.txt
**
Public bug reported:
This package cannot be installed because python-tegaki is not in any of
the repos.
** Affects: tegaki-pygtk (Ubuntu)
Importance: Undecided
Status: New
--
depends on python-tegaki, which is not available
https://bugs.launchpad.net/bugs/494815
You received this
Uhm the patch you posted here doesn't make a lot of sense. This would
have been on Karmic and its 2.6.31 based and the patch was applied to
2.6.29-rc1. Also, I verified that its contained in the source when I
pull do an apt-get source linux-image-2.6.31-14-generic. So I'm unsure
how I'm supposed
*** This bug is a duplicate of bug 216176 ***
https://bugs.launchpad.net/bugs/216176
Public bug reported:
Binary package hint: grub-pc
Okay I know I'm a crazy person for trying this stuff out but I was
curious.
I'm attempting to boot Xen 3.5 unstable with a vanilla 2.6.31.4 with the
xen-pv
*** This bug is a duplicate of bug 216176 ***
https://bugs.launchpad.net/bugs/216176
Oopse this maybe a duplicate of what's going on in bug 216176
** This bug has been marked a duplicate of bug 216176
Xen entries not working under grub2
--
grub-pc Xen dom0 support
didn't see a dmesg output log. so I'm posting one just in case.
** Attachment added: dmesg.log
http://launchpadlibrarian.net/33919873/dmesg.log
--
[113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x1004
https://bugs.launchpad.net/bugs/455067
You received this bug
Public bug reported:
hmmm it was interesting never thought my dosemu would kill the kernel
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33919820/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33919821/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33919822/BootDmesg.txt
**
And that post seemed rather useless. So here's all of messages file
** Attachment added: messages
http://launchpadlibrarian.net/33919971/messages
--
[113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x1004
https://bugs.launchpad.net/bugs/455067
You received this bug
Public bug reported:
r...@dmlb2010-lappy:/usr/src/kvm-84# lsb_release -rd
Description:Ubuntu jaunty (development branch)
Release:9.04
r...@dmlb2010-lappy:/usr/src/kvm-84#
r...@dmlb2010-lappy:/usr/src/kvm-84# apt-cache policy kvm-source
kvm-source:
Installed: 1:84+dfsg-0ubuntu3
** Attachment added: lspci -vvnn output
http://launchpadlibrarian.net/21060186/lspciout
--
xserver-org-video-vmware border rendering problems
https://bugs.launchpad.net/bugs/312080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/21060211/Xorg.0.log
--
xserver-org-video-vmware border rendering problems
https://bugs.launchpad.net/bugs/312080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This particular /etc/X11/xorg.conf has been modified from the default
vmware-tools installed version, by adding the higher resolution of my
display. However, the problem occurs on other images that have not been
modified.
** Attachment added: xorg.conf
Reattaching, after running as root.
** Attachment added: lspciout
http://launchpadlibrarian.net/21060264/lspciout
--
xserver-org-video-vmware border rendering problems
https://bugs.launchpad.net/bugs/312080
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: xserver-xorg-video-vmware
I believe this is the same as this Fedora bug
https://bugzilla.redhat.com/show_bug.cgi?id=464031
I'm running VMWare Fusion 2.0.1, but the other user reports this
happening on other VMWare systems.
Basically, any window manager
** Attachment added: Image capture of rendering error.
http://launchpadlibrarian.net/20789437/bad-border.png
--
xserver-org-video-vmware border rendering problems
https://bugs.launchpad.net/bugs/312080
You received this bug notification because you are a member of Ubuntu
Bugs, which is
]
Process `a' aborted (core dumped)
Thus, A+ never starts.
David Brown
** Affects: aplus-fsf (Ubuntu)
Importance: Undecided
Status: New
--
A+ crashes on start in x86-64
https://bugs.launchpad.net/bugs/196013
You received this bug notification because you are a member of Ubuntu
Bugs
This may only happen on specific sis hardware, specifically mine is an
older pentium4 that uses sdram the newer sis motherboards may not have
this issue.
On 4/29/07, Cheetahcat [EMAIL PROTECTED] wrote:
FYI, i did a clean install of Ubuntu 6.10 on my Gericom Frontman Force,
then updated 6.10,
You could keep the modified initrd just fine, the way I recommended you
modify the initrd should keep across upgrades and such.
I experienced this bug with 2.6.20-4-386 and 2.6.20-4-generic, which
means by 2.6.20-5-386 and 2.6.20-5-generic it should be fixed. However,
I'm not an ubuntu kernel
well the work around while the kernel is getting built is to go in and change
the initramfs package to only use the files listed.
I don't have an ubuntu box in front of me so bear with me...
edit /etc/initramfs-tools/initramfs.conf (??) and switch the first option to
list (iirc). Then edit the
Should the pata drivers not be put into the default initramfs then? I
had upgrade issues from 6.10 to 7.04 because the initramfs created tried
to load this driver and wouldn't ever get to the root hard-drive.
When will this be fixed? eta? I'd like to revert the changes I made to
the initramfs
39 matches
Mail list logo
