[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Nice idea! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
I can confirm all said before. In my case my laptop is an ASUS VivoBook S14 S430FA. I bought it 2 days ago 'cause it was a cheep nice laptop with just what I needed, and did came with a preinstalled linux (Endless), so I could guess that it had to work properly in another Linux like Xubuntu (I'm on Xubuntu 18.04.2 both in my desktop and now in my new laptop). Could not expect this problems, but finaly it's working fine, and everything works like a charm from hardware side, as intended. I had a very hard time to get it running, and reinstalled thousand times the whole system (with encrypted HD or not), till I could guess the problem started when updating some packages, among them the intel- microcode. But I was not sure which one exactly was (or had the time for more trials), though I suspect this one could be THE one. Fortunately, I just found that the lowlatency kernels did work! So, probably the lowlatency are not injecting the intel-microcode code, which could perhaps be thought as a new bug, but for me was a real blessing. I do work with audio usually, but never had the real need of a RT kernel, so I'm pleased to have find this and being able to go back to standard kernel. For my laptop there is no new BIOS by ASUS by now (still on 300), so I have to use workarounds I or II, both work fine. For more comfort, I use the second one, the pinned package, so that it will be easy so see when a new one comes, and try if it solves or not the problem. And I tend to think that an outdated intel-microcode (for the infamous spectre and meltdown intel failure) is better than no microcode applied. Or is not the way it works? Should I choose the I option or it's the same? Anyway, thanks a lot, and, if you come in trouble again with that, remember that the lowlatency kernel does not suffer this problems, you don't need an "exotic" kernel, just one at hand... (I'm keeping the 4.18 lowlatency kernel just in case, while using the 5.00 generic, so that it defaults to generic, but have my second option just in case something fails again, or just I feel the need at any point for a RT kernel) BTW: I was unable to boot ever from a 19.04 ubuntu version (nor Xubuntu, nor Ubuntu, nor Lubuntu). That was another trial I was at after being pissed by the bizarre problem for a number of times. But never got a simple booting from pendrive with any xUbuntu 19.04. And it seems logical now, probably the intel-microcode is yet included in the images. Probably I could have used the I workaround, but I didn't find this page till now. Anyway, I prefer to keep at LTS just not to be updating each 6 months... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406221] [NEW] package linux-image-3.16.0-28-generic 3.16.0-28.38 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 17
Public bug reported: properly upgraded from trusty. Everuthing seems to work properly, but each time system starts, plenty windows about this system fail appear. After closing them, no more problems. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nachordez 3862 F pulseaudio nachordez 3989 F panel-5-mixer /dev/snd/seq:timidity 2168 F timidity Date: Thu Dec 25 16:34:35 2014 DuplicateSignature: package:linux-image-3.16.0-28-generic:3.16.0-28.38:el subproceso instalado el script post-installation devolvió el código de salida de error 17 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 17 HibernationDevice: RESUME=UUID=2334f559-9149-4f85-9353-1fd82b0a2e48 MachineType: Packard Bell BV EasyNote_MX36 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic root=UUID=b42df561-ac6c-4f81-a05a-ffb83cb6f05f ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-15 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.16.0-28-generic 3.16.0-28.38 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 17 UpgradeStatus: Upgraded to utopic on 2014-12-25 (3 days ago) WpaSupplicantLog: dmi.bios.date: 07/28/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: EasyNote_MX36 dmi.board.vendor: PACKARD BELL BV dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: PACKARD BELL BV dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr306:bd07/28/2007:svnPackardBellBV:pnEasyNote_MX36:pvrPB90E07204:rvnPACKARDBELLBV:rnEasyNote_MX36:rvr1.0:cvnPACKARDBELLBV:ct10:cvr1.0: dmi.product.name: EasyNote_MX36 dmi.product.version: PB90E07204 dmi.sys.vendor: Packard Bell BV ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package i386 utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406221 Title: package linux-image-3.16.0-28-generic 3.16.0-28.38 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1406221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754000] Re: Running Unity disables Xorg's 3-finger click support (middle click)
All that's a bit confusing for me. I have a synaptics touchpad, and I was using really MUCH the three-fingers tap for opening links in a new tab, closing tab, pasting selections, etc. I think that was such a natural way of doing, that to say: change that for two fingers, is not a solution I can accept. There is a BIG advantage on having the mid-click assigned for three fingers: I use two for scrolling, and having two as a mid-clicks can trigger this action by mistake if I touch accidentally shot the touchpad, and then is much nicer to have the two-fingers-click assigned to right button, so, it just triggers the menu, ans just touching outside it get its out. Really fast and comfortable. The problem (don't know if that's what Unity is doing to avoid the three-finger-click) is that synclient -m 100 reports just one finger in touchpad when there are three. And for me is the same in unity or XFCE4. I cannot use he mid-click with three fingers, and, really, it's a hell.. That should never be changed in that way, with no option to re-adjust. It's not a new action. It's a BUG. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754000 Title: Running Unity disables Xorg's 3-finger click support (middle click) To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/754000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 840509] Re: touchpad triple-tap to middle-click stopped working in 11.10
That's not a duplicate of #754000 though related. They talk about triple-click on a clickpad, not triple-tap on a touchpad. But it seems that the triple-click question is turning down the triple- tap. Please, that's a very important question. I (and many other people) do REALY NEED the third-button-triple-tap emulation. That cannot be changed so uncounsciously! The synclient -m 100 informs just one finger when there are 3 or 4 (it's right when 1 or 2). That nees to be corrected IMMEDIATELY. ** This bug is no longer a duplicate of bug 754000 Running Unity disables Xorg's 3-finger click support (middle click) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/840509 Title: touchpad triple-tap to middle-click stopped working in 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/840509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873482] Re: elantech: Touchpad always reports 3 finger tap as 1 finger tap
It's the same for me, since upgrade to Oneiric, I've losted the triple- finger-mid-click emulation. synclient reports just 1 finger when three (or four) are used. I own also an Eeepc 1015, and worked fine befor upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873482 Title: elantech: Touchpad always reports 3 finger tap as 1 finger tap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/873482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 356252] Re: no screen does not come back on restoring after suspend, ati
The problem is still there... I can't use suspension, 'cause the screen stands black after trying to reiniciate. And the worse thing is that even if I try to reboot my laptop pressing the start button (the only one, as usual on laptops), I just get the computer off, and when it starts again, is still in the same still black waitng state... no way. I had to unplug the electricity and battery to have a real reboot... Thanks 2009/10/19 Nacho Rodriguez nachor...@gmail.com I'm upgrading just now to 9.10 Beta (hope is stable enough!), and then will try it and send you the results Thanks 2009/10/17 Jim Lieb j...@canonical.com Can you confirm this issue exists with the most recent Karmic Koala 9.10 Beta release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Thanks in advance. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- no screen does not come back on restoring after suspend, ati https://bugs.launchpad.net/bugs/356252 You received this bug notification because you are a direct subscriber of the bug. Status in “linux” package in Ubuntu: Incomplete Bug description: On restoring after suspend, HD sounds like working, but there's no screen image nor light. Hard reset needed ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 CurrentDmesg: [ 89.057558] eth0: link down [ 89.057856] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 99.332065] ath0: no IPv6 routers present [ 155.615351] padlock: VIA PadLock not detected. DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python2.6 MachineType: Packard Bell BV EasyNote_MX36 NonfreeKernelModules: ath_hal Package: linux-image-2.6.28-11-generic 2.6.28-11.40 ProcAttrCurrent: unconfined ProcCmdLine: root=UUID=b42df561-ac6c-4f81-a05a-ffb83cb6f05f ro quiet ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.28-11.40-generic SourcePackage: linux Tags: resume suspend Title: [Packard Bell BV EasyNote_MX36] suspend/resume failure [non-free: ath_hal] UserGroups: -- no screen does not come back on restoring after suspend, ati https://bugs.launchpad.net/bugs/356252 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 456221] [NEW] Arbitrary clics on touchpad
Public bug reported: Since I have upgraded to Karmic Koala (Beta), the touchpad of my laptop is not working properly. When I try to move the pointer, and so touch the touchpad, it registers clicks I'm not doing (even if moving slowly and pressing for a good contact), so that it presses buttons it goes upon, or grab icons, etc. It did worked the fist boot to KK, but then, in sucesives, it fails Mine is a Packard Bell easynote-mx36-u-087 Karmic Koala Beta (October 19th 2009) 32 bits ** Affects: ubuntu Importance: Undecided Status: New ** Tags: touchpad -- Arbitrary clics on touchpad https://bugs.launchpad.net/bugs/456221 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 456221] Re: Arbitrary clics on touchpad
I have discovered it JUST happens when atached to a LAN fisical connection, not when using Wifi... -- Arbitrary clics on touchpad https://bugs.launchpad.net/bugs/456221 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
Re: [Bug 356252] Re: no screen does not come back on restoring after suspend, ati
I'm upgrading just now to 9.10 Beta (hope is stable enough!), and then will try it and send you the results Thanks 2009/10/17 Jim Lieb j...@canonical.com Can you confirm this issue exists with the most recent Karmic Koala 9.10 Beta release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Thanks in advance. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- no screen does not come back on restoring after suspend, ati https://bugs.launchpad.net/bugs/356252 You received this bug notification because you are a direct subscriber of the bug. Status in “linux” package in Ubuntu: Incomplete Bug description: On restoring after suspend, HD sounds like working, but there's no screen image nor light. Hard reset needed ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 CurrentDmesg: [ 89.057558] eth0: link down [ 89.057856] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 99.332065] ath0: no IPv6 routers present [ 155.615351] padlock: VIA PadLock not detected. DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python2.6 MachineType: Packard Bell BV EasyNote_MX36 NonfreeKernelModules: ath_hal Package: linux-image-2.6.28-11-generic 2.6.28-11.40 ProcAttrCurrent: unconfined ProcCmdLine: root=UUID=b42df561-ac6c-4f81-a05a-ffb83cb6f05f ro quiet ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.28-11.40-generic SourcePackage: linux Tags: resume suspend Title: [Packard Bell BV EasyNote_MX36] suspend/resume failure [non-free: ath_hal] UserGroups: -- no screen does not come back on restoring after suspend, ati https://bugs.launchpad.net/bugs/356252 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 356252] [NEW] no screen does not come back on restoring after suspend, ati
Public bug reported: On restoring after suspend, HD sounds like working, but there's no screen image nor light. Hard reset needed ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 CurrentDmesg: [ 89.057558] eth0: link down [ 89.057856] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 99.332065] ath0: no IPv6 routers present [ 155.615351] padlock: VIA PadLock not detected. DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python2.6 MachineType: Packard Bell BV EasyNote_MX36 NonfreeKernelModules: ath_hal Package: linux-image-2.6.28-11-generic 2.6.28-11.40 ProcAttrCurrent: unconfined ProcCmdLine: root=UUID=b42df561-ac6c-4f81-a05a-ffb83cb6f05f ro quiet ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.28-11.40-generic SourcePackage: linux Tags: resume suspend Title: [Packard Bell BV EasyNote_MX36] suspend/resume failure [non-free: ath_hal] UserGroups: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume suspend -- no screen does not come back on restoring after suspend, ati https://bugs.launchpad.net/bugs/356252 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 356252] Re: no screen does not come back on restoring after suspend, ati
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/24865917/BootDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24865918/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/24865919/HalComputerInfo.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/24865920/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/24865921/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/24865922/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/24865923/ProcInterrupts.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/24865924/ProcMaps.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/24865925/ProcModules.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/24865927/ProcStatus.txt ** Attachment added: SleepLog.txt http://launchpadlibrarian.net/24865929/SleepLog.txt -- no screen does not come back on restoring after suspend, ati https://bugs.launchpad.net/bugs/356252 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
