I want to encode a videostream to H.264. But when I start the gstreamer program I get the following error. No Element >>x264enc>x264<< ```

I am using Fedora 40 with Gnome. I am somehow able to play mkv video files with vlc after installing its plugins but I want to install codecs in the system so that I could play videos with any player like Gnome videos or Haruna. Tried rpmfusion and many other but idk if I missed something there, nothing worked. Can anyone guide me to get things working?

I'm new Linux user so be kind. Whenever I boot my Linux on PC I get different uuid from media. See this dir: /media/my_name/2B283D3C465F37B722/folder_name/folder_namev1 And when I open for example InteliJ I open that folder manually. Thats good. Now when I turn off my PC and start it again I can not load that project until I manually again choose folder. Why? Because this 2B283D3C465F37B722 is not same anymore. How I can stop Linux creating new uuid like that? I also have a problem now with Steam, whenever I try to launch some game I need to install it again because of that, Steam can not recognize it I tried some cmds but dint work and I'm scared to not screw up more. NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda ├─sda1 │ ntfs System Reserved │ 50782D45782D2AE4 ├─sda2 │ ntfs 300C7DBC0C7D7E22 ├─sda3 │ vfat FAT32 7EB4-3DE8 500,3M 2% /boot/efi ├─sda4 │ └─sda5 ext4 1.0 f5ca8302-5be7-41de-a052-9d9f064d03d2 392,8G 13% / sdb ├─sdb1 │ └─sdb2 ntfs 2B283D3C465F37B7 99,9G 57% /media/my_name/2B283D3C465F37B726

MediaTomb adds album covers and DVD covers into the photo collection. That means, when you are going through your photos, you also get album covers intermixed in there. Is there a way of restricting the type of media from specific folders. So, /path/to/music will be restricted to music, /path/to/photos will be restricted to photos etc?

I have an old car with no native Bluetooth for audio, so to use my phone for music, I have a Bluetooth receiver connected to the 3.5mm aux jack in my car. The problem is controlling the playback on the phone without having to handle the phone while driving (it's illegal you know >:) ). So, I got the idea that a fun weekend project would be to hook up my Banana Pi to the car's CAN bus in order to listen for the media buttons on the steering wheel (not used while playing from aux) while also having the Banana Pi act as an A/V Media Controller for the phone to connect to via Bluetooth to control the phones media player. The easy part in all of this was connecting and sniffing the CAN bus. The Bluetooth part, not so much. (remember why I haven't touched anything Bluetooth in about 20 years..) I'm using BlueZ-5.69 under Arch Linux. I have disabled all the features except for the AVRCP profile. [bluetooth]# show Controller AA:AA:AA:AA:AA:AA (public) Name: "Car Controller" Alias: "Car Controller" Class: 0x0000050c (1292) Powered: yes PowerState: on Discoverable: no DiscoverableTimeout: 0x000000b4 (180) Pairable: yes UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0545 Discovering: no Roles: central Roles: peripheral ExperimentalFeatures: BlueZ Experimental ISO... (6fbaf188-05e0-496a-9885-d6ddfdb4e03e) As I understand, this should allow the phone to connect and the media player controls should be exposed via dbus. Discovery and pairing seem to be working fine, but after pairing is done, the phone disconnects and refuses to connect again (I actually tried setting up a NAP profile as well with bt-network and now the phone actually stays connected using the network provided). This is what happens when paring the phone seen from the bluetoothctl perspective. [NEW] Device 3C:38:F4:93:55:61 Xperia 10 Ⅳ Request confirmation [agent] Confirm passkey 935792 (yes/no): yes [CHG] Device 3C:38:F4:93:55:61 Bonded: yes [CHG] Device 3C:38:F4:93:55:61 Modalias: usb:v0FCEp020Cd0010 [CHG] Device 3C:38:F4:93:55:61 UUIDs: 00001105-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 00001112-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 00001115-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 00001116-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 00001132-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Device 3C:38:F4:93:55:61 UUIDs: a82efa21-ae5c-3dde-9bbc-f16da7b16c5a [CHG] Device 3C:38:F4:93:55:61 ServicesResolved: yes [CHG] Device 3C:38:F4:93:55:61 Paired: yes [CHG] Device 3C:38:F4:93:55:61 ServicesResolved: no [CHG] Device 3C:38:F4:93:55:61 Connected: no And the bleutoothd logs Sep 22 14:52:32 alarm bluetoothd: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000b Sep 22 14:52:32 alarm bluetoothd: src/adapter.c:connected_callback() hci0 device 3C:38:F4:93:55:61 connected eir_len 20 Sep 22 14:52:32 alarm bluetoothd: src/device.c:device_create() dst 3C:38:F4:93:55:61 Sep 22 14:52:32 alarm bluetoothd: src/device.c:device_new() address 3C:38:F4:93:55:61 Sep 22 14:52:32 alarm bluetoothd: src/device.c:device_new() Creating device /org/bluez/hci0/dev_3C_38_F4_93_55_61 Sep 22 14:52:32 alarm bluetoothd: src/device.c:device_set_class() /org/bluez/hci0/dev_3C_38_F4_93_55_61 0x5A020C Sep 22 14:52:32 alarm bluetoothd: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000f Sep 22 14:52:32 alarm bluetoothd: src/adapter.c:user_confirm_request_callback() hci0 3C:38:F4:93:55:61 confirm_hint 0 Sep 22 14:52:32 alarm bluetoothd: src/device.c:new_auth() Requesting agent authentication for 3C:38:F4:93:55:61 Sep 22 14:52:32 alarm bluetoothd: src/agent.c:agent_ref() 0x1752050: ref=2 Sep 22 14:52:32 alarm bluetoothd: src/agent.c:agent_request_confirmation() Calling Agent.RequestConfirmation: name=:1.62, path=/org/bluez/agent, passkey=935792 Sep 22 14:52:37 alarm bluetoothd: src/agent.c:agent_ref() 0x1752050: ref=3 Sep 22 14:52:37 alarm bluetoothd: src/adapter.c:btd_adapter_confirm_reply() hci0 addr 3C:38:F4:93:55:61 success 1 Sep 22 14:52:37 alarm bluetoothd: src/agent.c:agent_unref() 0x1752050: ref=2 Sep 22 14:52:37 alarm bluetoothd: src/agent.c:agent_unref() 0x1752050: ref=1 Sep 22 14:52:37 alarm bluetoothd: src/shared/mgmt.c:send_request() [0x0000] command 0x001c Sep 22 14:52:37 alarm bluetoothd: src/shared/mgmt.c:can_read_data() [0x0000] command 0x001c complete: 0x00 Sep 22 14:52:39 alarm bluetoothd: src/shared/mgmt.c:can_read_data() [0x0000] event 0x0009 Sep 22 14:52:39 alarm bluetoothd: src/adapter.c:new_link_key_callback() hci0 new key for 3C:38:F4:93:55:61 type 8 pin_len 0 store_hint 1 Sep 22 14:52:39 alarm bluetoothd: src/device.c:device_set_bonded() setting bonded for device to true Sep 22 14:52:39 alarm bluetoothd: src/device.c:btd_device_set_temporary() temporary 0 Sep 22 14:52:39 alarm bluetoothd: src/device.c:device_bonding_complete() bonding (nil) status 0x00 Sep 22 14:52:39 alarm bluetoothd: src/device.c:device_bonding_complete() setting timer for reverse service discovery Sep 22 14:52:39 alarm bluetoothd: src/adapter.c:resume_discovery() Sep 22 14:52:39 alarm bluetoothd: src/shared/mgmt.c:send_request() [0x0000] command 0x0033 Sep 22 14:52:39 alarm bluetoothd: src/shared/mgmt.c:can_read_data() [0x0000] event 0x002a Sep 22 14:52:39 alarm bluetoothd: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0033 complete: 0x00 Sep 22 14:52:39 alarm bluetoothd: src/adapter.c:add_accept_list_complete() 3C:38:F4:93:55:61 added to kernel accept list Sep 22 14:52:41 alarm bluetoothd: profiles/audio/avrcp.c:avrcp_controller_probe() path /org/bluez/hci0/dev_3C_38_F4_93_55_61 Sep 22 14:52:41 alarm bluetoothd: profiles/audio/control.c:control_init() Registered interface org.bluez.MediaControl1 on path /org/bluez/hci0/dev_3C_38_F4_93_55_61 Sep 22 14:52:41 alarm bluetoothd: src/service.c:btd_service_ref() 0x17458d0: ref=2 Sep 22 14:52:41 alarm bluetoothd: src/service.c:change_state() 0x17458d0: device 3C:38:F4:93:55:61 profile avrcp-controller state changed: unavailable -> disconnected (0) Sep 22 14:52:41 alarm bluetoothd: profiles/audio/avrcp.c:avrcp_target_probe() path /org/bluez/hci0/dev_3C_38_F4_93_55_61 Sep 22 14:52:41 alarm bluetoothd: src/service.c:btd_service_ref() 0x17524c0: ref=2 Sep 22 14:52:41 alarm bluetoothd: src/service.c:change_state() 0x17524c0: device 3C:38:F4:93:55:61 profile audio-avrcp-target state changed: unavailable -> disconnected (0) Sep 22 14:52:41 alarm bluetoothd: src/device.c:device_svc_resolved() /org/bluez/hci0/dev_3C_38_F4_93_55_61 err 0 Sep 22 14:52:47 alarm bluetoothd: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000c Sep 22 14:52:47 alarm bluetoothd: src/adapter.c:dev_disconnected() Device 3C:38:F4:93:55:61 disconnected, reason 3 Sep 22 14:52:47 alarm bluetoothd: src/adapter.c:adapter_remove_connection() Sep 22 14:52:47 alarm bluetoothd: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 3C:38:F4:93:55:61 type 0 status 0xe Sep 22 14:52:47 alarm bluetoothd: src/device.c:device_bonding_complete() bonding (nil) status 0x0e Sep 22 14:52:47 alarm bluetoothd: src/device.c:device_bonding_failed() status 14 Reading this line Sep 22 14:52:41 alarm bluetoothd: profiles/audio/control.c:control_init() Registered interface org.bluez.MediaControl1 on path /org/bluez/hci0/dev_3C_38_F4_93_55_61, it looks promising, but it disconnects after just a second or less. So, after getting this far, I went down the rabbit hole of Bluetooth standards for about a week, implementing my own AVRCP profile and service until I gave up. Then I dug up an old iPhone and paired it with the Banana Pi and just pressed connect on the phone and this is what I got back [agent] Authorize service 0000110e-0000-1000-8000-00805f9b34fb (yes/no): yes [NEW] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 [default] [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Repeat: off [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Shuffle: off [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Status: stopped [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Key: Title [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Value: [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Key: TrackNumber [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Value: 0x00000000 (0) [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Key: NumberOfTracks [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Value: 0x00000000 (0) [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Key: Duration [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Value: 0x00000000 (0) [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Key: Album [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Value: [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Key: Artist [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Value: [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Key: Genre [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Track Value: [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Position: 0x00000000 (0) [CHG] Player /org/bluez/hci0/dev_58_E2_8F_62_31_7C/player0 Position: 0x00000000 (0) It works! So my question now is why does the iPhone connect to the Media Controller service without any problems when any Android phone (3 of which I have available) won't even try to connect after pairing? I'm really at a loss here, so any insight would be greatly appreciated.

I installed Debian 7 using a USB flash drive "burned" from the first DVD ISO of the Debian installation CD/DVD. I did a very minimal install without Debian desktop environment, Print server and Standard system utilities. After installation and a reboot, I was presented with a console with the words *Debian GNU/Linux 7 hostname tty1*. I supplied the login username and password. After I typed the command sudo apt-get install xorg, an error message popped up stating: Media changed: please insert the disk labeled 'Debian GNU/Linux 7.4.0 _Wheezy_ - Official amd64 DVD Binary-1 20140208-13:47' in the drive and press Enter I inserted the same USB flash drive into the same port and after waiting for a few seconds, I pressed Enter. The same error message popped up. I have tried the following steps on the advice of some of my colleagues: 1. remove/delete all the entries in /etc/apt/sources.list and reboot the computer 2. dmesg and fstab show that the USB thumb drive is mounted on /dev/sdb1 3. sudo mount /dev/sdb1 /media/usb0 4. sudo apt-cdrom -m -d /media/usb0 add After doing the above, the following error message appears: Using CD-ROM mount point /media/cdrom/ Identifying.......{a long string of alphanumeric characters} Scanning disc for index files............... Found 0 package indexes, 0 source indexes, 0 translation indexes and 0 signatures W: Failed to mount '/dev/sr0' to '/media/cdrom/' E: Unable to locate any package files, perhaps this is not a Debian disc or the wrong architecture I prefer to install Xorg (60MB) and gnome-core (400MB) from the USB stick. The NGO that I am working with is in a developing country with a very basic internet access infrastructure. Internet access is very patchy and the average download speed is less than 2 Mbps.

I notice that the pw-play command (pipewire play audio file) accepts a media-role parameter. It's not clear what are the valid options for media role, and what impact does it have. I've search the man pages and online docs, and there is little info. Anyone know?

My girlfriend accidently bought an audio book on the internet and she saved it on my hard disk in windows media audio format (.wma) and now she asks me how to listen to it. I'm a bit puzzled this format still survived. I'm on ArchLinux, kernel 4.2.1-1-ARCH. My first idea was simply trying to read it with VLC as it usually is a general problem solver for audio files and comes with a couple of codecs. But it didn't work. Second idea was converting, I usually use Audacity for quick format swaps, but after several attempts of exporting to ogg/vorbis or ogg/opus I noticed Audacity already failed to read the proprietary file format. I looked up the codecs section on arch wiki but it does not contain any hints for WMA. How to proceed? How to convert audio/x-ms-wma to audio/ogg, audio/vorbis, or audio/opus format?

On my **Ubuntu Linux 18.04** machine I have a whole bunch of WMA files (don't ask) which have gotten mixed up with several files from another computer that are DRM protected. The latter won't play and even crash some player software. Is there a quick-and-easy way to recurse through the entire subdirectory tree and detect which WMA files are DRM protected? I've seen solutions based on Windows XP and Powershell, but nothing for *ix. Mind you, I'm NOT looking for a (legally dubious) way to strip off the DRM protection; I just need to find out which ones are DRM protected without trying them out one by one so I can remove them. Advise to discontinue the use of WMA and switch to more sensible formats instead is unnecessary; I never use WMA if I can possibly avoid it. However, the people who pay for my meal ticket require me to support this [censored] so I have little choice.

In windows music files have metadata like artist name, album name associated with them. How is this metadata stored. Is it stored in file system like other file attributes or is it part of MP3 data that Windows Explorer extracts using a MP3 reader plugin? Is it possible to read/change this information in Linux? Is it possible with commandline? *(I know these attributes can be set using Rhythymbox or some music player but I'm curious if these could also be set directly. Like in Windows the windows itself shows you artist information if you right click the file and open properties dialog)*

I have some MVs that is recorded from a TV, but timeline was incorrect somehow: Anyone know some tool that can fix it ? The media plays fine, just the displayed stuff doesn't look good

My desktop environment seems to know what music I am playing. I want to be able to check that from the command line too. Is there a tool or dbus query that will tell me what music or media is playing at the moment, and preferably what app it is playing in? The are many possible applications for this, but my actual use case is that I want to queue up playing some music from the CLI after a one hour music set finishes playing in YouTube on Chrome.

I have dual booted kali linux with windows 11 and all the media keys combination and media buttons works fine in windows. I have also seen many people having the same issue as well, but the problem is something else i guess. When i tried kali linux as a live system from usb all the keys, buttons and other things worked great. Whats the reason for this weird behaviour, Did i miss something in installation process. Thanks and please help

Is it possible to share a directory with media files to an Apple TV (Gen 2 & 3) using Home Sharing on a Linux machine? I've found some solutions suggesting DAAP but none of them seems to be for video or Apple TV. - http://linuxhomeserverguide.com/mediaserver/firefly.php - iTunes DAAP server setup on Debian Linux - LinuxConfig.org I would prefer a native solution instead of for example running iTunes through Wine.

I am trying to use the F3 program (Fight flash fraud) to test an external USB disk drive. The name of this external USB disk drive is "TEST A". The syntax of the commands that I would like to use are as follows: > f3write /mount/(username folder)/(USB ID) > Example: f3write /mount/root/7A3C-VD3D > > f3read /mount/(username folder)/(USB ID) > Example: f3read /mount/root/7A3C-VD3D Documentation: https://fight-flash-fraud.readthedocs.io/en/latest/usage.html#how-to-use-f3write-and-f3read Now from the command above, one would see the VID and PID of the USB Flash drive would be 7A3C-VD3D and I would infer that I would need to determine the VID and PID of my external hard disk drive to be able to scan it with the f3 program. However I tried lsusb to get the VID and PID of my device > Bus 002 Device 002: ID 0bc2:5031 Seagate RSS LLC FreeAgent Go Flex USB > 3.0 Which is 0bc2:5031 So following the syntax of the command above I tried: > f3read /mount/root/0bc2-5031 It does not work. The program tells me It can't find the directory. > f3read /media/root/0bc2-5031 Again it does not work. The program tells me It can't find the directory. However executing the command > f3read /media/root/"TEST A" It works. The f3 program reads the device. 1. Why is it necessary to determine the VID and PID of a USB device if its mounted via /mount/root/? 2. Why is it unnecessary to determine the VID and PID of a USB device if its mounted via /media/root? If there's a backstory to it as well, I would like to know to gain a deeper understanding. AFAIK, /mnt is for temporary mounting and /media is IF the linux distro auto mounts the device for you, then the device will most likely appear here. Its annoying to have to constantly check 2 directories whenever mounting a USB.

I am attempting to format some CF cards for use in an OLD digital camera (1995 Kodak DCS460). The camera uses PCMCIA Type III. It came with a Type III 260MB hard drive. If I format the CF card under Linux or Windows, as FAT16, the camera can see the card, and will write to it, but the resultant file won't be visible, and has to be recovered with a data recovery scanning tool. One thing I tried was to dd the image of the 260MB hard drive, and write that to a 512MB CF card. With this image, the camera can correctly write to the card, and the images can be seen and copied off directly in a card reader. The partition of the 260MB hard drive shows as FAT16/msdos, same as the one I formatted directly. There is also a folder with a driver in it from the hard drive image. I copied that to a 1GB CF card formatted as FAT16, but got the same behavior of unreadable files. Other users of these cameras report being able to use them with up to 2GB PC card hard drives, so I don't think 260MB is the limit here. Any ideas what might be different about the FAT16 formatting that came on the PCMCIA hard drive vs. the FAT16 formatting applied by GParted and other tools? Any suggestions on tools that can show me things like file allocation tables, in case these are being handled differently between the two formats? Edit: One new piece of information I have: the 260MB image that works fine in the camera has these properties: Device Boot Start End Sectors Size Id Type /dev/sdb1 * 34 509183 509150 248.6M 6 FAT16 I cannot create a partition that starts on less than sector 2048. I tried fdisk and gparted. Edit 2: I found that, with the dos compatibility flag set, I was able to create a partition starting at 34. I used fdisk to create a 2GB partition (max for FAT16) on a 5GB PCMCIA hard drive and set it to type 6 and bootable. I then formatted it as FAT16 with gparted. In a Linux machine or a Windows machine it shows as a fine 2GB drive. The camera says it's not formatted. Edit 3: After building a Windows 98SE system, I was able to use the camera's original TWAIN driver to manage it. This allowed me to format cards in the camera. After formatting, these cards (up to 2GB) work fine in the camera and can be directly read in PC readers. I am still not sure what is different about their format layout. One thing that does clarify things a bit, though, is how the 5GB disk acted in the camera. It would not format there. I tried creating a 2GB DOS/FAT16 partition on it using fdisk in a Linux laptop, and then formatting it in the camera. The format would fail, and the card would then have a 4.7GB partition on it. I guess "format" in the camera is actually partition-and-format, and it uses the whole drive even if that results in something beyond the capabilities of FAT16. dd-ing the format from a 1GB CF card that was formatted in the camera does work on the 5GB drive (although with only 1GB, as expected). fdisk says the layout of the 1GB CF card is: Device Boot Start End Sectors Size Id Type /dev/sdb1 63 2014991 2014929 983.9M 6 FAT16 Although I initially created a partition starting on sector 34, the camera format starts at 63. lsblk says the file system is vfat. I had been trying FAT16. The 512MB CF card was similar (starting on sector 63 and with vfat for the FS). So, in a nutshell, I guess the larger drives (> 260MB?) need to start at 63 (even though lsblk says they're still using 512 byte sectors), have one primary, non-bootable, FAT16 partition, and be formatted with vfat.

I've installed Mediawiki v1.24.1 on my server which is running RHEL7. I've installed it under /var/www/foohelp/wiki. However, when I try to upload a file, I get the following error: [f3eae72a] /foohelp/wiki/index.php/Special:Upload Exception from line 1871 of /var/www/foohelp/mediawiki-1.24.1/includes/filerepo/file/LocalFile.php: Could not acquire lock for 'User-default.png.' Backtrace: #0 /var/www/foohelp/mediawiki-1.24.1/includes/filerepo/file/LocalFile.php(1174): LocalFile->lock() #1 /var/www/foohelp/mediawiki-1.24.1/includes/upload/UploadBase.php(738): LocalFile->upload(string, string, string, integer, array, boolean, User) #2 /var/www/foohelp/mediawiki-1.24.1/includes/specials/SpecialUpload.php(467): UploadBase->performUpload(string, string, boolean, User) #3 /var/www/foohelp/mediawiki-1.24.1/includes/specials/SpecialUpload.php(186): SpecialUpload->processUpload() #4 /var/www/foohelp/mediawiki-1.24.1/includes/specialpage/SpecialPage.php(363): SpecialUpload->execute(NULL) #5 /var/www/foohelp/mediawiki-1.24.1/includes/specialpage/SpecialPageFactory.php(584): SpecialPage->run(NULL) #6 /var/www/foohelp/mediawiki-1.24.1/includes/MediaWiki.php(275): SpecialPageFactory::executePath(Title, RequestContext) #7 /var/www/foohelp/mediawiki-1.24.1/includes/MediaWiki.php(584): MediaWiki->performRequest() #8 /var/www/foohelp/mediawiki-1.24.1/includes/MediaWiki.php(435): MediaWiki->main() #9 /var/www/foohelp/mediawiki-1.24.1/index.php(46): MediaWiki->run() #10 {main} If I edit /includes/filebackend/FileBackendGroup.php and modify LockManager to 'lockManager' => 'fsLockManager', and modify permissions as follows: chown -R apache:apache images/ chown -R 755 images/ I get the following error: (Could not create directory "mwstore://local-backend/local-public) I've tried most of the forums and there is no solution that seems to fix my problem. Any help would be appreciated.

I'm on Linux Mint 19. Sometimes my media keys (play, pause, next, etc.) work fine with media apps (Spotify, in my case). Sometimes they do not work, and sometimes they even end up controlling media in my browser. Even though there is nothing in browsers, they do not "connect" to Spotify. What can I do? Media keys works nice on Chrome.

I want to convert a set of flac files to aac using best resolution for aac file . I found this tool [audio convert](https://savannah.nongnu.org/projects/audio-convert) but I am missing the man page or a help side. The command works when I use audio-convert .flac but it starts some graphical choice wizard. Is there a way to only use one terminal command so I can batch it over a set files?

I'm developing an application which at some point needs to write in a USB drive unit. The application gets executed with non-superuser permissions and I've thought the best way to write on the drive would be to have it mounted with the flush option as soon as the drive gets inserted, this way, theoretically I don't need to do any umount operation, with this udev rule: ACTION="add", KERNEL="sd*[0-9]", SUBSYSTEMS="usb", RUN+="/bin/sh mymountscript.sh '%E{DEVNAME}'" The mount script tries to invoke the command this way: mount -o --flush $1 /media/my-user/my-usb-unit But I get this mount error : mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error What it's curious about it is that I get this error only when trying to mount it through the udev rule, if I invoke mymountscript.sh myself the unit gets properly mounted in the point. Apart from a solution for this issue, I would like to know if it's risky to do it this way (I understand it is because I don't umount the drive after the file is written). If I go the other way, I would need the application script (which gets executed on behalf of the user) to be able to mount/umount the unit himself. For this, I would need to save the device name somewhere when it gets inserted and also to grant mount permissions to the application. The OS is Xubuntu 16.04.