So this is a bit weird cyade this came out of nowhere, as I didn’t used to have any problem on this aspect
But in short, my system won’t recognize neither my android phone nor my kindle. Zero, nada, nothing shows. My devices act as if connected to a power supply but nothing else (USB debug is on in my android phone). This is particularly troublesome as I use my phone as an USB tethering devices since my USB wifi dongle died
The devices don’t show up neither on the disk application nor when usen the lsusb command
For testing purposes I connected an old Realtek USB dongle and it shows up (sadly there are no drivers for Linux..). My keyboard is also connected through USB and works fine.
It a the same cable I’ve been using so far, and testing with another cable the problem persists.
This was after I phone call, it could be possible that idle clicking led me to dismiss/active some kind of pop-up notification/configuration?
Sorry about formatting, doing this on my phone
PCManFM 1.2.5 in Lubuntu 18.04 here.
want to add a custom command to right click menu to batch rename all files in the selected dir, including all files in all subdirs, to subdir001, subdir002, …
For example, if a directory x has subdirs abc and def containing files a1.mp3, a2.mp3, a3.mp3 each, I want the files in abc to be renamed abc001.mp3, abc002.mp3, abc003.mp3, in the same order. Same for the def dir, except to def001.mp3, etc…
How do I do this? I was searching for solutions, but they all seem to be PCManFM version dependent.
firefox and chrome keep crashing on lubuntu 19.04 and ubuntu 18.04 ff ver 68.0.2 this is on a 4000 series ?? i7 with 8 gig ram 120 ssd, no video card i have another pc hooked on network that has had no issues in the last 6 days with chrome and ff i
ve changed Ethernet ports on router and back of i7 pc ive changed Ethernet cables that are 2 ft long i
ve disable hardware acceleration on both browsers i wasnt having an issue until about 3 weeks ago im fixing to try puppy linux on my usb drive for a couple of days
I tried to install the Nvidia driver 304.317 according this post: Can't install Nvidia drivers on Ubuntu 18.04
During installation, several errors occurred:
Error message 1:
ERROR: Failed to run '/usr/sbin/dkms build -m nvidia -v 304.137 -k 5.0.0-23-generic': Kernel preparation unnecessary for this kernel. Skipping ... Building module: cleaning build area... make -j2 KERNELRELEASE=5.0.0-23-generic module SYSSRC=/lib/modules/5.0.0-23-generic/build...................(bad exit status: 2) ERROR (dkms apport): binary package for nvidia: 304.137 not found Error! Bad return status for module build on kernel: 5.0.0-23-generic (i686) Consult /var/lib/dkms/nvidia/304.137/build/make.log for more information.
Error message 2:
ERROR: Failed to install the kernel module through DKMS. No kernel module was installed: please try to installing again without DKMS, or check the DKMS logs for more information.
Error message 3:
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Sat Aug 10 21:13:58 2019 installer version: 304.137 PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin nvidia-installer command line: ./nvidia-installer Unable to load: nvidia-installer ncurses v6 user interface Using: nvidia-installer ncurses user interface -> License accepted. -> Installing NVIDIA driver version 304.137. -> Running distribution scripts executing: '/usr/lib/nvidia/pre-install'... -> done. -> The distribution-provided pre-install script failed! Continue installation anyway? (Answer: Yes) -> Would you like to register the kernel module sources with DKMS? This will allow DKMS to automatically build a new module, if you install a different kernel later. (Answer: Yes) -> Installing both new and classic TLS OpenGL libraries. -> Searching for conflicting X files: -> done. -> Searching for conflicting OpenGL files: -> done. -> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86' (304.137): executing: '/sbin/ldconfig'... executing: '/sbin/depmod -aq'... depmod: WARNING: Ignored deprecated option -q -> done. -> Driver file installation is complete. -> Installing DKMS kernel module: ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 304.137 -k 5.0.0-23-generic`: Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j2 KERNELRELEASE=5.0.0-23-generic module SYSSRC=/lib/modules/5.0.0-23-generic/build...................(bad exit status: 2) ERROR (dkms apport): binary package for nvidia: 304.137 not found Error! Bad return status for module build on kernel: 5.0.0-23-generic (i686) Consult /var/lib/dkms/nvidia/304.137/build/make.log for more information. -> error. ERROR: Failed to install the kernel module through DKMS. No kernel module was installed; please try installing again without DKMS, or check the DKMS logs for more information. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
DKMS make.log for nvidia-304.137 for kernel 5.0.0-23-generic (i686) Sa 10. Aug 21:14:49 CEST 2019 NVIDIA: calling KBUILD... Makefile:223: ================= WARNING ================ Makefile:224: 'SUBDIRS' will be removed after Linux 5.3 Makefile:225: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:226: ========================================== test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) mkdir -p /var/lib/dkms/nvidia/304.137/build/.tmp_versions ; rm -f /var/lib/dkms/nvidia/304.137/build/.tmp_versions/* make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia/304.137/build (cat /dev/null; echo kernel//var/lib/dkms/nvidia/304.137/build/nvidia.ko;) > /var/lib/dkms/nvidia/304.137/build/modules.order [several compiler calls] cc -Wp,-MD,/var/lib/dkms/nvidia/304.137/build/.os-interface.o.d -nostdinc -isystem /usr/lib/gcc/i686-linux-gnu/7/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -Iubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror-implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m32 -msoft-float -mregparm=3 -freg-struct-return -fno-pic -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -Wa,-mtune=generic32 -ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-var-tracking-assignments -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -I/var/lib/dkms/nvidia/304.137/build -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"304.137\" -Wno-unused-function -Wuninitialized -UDEBUG -U_DEBUG -DNDEBUG -DMODULE -DKBUILD_BASENAME='"os_interface"' -DKBUILD_MODNAME='"nvidia"' -c -o /var/lib/dkms/nvidia/304.137/build/os-interface.o /var/lib/dkms/nvidia/304.137/build/os-interface.c [several compiler warnings -Wsign-compare] /var/lib/dkms/nvidia/304.137/build/os-interface.c: In function ‘os_get_current_time’: /var/lib/dkms/nvidia/304.137/build/os-interface.c:667:5: error: implicit declaration of function ‘do_gettimeofday’; did you mean ‘efi_gettimeofday’? [-Werror=implicit-function-declaration] do_gettimeofday(&tm); ^~~~~~~~~~~~~~~ efi_gettimeofday [several compiler calls] Makefile:1606: recipe for target '_module_/var/lib/dkms/nvidia/304.137/build' failed make: *** [_module_/var/lib/dkms/nvidia/304.137/build] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! Makefile:262: recipe for target 'module' failed make: *** [module] Error 1 makefile:59: recipe for target 'module' failed make: *** [module] Error 2
I tried to install the driver without dkms, but I had the same problem. The readme from nvidia couldn’t help me out. Any suggestions?
Running TOP shows that plasmashell was just eating CPU. The culprit, it seems, is a long-standing KDE bug that apparently rears its ugly head every now and then.
Temporary fix: run:
killall plasmashell; plasmashell &
…from a terminal, and it SHOULD drop back to normal. The problem, it seems, is with the notification icon(s) in your system tray…get one, or have one with an animation (weather? Network? New mail?), and you get the spike.
Upon logging in on Lubuntu 19.04 it is using sddm, but when the computer is idle too long and it goes into idle, when I go to log back in it is using xscreensaver(which I can’t stand the look of). I installed gdm3 in an attempt to change both over to a single interface, but all it did is replace sddm leaving xscreensaver as my login after idle. How can I replace xscreensaver in Lubuntu?
I tried all the copy past and other things to enable my Telegram on the Lubuntu startup.
I have an older Asus Eee PC that in previous versions of Lubuntu I was able to install and use acpi-call-dkms to disable my NVidia graphics card and enable the Intel graphics for the next boot.
I installed a fresh copy of Lubuntu:
Distributor ID: Ubuntu Description: Ubuntu 19.04 Release: 19.04 Codename: disco
I then installed acpi-call-dkms:
acpi-call-dkms is already the newest version (1.1.0-4).
When I make my call which worked in previous versions of Lubuntu (16.04):
eee:~$ sudo echo "\OSGS 0x01" > /proc/acpi/call
I get this:
bash: /proc/acpi/call: No such file or directory
I have searched around and even checked my own notes from when I upgraded to 16.04 in the past, but can’t make it work this time…
Any help would be greatly appreciated.
I have an old, 32-bit Dell Inspiron 1505 laptop that had been running an earlier version Lubuntu. I recently installed Lubuntu 18.04 and it initially worked. Then, following a major software update to that re-installation (45 minutes), an unusual boot problem occurred. Problem Statement • Press power button once: Dell splash screen > brief flash of dim background light > Grub menu appears > screen remains black for as long as I let it sit there, but the power indicator light remains ON. So power is on but with a black screen. • Press and hold power button: brief flash of dim background light > power goes OFF. Power indicator light OFF. No power to the laptop. • Press power button a 2nd time: Dell splash Screen > Grub Menu > blinking cursor > /dev/sda1/ recovering journal, followed by a minute of messages for starting various services and modules > Lubuntu desktop opens. Power light ON, hard drive light OFF, until I open a browser; then the hhd light turns ON. • So, I am able to access the GRUB menu on the 2nd power boot and open Lubuntu • I can boot from either the USB or DVD options, and from a Live DVD USB or disk Actions Taken so far: • I have run ‘Boot Repair Disk’ twice. I have posted its report at http://paste.ubuntu.com/p/WZdNGXKWzG for further info. • If it matters, the battery on this laptop is no longer taking a charge. • I have run MemTest+86 and hard drive S.M.A.R.T. tests, and they show no errors • Sda1 is using the ext4 file format. I have researched this problem and identified several potential solutions: 1. Edit Grub file and replace ‘quiet splash’ with nomodset 2. Use a different kernel (I only have 1 on the Grub menu) 3. Disconnect a USB mouse (didn’t help) 4. Substitue gdm for lightdgm as default log in manager (how to do this?) 5. Boot into a recovery mode and run fsck 6. Examine the /var/log/dpkg.log for errors 7. I have read there is a bug with Lubuntu 18.04 on 32-bit systems So if Grub menu works, power to the laptop is on (on 2nd power button), and hardware is not an issue (hhd and RAM tested good), then at what point does this boot problem occur, what does ‘recovering journal’ imply, and how do I fix it? It seems to me to be a software, rather than a hardware problem, but any suggestions would be most appreciated to this highly frustrating boot problem. Thanks.
I use Mac for work, Meta+C/V seems a much saner combination to me than having to use Shift in terminal because of INTC. I’m trying to remap the Ctrl+C/V combos in LXQT to mac-like Windows/Command+C/V, but it doesn’t seem to have any effect. What I have tried so far is adding a new global binding to
Shortcut Keys app:
xclip -out -selection primary | xclip -in -selection clipboard
This command seems to work great in terminal but has no effect in the Shortcuts App, almost as if the app is spawned in a sandbox. The idea behind it is to copy the primary clipboard (auto-populated on text selection) into the more sane/permanent clipboard that works similar to OSX. I’m not attached to the above command, if there is a cleaner way to remap
Ctrl keys in LXQT, I’ll do it. In Awesome WM, I simply added them into my
rc.lua. I did check
~/.config/openbox/lxqt-rc.xml but don’t see anything relevant there. Also, is it possible to integrate this with qlipper?