I'm closing the bug myself because the issue was only vmware horizon
keeping the hardware for itself.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I forgot to update the thread with the solution, since vmware horizon v4.3
there is n option to easily choose what to do with the usb devices connected.
To be able to use the devices normally it's just a matter of deselecting the
devices from the menu.
This bug should be closed.
Thanks for your
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
The device on /dev/sdx is not created when inserting new devices
To
No, the only thing that affected the operation of the usb ports was the
vmware horizon software. I conjectured other things before finding the
root cause.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Joan, if using a later kernel had an improving effect, then is VMware
confirmed the root/only root cause?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
The device on /dev/sdx is not c
I finally found out the cause for this, still no idea about a proper solution.
I am using vmware horizon to connect to a windows computer, it has a funcion
called usb redirection that allows you to use your usb from the windows
computer.
It seems that when vmware horizon is open, the usb devices
Done, I'm on rc7
$ uname -r
4.8.0-040800rc7-generic
What I observed is that after booting the system, the ports work
properly, but on the next day (laptop being only locked and connected to
the power outlet), they just do the wrong behavior
--
You received this bug notification because you are
Joan, to keep this relevant to upstream, one would want check for, and
test the latest mainline kernel (now4.8-rc6) as it is released.
Could you please advise?
** Tags removed: bios-outdated-1.25
** Tags added: latest-bios-1.25
--
You received this bug notification because you are a member of U
Sure, there you go
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
J5ET54WW (1.25 )
07/18/2016
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
The device on /d
Joan, please provide the output of the following terminal command (not perform
an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags removed: bios-outdated-1.24
** Tags added: bios-ou
It seems to me that the problem is on boot, I have found that:
- If I boot without a device then it doesn't work, it happened to me with a USB
to serial (not creating /dev/ttyUSB0 and also with pendrives /dev/sdx
- If I boot with the device, then I can plug / unplug without issues, even new
devi
I changed the status into confirmed (didn't see how to reopen the
issue), if I have to open a new bug referring this one, just tell me.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Ti
Hello again, it seems that the issue arose again, I don't know at what
point but it's still present. Apparently the kernel upgrade didn't fix
the issue, because when it appeared back on the new install I upgraded
the kernel again to current version, and it's still happening
$ uname -r
4.7.0-040700
Joan, let this be marked Invalid for now given it's not reproducible.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
Yes, exactly that, I can no longer reproduce it with the current system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
The device on /dev/sdx is not created when inserting new devices
Joan, to clarify, the originally reported issue is no longer
reproducible in the new install with the default Ubuntu kernel (not
upstream)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
Unfortunately I can reproduce the bug anymore, after installing 4.7rc2 the
devices appeared in my system but strangely the order was changed, so sda was
the removable disk and sdb the fixed drive, I did an dd to sdb (to create a
bootable pendrive) and screwed my system. So I'm now in a freshly i
Jaon, the next step is to fully reverse commit bisect from kernel 4.4 to
4.7-rc2 in order to identify the last bad commit, followed immediately
by the first good one. Once this good commit has been identified, it may
be reviewed for backporting. Could you please do this following
https://wiki.ubunt
Ok, I just booted into 4.7-rc2, it seems to work fine, the usb reappears
every time under /dev with the same name, and I can use it normally.
** Attachment added: "systemdlog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589997/+attachment/4680449/+files/systemdlog.txt
--
You r
I wanted to say on the last comment (I posted it before finishing) that
the only strange thing is a message in the syslog saying that the device
"appeared twice with different sysfs paths", might caused by me
plugging/unplugging the device.
--
You received this bug notification because you are a
Joan, would the latest mainline kernel (4.7-rc2) allow a test?
** Tags added: bios-outdated-1.24
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
The device on /dev/sdx is not created w
I had to patch apport-kde (see
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1368911), but
finally could use apport-collect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
The d
apport information
** Tags added: apport-collected xenial
** Description changed:
I am on kubuntu xenial (upgraded from 15.10), from a couple of weeks I
noticed that the pendrives i insert to my computer are detected but the devices
under /dev are no longer created.
I if reboot the pc with
Joan, would the following work to gather the previously requested logs:
apport-cli -u 1589997
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
The device on /dev/sdx is not created when
I tried with linux-image-4.7.0-040700rc1-generic, but couldn't boot, I
am thrown into console with this message, I had to reboot into the
linux-image-4.4.0-22-generic to boot the machine.
Error parsing PCC subspaces from PCCT
error getting socket: Address family not supported by proco
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7-rc1 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fi
Unfortunately apport-collect does not work in my system (I guess that
apport-kde is not in a very good shape, can I provide the logs in
another way?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/158999
** Package changed: udev (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
The device on /dev/sdx is not created when inserting new devices
To manage notificat
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1589997/+attachment/4678990/+files/syslog.txt
** Description changed:
I am on kubuntu xenial (upgraded from 15.10), from a couple of weeks I
noticed that the pendrives i insert to my computer are detected
29 matches
Mail list logo