Update :
I can adjust the brightness again after a sleep mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913961
Title:
impossible to adjust the brightness after upgrading the kernel to
versio
update :
same things with 5.8.0.43.49.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913961
Title:
impossible to adjust the brightness after upgrading the kernel to
version 5.8 (hwe)
To manage n
** Also affects: fedora
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/1913961
Title:
impossible to adjust the brightness after upgrading the kernel to
v
Public bug reported:
It is impossible for me to adjust the screen brightness using the slider
in the Gnome menu, nor in the energy settings.
I'm on Ubuntu 20.04.2, the Nvidia 450.102.04 drivers with an xorg session (no
.conf file in /etc/X11/)
I have an Imac 27" end2013.
This happened after the
Same observation, my NAS is in smb1, idem for my router with a USB disk.
The files are seen as folders. You can neither read the files nor delete them.
The same folder mounted in CIFS by fstab is seen correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
smbclient //192.168.1.1/USB1 --option='client min protocol=NT1'
Enter WORKGROUP\laurent's password:
Try "help" to get a list of possible commands.
smb: \>
I just added "client min protocol=NT1" to my /etc/samba/smb.conf and it works
again. Thanks to all of you for your help and sorry, as Stefan
indeed I have just checked and my router however relatively recent still
uses smb1.
"Morbius1 (morbius1) ", According to what you say, I could not access my
NAS or my router any more than a CIFS mount? it's a pity, even under
windows one can force, even if it is not recommendable from a security
p
Thank you for your help but I only indicated some tests I had done after
internet research before posting here.
Anyway, despite the changes in the smb.conf that I mentioned at the beginning
of my post, especially concerning the smb1 protocol, smbclient doesn't work. As
I said before posting the
In response to the error "Unknown parameter encountered: ", bind interfaces
only"...
Ignoring unknown parameter ", bind interfaces only", I corrected the typo and
I'll send you my smb.conf just in case.
** Attachment added: "smb.conf"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/18753
I confirm that it still works with ubuntu 19.10 up to date.
However, I can't navigate in the windows network. The folder remains empty.
The access by smb://IP/folder works, as well as smbclient //IP/folder but
smbtree tells me "Unable to initialise messaging context" but this seems to be
normal g
Sorry, I got confused with smb://.
...I've been doing a lot of tests because I'm not getting the same feedback:
laurent@laurent-iMac:~$ smbclient //192.168.1.1/USB1
Unknown parameter encountered: ", bind interfaces only"
Ignoring unknown parameter ", bind interfaces only"
protocol negotiation fai
IP of my pc : 192.168.1.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10
To manage notifications about this bug g
Thank you for coming back.
So I'm going to start from a good base and delete what I did.
laurent@laurent-iMac:~$ pkill gvfs; pkill nautilus
pkill: le pid 1184 n'a pu être tué: Opération non permise
pkill: le pid 1199 n'a pu être tué: Opération non permise
pkill: le pid 1204 n'a pu être tué: Opérat
modified the source package attributed to this bug
** Package changed: ubuntu => gvfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No more smb access after migration to UBU
Public bug reported:
Hello everyone,
I no longer have access to my devices (NAS and other pcs - windows) from
Nautilus. The command smb://IP address doesn't work anymore since the upgrade.
some tests :
1
I tried to change the parameter "client max protocol = NT1" in client max
protocol = NT1 si
15 matches
Mail list logo
