[Bug 203385] Re: Recovery menu cannot be controlled with keyboard
In case it's useful: at the end of the video, after the text stops scrolling, i press: r a few times enter a few times ctrl-alt-del /etc/default/grub included (as you can see from the commented lines I have been trying to figure out if thats why it isnt working, because it seems to have broken some time after doing a bunch of resolution tests) http://oh-hi.info/video/2020-06-04-- 19-44-58_concatFilter_H264-veryslow.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/203385 Title: Recovery menu cannot be controlled with keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/203385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203385] Re: Recovery menu cannot be controlled with keyboard
Still seeing this in Kubuntu 18.04 installs. Menu does not display, blind selections seem to do nothing or simply restart. As stated above: this is a system killer if discovered when we actually have a serious problem. Fortunately in my case I was able to work around it, but it was still terrifying to discover half way through 2020 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/203385 Title: Recovery menu cannot be controlled with keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/203385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203385] Re: Recovery menu cannot be controlled with keyboard
PS: it seems to be entirely ignoring GRUB_GFXMODE / GRUB_GFXPAYLOAD_LINUX at some point after selecting a 'recovery options' grub-entry. It looks to be reverting to 640x480...maybe relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/203385 Title: Recovery menu cannot be controlled with keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/203385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859400] [NEW] bind Home key to F1 and then back to Home=Home - fails
Public bug reported: works as expected: (keycode 110 = Home) xmodmap -e "keycode 110 = a a a" press Home in kate or on konsole: (returns 'a') xmodmap -e "keycode 110 = Home Home Home" press Home in kate or on konsole: (cursor positions to full-left of line) ie: the above works perfectly but after binding: xmodmap -e "keycode 110 = F1 F1 F1" and then reverting xmodmap -e "keycode 110 = Home Home Home" Home key no longer functions as expected. (it does something, as the cursor changes for no apparent reason, but I can't figure out what it's doing) NOTE: I have a global KDE hotkey set to F1, that runs a context sensitive bash script (the active window determines what happens, mostly it uses xdotool to determine window title, uses that to determne if video is being played or recorded, and then writes a timestamp into a text file based on the results) Description:Ubuntu 18.04.3 LTS Release:18.04 xdotool: Installed: 1:3.20160805.1-3 Candidate: 1:3.20160805.1-3 Version table: *** 1:3.20160805.1-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: xmodmap (Ubuntu) Importance: Undecided Status: New ** Description changed: works as expected: (keycode 110 = Home) xmodmap -e "keycode 110 = a a a" - press F1 in kate or on konsole: - (returns 'a') + press Home in kate or on konsole: + (returns 'a') xmodmap -e "keycode 110 = Home Home Home" - press F1 in kate or on konsole: - (cursor positions to full-left of line) - - ie: the above works perfectly + press Home in kate or on konsole: + (cursor positions to full-left of line) - but after binding: + ie: the above works perfectly + + but after binding: xmodmap -e "keycode 110 = F1 F1 F1" - and then reverting + and then reverting xmodmap -e "keycode 110 = Home Home Home" - Home key no longer functions as expected. (it does something, as the cursor changes for no apparent reason, but I can't figure out what it's doing) + Home key no longer functions as expected. (it does something, as the cursor changes for no apparent reason, but I can't figure out what it's doing) NOTE: I have a global KDE hotkey set to F1, that runs a context sensitive bash script (the active window determines what happens, mostly it uses xdotool to determine window title and then writes a timestamp into a text file) - Description:Ubuntu 18.04.3 LTS Release:18.04 xdotool: - Installed: 1:3.20160805.1-3 - Candidate: 1:3.20160805.1-3 - Version table: - *** 1:3.20160805.1-3 500 - 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:3.20160805.1-3 + Candidate: 1:3.20160805.1-3 + Version table: + *** 1:3.20160805.1-3 500 + 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages + 100 /var/lib/dpkg/status ** Description changed: works as expected: (keycode 110 = Home) xmodmap -e "keycode 110 = a a a" press Home in kate or on konsole: (returns 'a') xmodmap -e "keycode 110 = Home Home Home" press Home in kate or on konsole: (cursor positions to full-left of line) ie: the above works perfectly but after binding: xmodmap -e "keycode 110 = F1 F1 F1" and then reverting xmodmap -e "keycode 110 = Home Home Home" Home key no longer functions as expected. (it does something, as the cursor changes for no apparent reason, but I can't figure out what it's doing) NOTE: - I have a global KDE hotkey set to F1, that runs a context sensitive bash script (the active window determines what happens, mostly it uses xdotool to determine window title and then writes a timestamp into a text file) + I have a global KDE hotkey set to F1, that runs a context sensitive bash script (the active window determines what happens, mostly it uses xdotool to determine window title, uses that to determne if video is being played or recorded, and then writes a timestamp into a text file based on the results) Description:Ubuntu 18.04.3 LTS Release:18.04 xdotool: Installed: 1:3.20160805.1-3 Candidate: 1:3.20160805.1-3 Version table: *** 1:3.20160805.1-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859400 Title: bind Home key to F1 and then back to Home=Home - fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmodmap/+bug/1859400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!
Yep, mine reverts to 1024x760 76Hz and has no options whatsoever. It's a bit of a showstopper. dmesg: nvidia: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be '3.13.0-143-generic SMP mod_unload modversions retpoline ' works: Linux betlogbrick 3.13.0-142-generic #191-Ubuntu SMP Fri Feb 2 12:13:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux fails: *3.13.0-143* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler! To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1750937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423093] Re: baloo search does not find directory names
My bad. Done: https://bugs.kde.org/show_bug.cgi?id=344316 ** Bug watch added: KDE Bug Tracking System #344316 https://bugs.kde.org/show_bug.cgi?id=344316 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423093 Title: baloo search does not find directory names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baloo/+bug/1423093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423093] [NEW] baloo search does not find directory names
Public bug reported: Using ctrl-f in dolphin to search mounted drives cannot find directory names. eg: This folder exists: /home/user/pictures/camera2/2013/2013-12-25--17.58.35_200mmf2.8_maroochydore/ But 'filename' or 'content' search for "maroochydore" yeilds nothing. <- PROBLEM ** Affects: baloo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423093 Title: baloo search does not find directory names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baloo/+bug/1423093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 549679] Re: Shutter has disabled features: Web capture, Edit and Send
On Kubuntu 12.04 : do I really need to install 47Mb of gnome stuff simply to make web capture work? Is there a more efficient KDE workaround? Or an actual first install/update fix? Shutter 0.88.1 rev: 1184 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/549679 Title: Shutter has disabled features: Web capture, Edit and Send To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/549679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328089] Re: splashy 0.3.13-3ubuntu1 fresh install conflicts with lsb-base
also; another question: splashy is the problem here... but usplash is fine? I ask because my bootsplash is messed up now, and i just found this rather useful looking usplash howto document to fiddle with http://linuxforclinics.sourceforge.net/docs/usplash.pdf -- splashy 0.3.13-3ubuntu1 fresh install conflicts with lsb-base https://bugs.launchpad.net/bugs/328089 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 328089] Re: splashy 0.3.13-3ubuntu1 fresh install conflicts with lsb-base
let me clarify my previous question: How do I remove splashy and fix this problem? ...by "--force-overwrite"ing it and then removing it? -- splashy 0.3.13-3ubuntu1 fresh install conflicts with lsb-base https://bugs.launchpad.net/bugs/328089 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 328089] Re: splashy 0.3.13-3ubuntu1 fresh install conflicts with lsb-base
This issue has completely locked up my ability to use kpackagekit on my system. Is there some temporary workaround available? is this useful to those of who don't really know what we are doing? sudo dpkg --force-overwrite --install /var/cache/apt/archives/splashy_0.3.13-5ubuntu1_i386.deb (or on amd64) splashy_0.3.13-5ubuntu1_amd64.deb -- splashy 0.3.13-3ubuntu1 fresh install conflicts with lsb-base https://bugs.launchpad.net/bugs/328089 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
