[Bug 1917278] [NEW] Unable to reinstall grub. Started with Windows 7. Installed Ubuntu 20.04 to dual boot. Upgraded to Windows 10. Got new monitor, did not recognize Ubuntu install. Reinstalled Ubunt
Public bug reported: >From what I can see, the original boot loader was not UEFI, it was legacy(not sure what that means). There are 3 primary partitions for windows and all Ubuntu was installed on an extended partition. I think the boot loader is the first primary partition that is 100 mb, but it is ntfs, not fat32 like efi partitions should be. Boot-repair doesn't work either. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 Date: Sun Feb 28 21:40:12 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917278 Title: Unable to reinstall grub. Started with Windows 7. Installed Ubuntu 20.04 to dual boot. Upgraded to Windows 10. Got new monitor, did not recognize Ubuntu install. Reinstalled Ubuntu. Nothing works. Post here. Cry in corner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1917278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585263] Re: MythTV playback issue - number of reference frames exceeds max
Looks like difficulties in VDPAU playback were indeed due to some junk left over from upgrades and local installs. A solid purge and re-install and VDPAU playback is working just fine (actually: much better than with 0.22-fixes under 9.10) However: CPU playback profiles which worked perfectly under 9.10 and 0.22-fixes still reproducibly and regularly stutter in 720p playback . The10.04 builds seem to be running less efficiently / not making as effective use of both CPU cores. A build difference in the binaries? Platform: 10.04 32-bit Hardware: Athlon 64 X2 6000+ -- MythTV playback issue - number of reference frames exceeds max https://bugs.launchpad.net/bugs/585263 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585263] Re: MythTV playback issue - number of reference frames exceeds max
Further investigations revealed that the same stream parsing error and hence frame-discards/ stutters also with non-VDPAU playback profiles. I'm beginning to wonder if the upgrade wasn't quite clean on my machine. The issue is so obvious visually I can't believe there aren't hordes of outraged german HD World-cup watchers complaining. I'll investigage further when I can boot back into 10.04 (its a 'production' system ;-) ). -- MythTV playback issue - number of reference frames exceeds max https://bugs.launchpad.net/bugs/585263 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585263] Re: MythTV playback issue - number of reference frames exceeds max
Just upgraded from karmic to lucid and hit exactly this problem. VERY noticeable on the heavily inter-cut World-cup coverage on ZDF and ARD here in Germany. Seems supiciously like a reincarnation of http://svn.mythtv.org/trac/ticket/7522 this was fixed 0.22-fixes. Could it be the ffmpeg upstream fix isn't present in the ubuntu 0.23 builds? ** Bug watch added: mythtv.org bug tracker #7522 http://svn.mythtv.org/trac/ticket/7522 -- MythTV playback issue - number of reference frames exceeds max https://bugs.launchpad.net/bugs/585263 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 446146] Re: Several Huawei USB dongle don't work with kernel 2.6.31-12.40 (2.6.31.1 update related)
Confirm: stock kernel 2.6.31-16.53 does not fix the issue for (my) Huawei E270. A custom kernel that includes the patch diff --git a/drivers/usb/storage/initializers.c b/drivers/usb/storage/initializers.c index 105d900..ec17c96 100644 --- a/drivers/usb/storage/initializers.c +++ b/drivers/usb/storage/initializers.c @@ -102,5 +102,5 @@ int usb_stor_huawei_e220_init(struct us_data *us) USB_TYPE_STANDARD | USB_RECIP_DEVICE, 0x01, 0x0, NULL, 0x0, 1000); US_DEBUGP(Huawei mode set result is %d\n, result); - return 0; + return (result ? 0 : -ENODEV); } which differentiated the 'apw10' test kernel from 'apw5 works correctly. Needless to say I'm holding on to that patch like grim death ;-) -- Several Huawei USB dongle don't work with kernel 2.6.31-12.40 (2.6.31.1 update related) https://bugs.launchpad.net/bugs/446146 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 363682] Re: cx24116 firmware doesn't load - firmware corrupt
Just updated my myth server (ubuntu 9.10) kernel. Boom... package still has old broken firmware in it which of course merrily over-wrote the working version copied into place after the last kernel update. (see comment #8 for the standard recipe). This urgently needs to be fixed in the ubuntu kernel packages. Are the Kernel packagers even aware of the issue? The firmware file you're distro-ing is not 'a bit flaky' or 'imperfect'. Its is 100% non-functional dead broken. If you have several cards the firmware reload loop approximates a denial-of-service attack. Please package a a working firmware! -- cx24116 firmware doesn't load - firmware corrupt https://bugs.launchpad.net/bugs/363682 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 446146] Re: Several Huawei USB dongle don't work with kernel 2.6.31-12.40 (2.6.31.1 update related)
Resultsfor my Vodafone Germany branded Huawei E270. 2.6.31-15.50 - no joy GSM modem converter disconnects leaving E270 in a confused state.Strangely unplugging and replugging works. 'apw5' - as for 15.50 'apw10' - Hurray this one works perfectly. -- Several Huawei USB dongle don't work with kernel 2.6.31-12.40 (2.6.31.1 update related) https://bugs.launchpad.net/bugs/446146 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 415076] Re: Can not connect to vpn using plasma-widget-networkmanagement
Also confirm. An openvpn connection (X.509 with password) sim fails without any error feedback when selected. /var/log/daemon.log reveals Nov 26 14:36:51 mouldy NetworkManager: info Starting VPN service 'org.freedesktop.NetworkManager.openvpn'... Nov 26 14:36:51 mouldy NetworkManager: info VPN service 'org.freedesktop.NetworkManager.openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 6903 Nov 26 14:36:51 mouldy NetworkManager: info VPN service 'org.freedesktop.NetworkManager.openvpn' just appeared, activating connections Nov 26 14:36:51 mouldy NetworkManager: info VPN plugin state changed: 1 Nov 26 14:36:51 mouldy NetworkManager: info VPN plugin state changed: 3 Nov 26 14:36:51 mouldy nm-openvpn[6906]: OpenVPN 2.1_rc19 x86_64-pc-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] built on Oct 13 2009 Nov 26 14:36:51 mouldy NetworkManager: info VPN connection 'New VPN Connection' (Connect) reply received. Nov 26 14:36:51 mouldy NetworkManager: WARN vpn_service_watch_cb(): VPN service 'org.freedesktop.NetworkManager.openvpn' died with signal 11 Nov 26 14:36:51 mouldy NetworkManager: WARN connection_state_changed(): Message did not receive a reply (timeout by message bus) Nov 26 14:36:51 mouldy NetworkManager: info (eth0): writing resolv.conf to /sbin/resolvconf Nov 26 14:36:51 mouldy NetworkManager: info Policy set 'Auto eth0' (eth0) as default for routing and DNS. Nov 26 14:36:51 mouldy NetworkManager: info VPN service 'org.freedesktop.NetworkManager.openvpn' disappeared, cancelling connections Note that under Gone using the gnome network manager applet the self- same openvpn connection configuration works just fine. This is a bit of PIA as I much prefer working under the slick KDE desktop ;- -- Can not connect to vpn using plasma-widget-networkmanagement https://bugs.launchpad.net/bugs/415076 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-networkmanagement in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 342166] [NEW] adjtimex broken on AMD64 / nForce chipset
Public bug reported: Binary package hint: adjtimex The version of adjtimex in hardy universe appears to have a Bug making it produce wildly inaccurate drift estimates on some mainboards. For example: r...@mouldy:/home/as# adjtimex -c=10 -d --- current --- -- suggested -- cmos time system-cmos error_ppm tick freqtick freq 1236933734 9.688040 1236933744 9.79671910867.9 1 5679872 1236933754 9.90541110869.2 1 56798729892 1142110 1236933764 10.01411110870.0 1 56798729892 1095235 1236933774 10.12280410869.3 1 56798729892 1137422 1236933783 10.23149810869.4 1 56798729892 1134297 where hwclock instead reckons a...@mouldy:~$ hwclock --show ;date Fri 13 Mar 2009 09:52:07 CET -0.721038 seconds Fri Mar 13 09:52:07 CET 2009 The effect is, of course, that the a huge (erroneous) correction for the systemc clock is recorded causing massive system clock drift massively after adjtimex installation. Later revisions of adjtimex appear to include new options to fix this issue. See (for example) http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/296ac353aede8ddb?fwc=1 ** Affects: adjtimex (Ubuntu) Importance: Undecided Status: New -- adjtimex broken on AMD64 / nForce chipset https://bugs.launchpad.net/bugs/342166 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253203] Re: isdn interface setup fails after gutsy to hardy upgrade
I managed to track down a small patch from the kernel mailing lists for isdn_net.c that fixed the issue for 2.6.24. I believe this propagated into the main kernel a while back. http://bugzilla.kernel.org/show_bug.cgi?id=9923 -- isdn interface setup fails after gutsy to hardy upgrade https://bugs.launchpad.net/bugs/253203 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253203] [NEW] isdn interface setup fails after gutsy to hardy upgrade
Public bug reported: Binary package hint: isdnutils When starting isdn after a hardy upgrade the ifconfig in /etc/isdn/device.ippp0 (generated using isdnconfig) setting the dummy IP addresses fails with SIOCSIFFLAGS: Invalid argument Driver module is 'hisax' with option 'type=35' to select driver support for the installed card. There are no obvious warnings or errors from the ISDN card kernel driver. Module load completes normally with [ 29.770290] HiSax: DSS1 Rev. 2.32.2.3 [ 29.770292] HiSax: 2 channels added [ 29.770295] HiSax: MAX_WAITING_CALLS added The issue appears kernel related - if the system is booted with 2.6.22-15 (left over from the gutsy install) isdn starts up and works normally. ** Affects: isdnutils (Ubuntu) Importance: Undecided Status: New -- isdn interface setup fails after gutsy to hardy upgrade https://bugs.launchpad.net/bugs/253203 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
