Thanks a lot
smbclient --user=userName1 --option='client min protocol=nt1'
//192.168.178.1/share1
worked ('NT1' = 'nt1' is non case sensitive).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873561
** Attachment added: "Ubuntu 19.10: Successful command: smbclient
--debuglevel=10 --user=ftpuser //192.168.178.1/share1"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1873561/+attachment/5356440/+files/Ubuntu-19.10-smbclient--debuglevel--user--IP--smb1-share1.log
--
You received this
Public bug reported:
$ smbclient --user=ftpuser //192.168.178.1/share1
protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED
Remvark, with SMB2 resources, the command runs O.K.
Remark: "I also coult not mount the SMB1 drives with "gio mount smb:",
what works easily with SMB2 drives.
I
** Attachment added: "Ubuntu 20.04: Failed command: smbclient --debuglevel=10
--user=ftpuser //192.168.178.1/share1"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1873561/+attachment/5356439/+files/Ubuntu-20.04-smbclient--debuglevel--user--IP--smb1-share1.log
--
You received this bug
I just saw, that it is not Ubuntu 20.04 beta, it is the real Ubuntu
20.04 now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872286
Title:
gio - cifs mount smb not possible "Location is not
Again: gvfs-backends is installed (it was removed without my knowledge during
the update from Ubuntu 19.10 to 20.04 beta). Perhaps you should not install a
beta version on a productive
system ;-)
When I want to mount the drive as in Ubuntu 19.10, I get:
$ gio mount
Remark: In Ubuntu 19.04, if the user/domain/password is not piped, `gio mount`
requests
the `user/domain/password`:
`$ gio mount smb://192.168.178.1/Fritz7490`
`Password required for share fritz7490 on 192.168.178.1
`User [SessionUserName]: NewUserIfDifferent
`Domain [WORKGROUP]:
I updated my Ubuntu 19.10 laptop with "sudo update-manager -d" to 20.04
beta. I always mount a small local drive in my network, because I have
there my private git repo, which is then easily available to my laptops
and to may raspberries.
I did not delete the package on my own, but there were
After installing package `gvfs-backends` and reboot, I got the follow
error:
`$ gio mount smb://192.168.178.1/PathName`
`gio: smb://192.168.178.1/PathName/: Failed to mount Windows share: Software
caused connection abort`
`gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse
I found out, that I had to install the package `gvfs-backends` to get
`gvfsd-smb`:
`$ find /usr -name 'gvfsd-smb' -exec ls -l '{}' \; 2>/dev/null`
`-rwxr-xr-x 1 root root 59704 Mär 11 17:23 /usr/libexec/gvfsd-smb`
`lrwxrwxrwx 1 root root 23 Mär 11 17:23 /usr/lib/gvfs/gvfsd-smb ->
Comments on
https://gitlab.gnome.org/GNOME/glib/-/issues/2090
showed, that there is this file `/usr/share/gvfs/mounts/smb.mount`
in Ubuntu 19.10, which is not there in Ubuntu 20.04 beta.
Inside of this file, there was a reference to the file
`/usr/lib/gvfs/gvfsd-smb`. Also a file
Sorry, should put my reading glasses on, 20:04beta's version 2.64.1-1 is
newer than 19.10's version 2.62.4-1.
I wished, I could correct messages here, unless someone else is on the
top ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Checked the (working) Ubuntu 19.04 package:
$ apt-cache policy libglib2.0-bin
libglib2.0-bin:
Installed: 2.62.4-1~ubuntu19.10.2
Candidate: 2.62.4-1~ubuntu19.10.2
Version table:
*** 2.62.4-1~ubuntu19.10.2 500
500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages
Opened
[https://gitlab.gnome.org/GNOME/glib/-/issues/2090](https://gitlab.gnome.org/GNOME/glib/-/issues/2090)
as requested, with additional comments that it works in Ubuntu 19.10 up
to kernel 5.6.3 (I use both Ubuntu and newest linux kernel).
** Bug watch added:
Public bug reported:
1) Release
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
2) Package
$ apt-cache policy libglib2.0-bin
libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
*** 2.64.1-1 500
500
I solved the problem, when I replaced inside of
~/.config/libfm/libfm.conf
the line
terminal=lxsession-default-terminal %s
by
terminal=lxterminal %s
.
Thank you very much Walter! Your questions did push me to dig much deeper and
to solve the problem in the end.
Inside of Unity I got
After I tried "lubuntu" instead of 'lxde" as desktop manager, all worked
like expected.
Then I tried it from pcmanfm within 'xfce', 'ubuntu', which failed too.
Starting via "Tools"-->"Run a Command in Current Folder..." worked
always.
--
You received this bug notification because you are a
I started "lxterminal &" from the terminal in the USB path
/media/dirk/32GB_USB3_Dirk
successfully, and this works from everywhere.
Trying to start lxterminal from another path within "pcmanfm" did not
work too from any path, so it is not the USB device.
When I did this on another computer
Public bug reported:
Tried to press F4 in pcmanfm showing an USB stick path. No lxterminal started,
it crashed.
The same happened when I tried to start a terminal via the menu
"Tools"-->"Open current folder in Terminal F4"
1) $ lsb_release -rd
Description:Ubuntu Zesty Zapus
Hi all, I was bugged by this both in Ubuntu 16.04 (any 4.4 kernel after
release) and in ArchLinUX with all actual 4.5 kernels.
My solution was to take the 4.6 kernel on ArchLinUX (testing repository), after
which I was cured from all difficulties. If you use VirtualBox with a new
4.4/4.5
Hi Daniel,
I could install the NVidia driver after you obviously made some updates. I
installed 173 a couple of days ago first and recommended drivers after new
updates later. I had the impression that it was important to install the
old drivers first.
I still have a test partition left if you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859847
Title:
virtualbox-dkms 4.1.2-dfsg-1ubuntu1: virtualbox kernel module failed
to build
To manage notifications about this bug go to:
Tried after fresh install of lubuntu 11.10 beta 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859847
Title:
virtualbox-dkms 4.1.2-dfsg-1ubuntu1: virtualbox kernel module failed
to build
To
Public bug reported:
After fresh install of lubuntu 11.10 beta 2
ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: nvidia-current-updates 280.13-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859863
Title:
nvidia-current-updates 280.13-0ubuntu3: nvidia-current-updates kernel
module failed to build
To manage notifications about this bug go
Public bug reported:
Obviously none of the current NVidia drivers (I tried the second and third or
four options) did install on my Dell Inspiron 1420 laptop.
I am using this laptop since latest beginning of 2008 with Ubuntu 64 and never
got any real problem so far (third bug).
ProblemType:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859870
Title:
nvidia-current 280.13-0ubuntu3: nvidia-current kernel module failed to
build
To manage notifications about this bug go to:
Public bug reported:
I cannot install virtualbox-dkms under lubuntu 11.10 (Oneiric).
ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: virtualbox-dkms 4.1.2-dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion:
28 matches
Mail list logo
