** Description changed:
Thunar 1.6.15 on Bionic 18.04, kernel 4.15.0-23-generic x86_64.
Behaviour seen on earlier Xubuntu versions as well.
To reproduce:
1. Open a Thunar file manager window at a directory containing
sub-directories (e.g. a home folder)
2. Open one of the
Public bug reported:
Thunar 1.6.15 on Bionic 18.04, kernel 4.15.0-23-generic x86_64.
Behaviour seen on earlier Xubuntu versions as well.
To reproduce:
1. Open a Thunar file manager window at a directory containing sub-directories
(e.g. a home folder)
2. Open one of the sub-directories in a new
I'm way out of date on this, but that patch looks like it was committed
into the Linux kernel in Mach 2015:
https://github.com/torvalds/linux/commit/227a4fd801c8a9fa2c4700ab98ec1aec06e3b44d
... which would suggest that it would have appeared "in the wild" with
3.19.2 or thereabouts?
Even if my
@jonas - OS version, kernel version? Output of uname -a and lsb_release
-a would help I've not come back to this, having run in USB2 for ~18
months, but it'd be interesting to know if it's still a problem...
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
I've seen a few reports, but more "hey, anyone...?" versus filing a bug,
so I thought I'd do the latter. Delete if a duplicate.
New upgrade of Xubuntu from 15.04 to 15.10 on a Gigabyte system with
Intel graphics. You can just be toddling along and BANG, you're back at
the
** Description changed:
I've seen a few reports, but more "hey, anyone...?" versus filing a bug,
so I thought I'd do the latter. Delete if a duplicate.
- New upgrade of Xubuntu from 15.04 to 15.10 on a Gigabyte system with
- Intel graphics. You can just be toddling along and BANG, you're
I will as soon as I can, but it obviously makes the system unserviceable
so it's not something I can do lightly.
Give me a few days and I'll find a quiet time in which I can potentially
destroy my system :-)
(Not that I did test 3.18.0-031800rc3-generic previously, so unless
there have been
I did find an upstream bug report from earlier this year:
https://bugzilla.kernel.org/show_bug.cgi?id=65021
... although haven't had a chance to progress it as getting my system
working was more of an imperative.
Might be worth everyone piling on the back of that one, or opening a new
report
