All perguntas(ubuntu)

Instalei o Ubuntu 24.04.2 LTS em um novo PC e estou enfrentando um problema com o adaptador Bluetooth. O sistema o detecta e parece estar ligado, mas não consegue encontrar nenhum dispositivo Bluetooth próximo.

Aqui estão as informações relevantes do sistema e diagnóstico:

Sistema operacional: Ubuntu 24.04.2 LTS Versão do kernel: 6.11.0-24-generic Adaptador Bluetooth: Rádio Bluetooth IMC Networks (ID USB 13d3:3600)

Saídas de diagnóstico:

Saída lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 004: ID 30fa:2350 INSTANT USB Keyboard
Bus 003 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 006: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 003 Device 007: ID 30fa:0400  USB Optical Mouse
Bus 003 Device 008: ID 13d3:3600 IMC Networks Bluetooth Radio
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub

lspci | grep Ethernet:

84:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 0c)

lsmod | grep bluetooth e lsmod | grep btusb saída:

bluetooth              1028096  34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
btusb                   69632  0
btrtl                   36864  1 btusb
btintel                 69632  1 btusb
btbcm                   24576  1 btusb
btmtk                   36864  1 btusb
bluetooth              1028096  34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm

status do systemctl bluetooth

bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-04-27 12:53:16 EDT; 5min ago
       Docs: man:bluetoothd(8)
   Main PID: 960 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37563)
     Memory: 3.2M (peak: 3.7M)
        CPU: 17ms
     CGroup: /system.slice/bluetooth.service
             └─960 /usr/libexec/bluetooth/bluetoothd

Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/faststream
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/faststream_duplex
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/opus_05
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/opus_05
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/opus_05_duplex

listar todos os rfkill

0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

bluetoothctl mostra relatórios Energizado: sim

Controller C0:BF:BE:B6:06:D9 (public)
    Manufacturer: 0x005d (93)
    Version: 0x0c (12)
    Name: moribots
    Alias: moribots
    Class: 0x006c0104 (7078148)
    Powered: yes
    Discoverable: no
    DiscoverableTimeout: 0x000000b4 (180)
    Pairable: yes
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    UUID: Audio Sink            (0000110b-0000-1000-8000-00805f9b34fb)
    UUID: Audio Source          (0000110a-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
    UUID: Handsfree         (0000111e-0000-1000-8000-00805f9b34fb)
    Modalias: usb:v1D6Bp0246d0548
    Discovering: no
    Roles: central
    Roles: peripheral
Advertising Features:
    ActiveInstances: 0x00 (0)
    SupportedInstances: 0x05 (5)
    SupportedIncludes: tx-power
    SupportedIncludes: appearance
    SupportedIncludes: local-name
    SupportedSecondaryChannels: 1M
    SupportedSecondaryChannels: 2M
    SupportedSecondaryChannels: Coded

Comportamento do comando bluetoothctl scan on: quando executo o scan on no bluetoothctl, o comando é executado e inicia a descoberta, mas não lista nenhum dispositivo Bluetooth próximo.

Saída dmesg relevante (mensagens do kernel sobre detecção de dispositivos e relacionadas a bluetooth/firmware):

[    0.514056] Relocating firmware framebuffer to offset 0x0000000000000000[d] within [mem 0x6800000000-0x6bffffffff flags 0x14220c]
[    0.656835] xhci_hcd 0000:00:0d.0: xHCI Host Controller
[    0.656841] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 1
[    0.657122] ahci 0000:80:17.0: version 3.0
[    0.657940] xhci_hcd 0000:00:0d.0: hcc params 0x20007fc1 hci version 0x120 quirks 0x0000000200009810
[    0.658458] ahci 0000:80:17.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[    0.658461] ahci 0000:80:17.0: 4/4 ports implemented (port mask 0xf0)
[    0.658462] ahci 0000:80:17.0: flags: 64bit ncq sntf led clo only pio slum part ems deso sadm sds
[    0.658898] xhci_hcd 0000:00:0d.0: xHCI Host Controller
[    0.658900] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 2
[    0.658902] xhci_hcd 0000:00:0d.0: Host supports USB 3.2 Enhanced SuperSpeed
[    0.658936] usb usb1: Product: xHCI Host Controller
[    0.658937] usb usb1: Manufacturer: Linux 6.11.0-24-generic xhci-hcd
[    0.659549] usb usb2: Product: xHCI Host Controller
[    0.659550] usb usb2: Manufacturer: Linux 6.11.0-24-generic xhci-hcd
[    0.662654] xhci_hcd 0000:80:14.0: xHCI Host Controller
[    0.662676] xhci_hcd 0000:80:14.0: new USB bus registered, assigned bus number 3
[    0.663817] xhci_hcd 0000:80:14.0: hcc params 0x20007fc1 hci version 0x120 quirks 0x0000000200009810
[    0.664080] xhci_hcd 0000:80:14.0: xHCI Host Controller
[    0.664082] xhci_hcd 0000:80:14.0: new USB bus registered, assigned bus number 4
[    0.664083] xhci_hcd 0000:80:14.0: Host supports USB 3.2 Enhanced SuperSpeed
[    0.664109] usb usb3: Product: xHCI Host Controller
[    0.664109] usb usb3: Manufacturer: Linux 6.11.0-24-generic xhci-hcd
[    0.665486] usb usb4: Product: xHCI Host Controller
[    0.665486] usb usb4: Manufacturer: Linux 6.11.0-24-generic xhci-hcd
[    0.667970] scsi host0: ahci
[    0.668049] scsi host1: ahci
[    0.668094] scsi host2: ahci
[    0.668139] scsi host3: ahci
[    0.668190] scsi host4: ahci
[    0.668237] scsi host5: ahci
[    0.668283] scsi host6: ahci
[    0.668324] scsi host7: ahci
[    0.900715] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[    1.145479] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[    1.294731] usb 3-2: new high-speed USB device number 3 using xhci_hcd
[    1.543702] usb 3-3: new low-speed USB device number 4 using xhci_hcd
[    1.792280] usb 3-7: new high-speed USB device number 5 using xhci_hcd
[    2.045769] usb 3-8: new full-speed USB device number 6 using xhci_hcd
[    2.296268] usb 3-9: new low-speed USB device number 7 using xhci_hcd
[    2.546264] usb 3-14: new full-speed USB device number 8 using xhci_hcd
[    2.676615] usb 3-14: Product: Bluetooth Radio
[    3.288546] intel_vpu 0000:00:0b.0: [drm] Firmware: intel/vpu/vpu_37xx_v0.0.bin, version: 20230726*MTL_CLIENT_SILICON-release*2101*ci_tag_mtl_pv_vpu_rc_20230726_2101*648a666b8b9
[    3.296754] Bluetooth: Core ver 2.22
[    3.317632] NET: Registered PF_BLUETOOTH protocol family
[    3.317635] Bluetooth: HCI device and connection manager initialized
[    3.317638] Bluetooth: HCI socket layer initialized
[    3.317639] Bluetooth: L2CAP socket layer initialized
[    3.317643] Bluetooth: SCO socket layer initialized
[    3.374792] rtw89_8851be 0000:83:00.0: loaded firmware rtw89/rtw8851b_fw.bin
[    3.376058] rtw89_8851be 0000:83:00.0: Firmware version 0.29.41.3 (65cefb31), cmd version 0, type 5
[    3.376060] rtw89_8851be 0000:83:00.0: Firmware version 0.29.41.3 (65cefb31), cmd version 0, type 3
[    4.372663] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.372666] Bluetooth: BNEP filters: protocol multicast
[    4.372670] Bluetooth: BNEP socket layer initialized
[    4.373513] Bluetooth: MGMT ver 1.23
[   15.142427] Bluetooth: RFCOMM TTY layer initialized
[   15.142434] Bluetooth: RFCOMM socket layer initialized
[   15.142438] Bluetooth: RFCOMM ver 1.11

Alguém pode me ajudar a identificar qual driver preciso instalar? Este driver está instalado em um PC Asus ROG700 pré-montado.

Atualizei recentemente da versão 20.04 para a 22.04 e o Firefox perdeu as decorações das janelas (ou seja, não há barra de título, nem alças nos cantos, e não consigo movê-lo ou redimensioná-lo). Encontrei várias postagens semelhantes, todas mencionando o uso das configurações do Gnome (não, estou usando o Fluxbox), a reativação da barra de título no menu "Personalizar Barra de Ferramentas" (não há nenhuma caixa de seleção que faça isso), e outras sugerem mexer no MOZ_GTK_TITLEBAR_DECORATION e/ou no GTK_CSD, mas nenhuma delas parece afetar o comportamento.

Não que eu ache que isso importe, o hardware é uma minitorre Dell mais antiga com uma placa de i7-6700vídeo Intel integrada HD Graphics 530.64G RAM

Outras coisas que são completamente ruins:

• não responde aos atalhos do teclado.
• os menus suspensos ativados com o mouse seguem o foco para outras áreas de trabalho

Alguém aqui tem outras ideias de como recuperar as decorações das janelas?

Eu instalei o Ubuntu 25.04 há alguns dias, após a última atualização, um novo ícone fantasma com o nome "Fortune" apareceu na tela do inicializador de aplicativos, este Fortune não existe no centro de aplicativos e não está instalado e não consigo removê-lo.

Quero criptografar o sistema de arquivos raiz de uma instalação do Ubuntu Server 24.04 no meu Raspberry Pi 5. Não tenho cabos para o conector microHDMI estranho que eles usam nos novos Pis, então seria legal fazer isso sem o headless. O sistema de arquivos raiz está localizado em um cartão SD, e eu gostaria de usar arquivos de chave para criptografia em vez de senhas. Há esta resposta e este guia , mas nada sobre como fazer isso sem o headless, infelizmente.

Estou configurando meu servidor de nuvem doméstico para testar tudo antes de comprar um gabinete de disco rígido multibaia adequado e alguns discos para construir um RAID. Quero usar um adaptador USB 3.0 para SATA barato e um disco WD Purple de 2 TB que tenho. O disco está funcionando no meu PC principal, conectado à porta SATA, mas se eu conectar o adaptador USB a uma porta USB 3.0, o disco não é detectado pelo lsblk. Se eu conectá-lo a uma porta USB 2.0, ele é detectado corretamente. O mesmo ocorre no meu PC com Windows. O adaptador tem entrada de 12 V, pois o disco é de 3,5 polegadas e o sistema está executando o Ubuntu Server mais recente. Alguém pode ajudar?

Tenho uma nova instalação do Ubuntu 22.04 com Wine 9 e a versão mais recente do PlayOnLinux.

Toda vez que crio uma nova unidade virtual pelo POL, durante a inicialização ele tenta baixar/instalar o Mono e o Gecko, mas a fase de download trava para sempre (a conexão com a internet não tem problemas).

O que eu poderia fazer para resolver esse problema?

Muito obrigado!

Tenho uma configuração dual-boot Ubuntu 24.04-Windows 11 em um laptop. Comecei com o Gnome com gdm e depois migrei para o KDE Plasma com sddm.

Meu Ubuntu Gnome Desktop tinha várias coisas faltando. Suspeitei que o sistema estivesse corrompido. Um exemplo é que não consegui instalar o R ​​com o apt. Além disso, meu navegador Firefox não funcionou. Há uma série de outros problemas. Então, estou pensando em reinstalar o Ubuntu e começar do zero.

Alguma dica sobre como reinstalar o Ubuntu com segurança (ou substituir o Ubuntu por uma distribuição diferente)? ​​Meu Windows tem alguns softwares profissionais que não posso perder.

Antes de sinalizar isso como duplicado, observe que já tentei todas as soluções neste tópico

meu /etc/samba/smb.conf

# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
   logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = classic
# primary domain controller', 'server role = classic backup domain controller'
# or 'domain logons' is set 
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/useradd --create-home %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
#   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/tmp
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

[media]
    comment = Medias
    path = /home/vincent/Media
    read only = yes
    browsable = yes
    public = yes
    guest ok = yes
    guest only = yes
    mangled names = no 

/home/vincent/Mídia e conteúdo têm 755 permissões

Reiniciei o serviço samba sudo service smbd restart

Em outra máquina Ubuntu, com o Nautilus, acessei a rede, encontrei meu servidor, cliquei nele e escolhi o compartilhamento de mídia. O pop-up de login aparece e eu escolho "Conectar como Anônimo" e clico em "Conectar". Recebo um erro: "Não foi possível acessar o local. Falha ao montar o compartilhamento do Windows: Permissão negada".

Se eu tentar conectar como usuário registrado, nome de usuário convidado, domínio GRUPO DE TRABALHO, senha vazia, então Conectar, recebo a mensagem "Não foi possível acessar o local. Falha ao montar o compartilhamento do Windows: argumento inválido".

Estou usando um laptop Acer Aspire Lite (AL15-41) e Ubuntu 24.04. O problema é que o Ubuntu não está reconhecendo dispositivos Bluetooth (meu celular e meu alto-falante). Meu celular não estava reconhecendo meu laptop.

Mudei o kernel para a versão mais recente. Nenhuma mudança nesse problema. C O que posso fazer agora?

Estou tentando instalar o Ubuntu em um VMware que já possui um sistema operacional convidado Kali Linux instalado. Quando me pedem para apagar o disco e instalar o Ubuntu, se eu prosseguir, o sistema operacional convidado Kali Linux também será excluído?