Public bug reported:
Received this error when doing do-release-upgrade from ubuntu 18.04.4 to
20.4
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
ApportVersion:
*** This bug is a duplicate of bug 1519463 ***
https://bugs.launchpad.net/bugs/1519463
** This bug has been marked a duplicate of bug 1519463
Cannot upgrade from Ubuntu 14.04 to 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm going to assume the Russian text is the usual upgrade-failed report,
which is:
"An unresolvable problem occurred while calculating the upgrade.
This can be caused by:
* Upgrading to a pre-release version of Ubuntu
* Running the current pre-release version of Ubuntu
* Unofficial software
*** This bug is a duplicate of bug 1519463 ***
https://bugs.launchpad.net/bugs/1519463
** This bug has been marked a duplicate of bug 1519463
Cannot upgrade from Ubuntu 14.04 to 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1519463 ***
https://bugs.launchpad.net/bugs/1519463
** This bug has been marked a duplicate of bug 1519463
Cannot upgrade from Ubuntu 14.04 to 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is a known issue, mentioned in the Xenial release notes: "14.04 LTS
to LTS upgrades will be enabled with the 16.04.1 LTS point release, in
approximately 3 months time." I imagine there is a main bug somewhere
but I can't find it.
--
You received this bug notification because you are a
Public bug reported:
Installer crashed while installing. Perhaps while installing packages.
Have been attempting the recover from a RAM crash. Replaced ram, system
test comes out OK. However, Ubuntu still won't boot. Tried to reformat
my OS partition and install Unbuntu. This resulted in a crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904571
Title:
installer crashed late in the install, while installing packages. Have
been trying to recover from memory (RAM) crash, replaced RAM but
Public bug reported:
I attempted to hibernate today and I got an error regarding the bluetooth
failing to shut down(?)
I will try to get the error message a little later...
ProblemType: KernelOops
Annotation: This occured during a previous hibernate and prevented it from
resuming properly.
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/32366724/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/32366726/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/32366732/ArecordDevices.txt
Public bug reported:
This is kinda a paper-cut bug.
When I want to change how Gnome handles CD media when inserted, I have
to open a nautilus window, go into it's preferences and edit it from
there.
Couldn't we have a shortcut in the Prefs menu?
Thanks,
T
** Affects: nautilus (Ubuntu)
Out of interest - does anyone have a method of rebuilding the grub2 menu
to make the Windows option show up?
Thanks :)
--
karmic alpha: wrong syntax in 30_otheros
https://bugs.launchpad.net/bugs/396587
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: grub2
I don't know if anyone else if having the same problem but I installed
Karmic on the 11 July (from a Daily Alternative Kubuntu disc) and found
that windows had disappeared from my boot menu, but was present in the
configuration file. Anyway I
Public bug reported:
KDE failed to restore to it's previous state when I hibernated... Don't
know what else I can supply to help here :(
ProblemType: KernelOops
Annotation: This occured during a previous hibernate and prevented it from
resuming properly.
Architecture: i386
DistroRelease: Ubuntu
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/24196326/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/24196327/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24196328/Dependencies.txt
**
I understand that Canonical want to make the best for our screens dpi -
but this doesn't work on an Acer Aspire One (135x135dpi resolution,
correctly identified) The best fix for me is to add
Option NoDDC
to the monitor section of my Xorg.conf.
If my Xorg.conf is empty I run 'sudo
I should add the above command will force a 96dpi default, so you should
adjust where necessary (though I don't know how to change my dpi within
Xorg.conf, or even if you can!)
--
[jaunty] Font becomes far too big
https://bugs.launchpad.net/bugs/327386
You received this bug notification because
Jose,
Blacklisting acer_wmi worked brilliantly, thanks :)
Can confirm as today my wireless (WPA2) connects.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
Just today (8.30 GMT) I reinstalled Kubuntu Jaunty Alpha 4, and dist-upgraded
to the current state.
The network manager plasmoid still shows a greyed out wlan0 with an enable
switch, which will not turn on.
Am I missing something? - some people seem to have more luck than me.
I have tried sudo
I have placed a patch on the alsa-devel mailing list which works for me
(which links across the latest version) and put a howto in the ubuntu
forums, so hopefully this can be made fixed now! :)
(I will place the patch here when I get back to my development machine
tonight)
** Also affects:
Public bug reported:
Binary package hint: nvidia-cg-toolkit
Hi all,
I tried an apt-get install on the nvidia-cg-toolkit and got this response in
the console.
(below was my second attempt of installing)
[removed unimportant apt messages]
...
Using
Hi Larry,
I've only tried the output for now, as the card now seems to lock up
after a while. I think it may be hardware issues for me :(
T
--
ICE1712 - M-Audio Delta 66 not detected by alsa
https://bugs.launchpad.net/bugs/280847
You received this bug notification because you are a member of
** Changed in: ubuntu
Status: New = Invalid
--
ICE1712 - M-Audio Delta 66 not detected by alsa
https://bugs.launchpad.net/bugs/280847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks Larry, I will try this tonight!
--
ICE1712 - M-Audio Delta 66 not detected by alsa
https://bugs.launchpad.net/bugs/280847
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
OK, on a live CD of Intrepid (daily) I have:
edited /etc/modprobe.d/alsa-utils and added the following:
options snd-ice1712 model=delta1010lt
then saved.
typed 'sudo alsa force-reload' at the prompt - which picks up the card.
'sudo apt-get install alsa-tools-gui' (for envy24control - would
** Tags added: regression
--
ICE1712 - M-Audio Delta 66 not detected by alsa
https://bugs.launchpad.net/bugs/280847
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
Anybody? I can confirm that my Delta 66 shows up with the 64Studio Live
CD (which is quite old)... Has something broken?
** Tags added: alsa intrepid
--
ICE1712 - M-Audio Delta 66 not detected by alsa
https://bugs.launchpad.net/bugs/280847
You received this bug notification because you are a
DMesg Reports this:
[ 32.872626] ICE1712 :01:07.0: PCI INT A - Link[APC2] - GSI 17 (level,
low) - IRQ 17
[ 32.895124] ICE1712 :01:07.0: PCI INT A disabled
[ 32.895700] ICE1712: probe of :01:07.0 failed with error -14
--
ICE1712 - M-Audio Delta 66 not detected by alsa
Two more things:
1. I am running the AMD64 version of Intrepid.
2. I now know what it is - the following website helped:
http://blog.tryphon.org/alban/archives/2008/08/07/m-audio-delta-66-rev-e
-in-the-house/
These guys could only get the Rev. E Delta 66 working by commenting out
code for the
** Visibility changed to: Public
--
mythbuntu-startup crashed with DebconfError in command()
https://bugs.launchpad.net/bugs/209577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Hi,
Using Intrepid (Daily - Oct 9 2008) I've found that my Delta 66 does not
show up in the list of available sound cards. It does however, show up
if I run an lspci...
Logs below: Can anyone help?
Thanks,
Tom
** Affects: ubuntu
Importance: Undecided
Status:
** Attachment added: lspci.txt
http://launchpadlibrarian.net/18371261/lspci.txt
--
ICE1712 - M-Audio Delta 66 not detected by alsa
https://bugs.launchpad.net/bugs/280847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
(run as sudo for capabilities)
** Attachment added: lspciasroot.txt
http://launchpadlibrarian.net/18371294/lspciasroot.txt
--
ICE1712 - M-Audio Delta 66 not detected by alsa
https://bugs.launchpad.net/bugs/280847
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: asoundconflist.txt
http://launchpadlibrarian.net/18371267/asoundconflist.txt
--
ICE1712 - M-Audio Delta 66 not detected by alsa
https://bugs.launchpad.net/bugs/280847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I switched from Hardy Heron to Debian Lenny and it's running 2.6.25 and
has been up weeks in X windows (with my PCI wireless card and Nvidia
video and AMD Athlon64 dual core) chugging along nicely. No lockups.
2.6.25 definitely fixes it. Good luck all.
--
Linux kernel 2.6.24-12 lockup
Guys, check out bug 204996. The problem is the 2.6.24 kernel. I switched
from Hardy Heron to Debian Lenny and upgraded to 2.6.25 and have had no
lockups on my system. (Nvidia GeForce 7800 GTS, Atheros PCI wireless
card, Athlon64 dual core)
Maybe 2.6.25 will fix your problems?
--
System Hang
See bug 204996. Upgrading to 2.6.25 may fix your problem. Good luck!
--
nvidia with compiz and with dual core freeze
https://bugs.launchpad.net/bugs/151382
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thank goodness I finally found this bug! It has been frustrating trying to find
out what the heck is causing this.
I took out my wireless card (Atheros chipset - Netgear WG311T) and I'm just
using my wired ethernet for the time being to see if the bug is triggered.
--
Linux kernel 2.6.24-12
I discovered this freeze / kernel panic has further reaching
implications than I thought. Even using the 'nv' (open source Xorg
driver), my system still randomly locked up while using X!
As a test, I regressed my kernel back to Gutsy 7.10's (2.6.22) and
installed the latest Nvidia driver and
Whilst using 'nv' driver, I found the system still locked up randomly
(but not as often as when using the proprietary Nvdiai driver).
I remember when I was using Gutsy, I never had this issue. So, I decided
to try using the latest Gutsy kernel (2.6.22-14-generic). I installed
the Gutsy kernel
Same problem here.
Hardy Heron
2.6.24-19-generic
AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ (SMP mode)
GeForce 7800 GS
Both 169.12+2.6.24.13-19.42 (Ubuntu supplied driver) and 173.14.05 (from
NVidia's site) affected.
I also ran the nvidia-glx (not the -new) before.. version 96.something (I
I can verify this happens with both Nvidia proprietary drivers versions:
169.12+2.6,24,13-19.42 driver in Hardy Heron and 173.14.05 (from
Nvidia's site)
I am running:
AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
2.6.24-19-generic
NVidia GeForce 7800 GS
When I switch to open-source 'nv'
I can confirm this on a Feisty machine that uses wireless (madwifi
drivers)
My /etc/network/interfaces has 'auto ath0' and 'wpa-conf
/etc/wpa_supplicant.conf' lines in it.
I have to manually do ifdown ath0; ifup ath0 to get it to come up properly.
Sticking that in /etc/rc.local seems to do the
Public bug reported:
Binary package hint: linux-source-2.6.20
1. Plug stick in
2. Copy files to stick
3. Eject stick
4. Plug stick back in
5. Copy files from stick to HDD
6. Copy fails!
Please refer to this thread:
http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg51849.html
Looks like latest Edgy kernel fixes this problem.
I haven't had the soft lockup messages in weeks.
You can close this bug out.
Thanks very much!
--
BUG: soft lockup detected on CPU#1!
https://launchpad.net/bugs/84045
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: linux-source-2.6.17
Version info:
Edgy 6.10
linux-image-2.6.17-11-generic 2.6.17.1-11.35
Summary:
Please upgrade the ipw2200 driver from 1.1.2 to 1.2.0 (1.2.1 is out, but it is
not considered stable, but 1.2.0 is.)
dmesg:
ipw2200:
Would this be linux-image-2.6.17-50-generic?
I don't see a restricted-modules package for it.
--
BUG: soft lockup detected on CPU#1!
https://launchpad.net/bugs/84045
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Dmesg attached.
** Attachment added: dmesg output
http://librarian.launchpad.net/6351114/soft-lockup.txt
--
BUG: soft lockup detected on CPU#1!
https://launchpad.net/bugs/84045
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
This bug doesn't seem to occur much but it does it randomly. Often when
I am just doing day-to-day tasks on the machine (Firefox open, maybe 3
or 4 terminals), playing music, etc..
The machine will lock up anywhere between 10 seconds to a minute
(depending on how many of
Could this be related?
http://madwifi.org/ticket/397
I don't know what revision the madwifi drivers are on edgy. I'm
wondering if rolling my own from svn would fix this.
--
BUG: soft lockup detected on CPU#1!
https://launchpad.net/bugs/84045
--
ubuntu-bugs mailing list
I can confirm this works for me.
Ubuntu Edgy 6.10 (amd64)
Using madwifi drivers in linux-restricted-modules
My /etc/network/interfaces :
auto ath0
iface ath0 inet manual
wpa-roam /etc/wpa_supplicant.conf
iface default inet dhcp
(I followed the instructions from
I can verify the exact same behavior happens on my Acer TravelMate
4021WLMi. If I take out the AC power plug, the gnome-power-manager
instantly complains that power level is critical and threatens to power
off.
Sometimes it doesn't.. it will mark the battery as 50% as soon as I
disconnect the
52 matches
Mail list logo
