Can't run an AppImage of android-file-transfer due tue nouveau driver error

Hi.

android-file-transfer is very reliable piece of software I used on my previous LEAP 15.2 installation.

The link to the project

As there is no rpm package, I tried to compile it from source and had several complications, but that’s another issue.

I then proceeded to download and install the AppImage. When I run it I get the following error:


(base) aleksandr@localhost:~> ./Applications/Android_File_Transfer_For_Linux-1509910-x86_64_5eb53de52ef1213a6414332a5121e838.AppImage
  
/usr/bin/AppImageLauncher: /usr/lib64/libcurl.so.4: no version information available (required by /usr/bin/../lib/x86_64-linux-gnu/ap
pimagelauncher/libappimageupdate.so) 
upload worker started 
current text color value:  39 , guessed theme:  "light" 
libGL error: MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: cannot open shared object file: No such file or dire
ctory (search paths /usr/lib64/dri, suffix _dri) 
libGL error: failed to load driver: nouveau

It seems like I have nouveau installed:


(base) aleksandr@localhost:~> sudo dmesg | grep nouveau 
    2.114648] fb0: switching to **nouveau** from EFI VGA 
    2.114769] **nouveau** 0000:09:00.0: vgaarb: deactivate vga console 
    2.114811] **nouveau** 0000:09:00.0: NVIDIA GP108 (138000a1) 
    2.232745] **nouveau** 0000:09:00.0: bios: version 86.08.13.00.0c 
    2.233992] **nouveau** 0000:09:00.0: pmu: firmware unavailable 
    2.238086] **nouveau** 0000:09:00.0: fb: 2048 MiB GDDR5 
    2.263693] **nouveau** 0000:09:00.0: DRM: VRAM: 2048 MiB 
    2.263696] **nouveau** 0000:09:00.0: DRM: GART: 536870912 MiB 
    2.263697] **nouveau** 0000:09:00.0: DRM: BIT table 'A' not found 
    2.263699] **nouveau** 0000:09:00.0: DRM: BIT table 'L' not found 
    2.263700] **nouveau** 0000:09:00.0: DRM: TMDS table version 2.0 
    2.263701] **nouveau** 0000:09:00.0: DRM: DCB version 4.1 
    2.263702] **nouveau** 0000:09:00.0: DRM: DCB outp 00: 01000342 04620010 
    2.263704] **nouveau** 0000:09:00.0: DRM: DCB outp 01: 01011352 04620020 
    2.263705] **nouveau** 0000:09:00.0: DRM: DCB conn 00: 00001031 
    2.263706] **nouveau** 0000:09:00.0: DRM: DCB conn 01: 00002161 
    2.264074] **nouveau** 0000:09:00.0: DRM: MM: using COPY for buffer copies 
    2.485300] **nouveau** 0000:09:00.0: DRM: allocated 1920x1080 fb: 0x200000, bo 00000000be93205a 
    2.485905] fbcon: **nouveau**drmfb (fb0) is primary device 
    2.684470] **nouveau** 0000:09:00.0: [drm] fb0: **nouveau**drmfb frame buffer device 
    2.712241] [drm] Initialized **nouveau** 1.3.1 20120801 for 0000:09:00.0 on minor 0 
    5.872913] snd_hda_intel 0000:09:00.1: bound 0000:09:00.0 (ops nv50_audio_component_bind_ops **nouveau**]) 
    7.374897] **nouveau** 0000:09:00.0: gr: intr 00000040

Please help run the AppImage

Hi
Not sure why the normal mtp type tools won’t work?

Anyway, here is a rpm package for you to test…

https://build.opensuse.org/package/show/home:malcolmlewis:TESTING/android-file-transfer-linux

They don’t for me. android-file-transfer did. I think the motto on their github page was “It just works” — the developers claim sometimes it’s the only working way for file transferring.

Thanks, I’ve installed and run it. I get the same error message about nouveau

Hi
Are you running Wayland? What desktop environment?

What does the following show;


/sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"

Did you try the cli tool? If not can you run aft-mtp-cli --verbose -l

Do not confuse kernel driver with user space library. This file is provided by package Mesa-dri-nouveau.

I am running X11, KDE Plasma

(base) aleksandr@localhost:~> /sbin/lspci -nnk | egrep -A3 "VGA|Display|3D" 

09:00.0 **VGA** compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) 
        Subsystem: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] 
        Kernel driver in use: nouveau 
        Kernel modules: nouveau


(base) aleksandr@localhost:~> aft-mtp-cli --verbose -l 
creating device descriptor at /sys/bus/usb/devices/1-10 
creating device descriptor at /sys/bus/usb/devices/3-4 
creating device descriptor at /sys/bus/usb/devices/1-7 
creating device descriptor at /sys/bus/usb/devices/3-1 
probing device 148f:7601 
error: Permission denied 
descriptor->TryOpen() failed 
probing device 045e:074a 
error: Permission denied 
descriptor->TryOpen() failed 
probing device 046d:c077 
error: Permission denied 
descriptor->TryOpen() failed 
probing device 2717:ff40 
capabilities = 0x000001fd 
page size = 4096 
<zero-packet>  
<no-packet-size-limit>  
<bulk-scatter-gather>  
<reap-after-disconnect>  
<mmap>  
<drop-privileges>  
<conninfo-ex>  
<suspend>  
configurations: 1 
interfaces: 1 
Device usb interface: 0:0, index: 0, endpoints: 3 
read control 80 06 0300 0000 
languages[4]: 
00000000: 04 03 09 04                                     .... 

read control 80 06 03ee 0409 
OSStringDescriptor[18]: 
00000000: 12 03 4d 00 53 00 46 00 54 00 31 00 30 00 30 00 ..M.S.F.T.1.0.0. 
00000010: 01 00                                           .. 

vendor code: 0x01 
read control c0 01 0000 0004 
extended compat id os feature desctriptor[40]: 
00000000: 28 00 00 00 00 01 04 00 01 00 00 00 00 00 00 00 (............... 
00000010: 00 01 4d 54 50 00 00 00 00 00 00 00 00 00 00 00 ..MTP........... 
00000020: 00 00 00 00 00 00 00 00                         ........ 

Xiaomi-RedmiNote5-21daac96

I also checked mtp-files and it seems to do what it is supposed to — my files were listed. I may consider learning cli tools to work with my phone in the future.

Yeah, I didn’t have Mesa-dri-nouveau installed. I had considered installing it before, but I was afraid to mess up with my system video configuration. When I tried installing it with zypper, it tried to pull this package from home:Regataos repo, which caused conflicts with some other video-related packages of earlier versions from official repos.

Now I’ve overcome myself and installed Mesa-dri-nouveau with vendor change. The AppImage I had installed earlier and the .rpm, courtesy of malcolmlewis, work fine. Thank you very much.

The only thing which bothers me a bit is that the package I have compiled myself doesn’t work, but I think it is beyond our conversation and I don’t really need this one.