[Bug 1776483] Re: Thunar doesn't navigate correctly to the root directory on "back"/"previous"

2018-06-12 Thread ProfYaffle
** 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 sub-directories in a new tab (right click or middle 
button) (e.g. ~/sub1)
- 3. Navigate to any next-level directory (e.g. ~/sub1/sub2)
- 4. Click the back/previous button (not "up")
+ 3. Switch to that tab
+ 4. Navigate to any next-level directory (e.g. ~/sub1/sub2) in that second tab
+ 5. Click the back/previous button (not "up")
  
  What should happen:
  
  You end up back in sub1, which is the root directory of that new tab
  
  What does happen:
  
  You end up back in ~, which is the root directory of the *parent* tab in
- that window. Any subsequent child tabs will exhibit the same behaviour,
- i.e. opening another tab on ~/sub1/sub2/sub3, go down one more level and
- back and you'll end up back at ~.
+ that window - and you skip over sub1 completely. Any subsequent child
+ tabs will exhibit the same behaviour, i.e. opening another tab on
+ ~/sub1/sub2/sub3, go down one more level and back and you'll end up back
+ at ~.
  
  This appears to be limited to the "previous" function, so it's something
  stack-related - probably, taking the value off the parent stack instead
  of a tab-specific stack, if I had to guess. "Up" works as intended.
  
  ---
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  
  $ apt-cache policy thunar
  thunar:
-   Installed: 1.6.15-0ubuntu1
-   Candidate: 1.6.15-0ubuntu1
-   Version table:
-  *** 1.6.15-0ubuntu1 500
- 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.6.15-0ubuntu1
+   Candidate: 1.6.15-0ubuntu1
+   Version table:
+  *** 1.6.15-0ubuntu1 500
+ 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
+ 100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776483

Title:
  Thunar doesn't navigate correctly to the root directory on
  "back"/"previous"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1776483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776483] [NEW] Thunar doesn't navigate correctly to the root directory on "back"/"previous"

2018-06-12 Thread ProfYaffle
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 tab (right click or middle button) 
(e.g. ~/sub1)
3. Navigate to any next-level directory (e.g. ~/sub1/sub2)
4. Click the back/previous button (not "up")

What should happen:

You end up back in sub1, which is the root directory of that new tab

What does happen:

You end up back in ~, which is the root directory of the *parent* tab in
that window. Any subsequent child tabs will exhibit the same behaviour,
i.e. opening another tab on ~/sub1/sub2/sub3, go down one more level and
back and you'll end up back at ~.

This appears to be limited to the "previous" function, so it's something
stack-related - probably, taking the value off the parent stack instead
of a tab-specific stack, if I had to guess. "Up" works as intended.

---

$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

$ apt-cache policy thunar
thunar:
  Installed: 1.6.15-0ubuntu1
  Candidate: 1.6.15-0ubuntu1
  Version table:
 *** 1.6.15-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: thunar (Ubuntu)
 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/1776483

Title:
  Thunar doesn't navigate correctly to the root directory on
  "back"/"previous"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1776483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1313279] Re: xHCI host not responding to stop endpoint command

2018-06-06 Thread ProfYaffle
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 timeline isn't completely accurate, and if that patch fixes
the problem, then it should be ancient history by your 4.4.0 kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313279

Title:
  xHCI host not responding to stop endpoint command

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1313279/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1313279] Re: xHCI host not responding to stop endpoint command

2016-05-02 Thread ProfYaffle
@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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313279

Title:
  xHCI host not responding to stop endpoint command

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1313279/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1528011] [NEW] Apparently random crash out of desktop to login scree

2015-12-20 Thread ProfYaffle
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 login prompt and all applications are closed - with obvious loss of
data.

I'm just looking at installing the Intel graphics drivers to see if that
helps... there's nothing obvious in most log files, but syslog contains
these lines:

Dec 20 13:02:58 Castor whoopsie[678]: [13:02:58] Parsing 
/var/crash/_usr_bin_Xorg.0.crash.
Dec 20 13:02:58 Castor whoopsie[678]: [13:02:58] Uploading 
/var/crash/_usr_bin_Xorg.0.crash.
Dec 20 13:02:59 Castor whoopsie[678]: [13:02:59] Sent; server replied with: No 
error
Dec 20 13:02:59 Castor whoopsie[678]: [13:02:59] Response code: 200
Dec 20 13:02:59 Castor whoopsie[678]: [13:02:59] Reported OOPS ID 
fe3e7276-a719-11e5-ad2f-fa163e4aaad4
Dec 20 13:03:05 Castor org.gnome.keyring.SystemPrompter[4761]: Gtk-Message: 
GtkDialog mapped without a transient parent. This is discouraged.
Dec 20 13:04:36 Castor systemd[1]: Stopping User Manager for UID 112...
Dec 20 13:04:36 Castor systemd[4594]: Stopped target Default.
Dec 20 13:04:36 Castor systemd[4594]: Stopped target Basic System.
Dec 20 13:04:36 Castor systemd[4594]: Stopped target Sockets.
Dec 20 13:04:36 Castor systemd[4594]: Reached target Shutdown.
Dec 20 13:04:36 Castor systemd[4594]: Stopped target Timers.
Dec 20 13:04:36 Castor systemd[4594]: Stopped target Paths.
Dec 20 13:04:36 Castor systemd[4594]: Starting Exit the Session...
Dec 20 13:04:36 Castor systemd[4594]: Received SIGRTMIN+24 from PID 5794 (kill).
Dec 20 13:04:36 Castor systemd[1]: Stopped User Manager for UID 112.
Dec 20 13:04:36 Castor systemd[1]: Removed slice user-112.slice.

... with ~/.xsession-errors:

upstart: upstart-event-bridge main process ended, respawning
upstart: upstart-event-bridge main process (4822) terminated with status 1
upstart: upstart-event-bridge main process ended, respawning
upstart: upstart-event-bridge main process (4823) terminated with status 1
upstart: upstart-event-bridge respawning too fast, stopped

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Sun Dec 20 14:24:52 2015
InstallationDate: Installed on 2014-12-07 (378 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2015-12-19 (0 days ago)

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528011

Title:
  Apparently random crash out of desktop to login scree

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1528011/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1528011] Re: Apparently random crash out of desktop to login scree

2015-12-20 Thread ProfYaffle
** 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 back at
- the login prompt and all applications are closed - with obvious loss of
- data.
+ New upgrade of Xubuntu from 15.04 to 15.10 on an MSI-based series 9
+ motherboard with Intel graphics (i3-4130). You can just be toddling
+ along and BANG, you're back at the login prompt and all applications are
+ closed - with obvious loss of data.
  
- I'm just looking at installing the Intel graphics drivers to see if that
- helps... there's nothing obvious in most log files, but syslog contains
- these lines:
+ 
+ uname -a:
+ 
+ Linux Castor 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC
+ 2015 x86_64 x86_64 x86_64 GNU/Linux
+ 
+ 
+ I'm just looking at installing the Intel graphics drivers to see if that 
helps... there's nothing obvious in most log files, but syslog contains these 
lines:
  
  Dec 20 13:02:58 Castor whoopsie[678]: [13:02:58] Parsing 
/var/crash/_usr_bin_Xorg.0.crash.
  Dec 20 13:02:58 Castor whoopsie[678]: [13:02:58] Uploading 
/var/crash/_usr_bin_Xorg.0.crash.
  Dec 20 13:02:59 Castor whoopsie[678]: [13:02:59] Sent; server replied with: 
No error
  Dec 20 13:02:59 Castor whoopsie[678]: [13:02:59] Response code: 200
  Dec 20 13:02:59 Castor whoopsie[678]: [13:02:59] Reported OOPS ID 
fe3e7276-a719-11e5-ad2f-fa163e4aaad4
  Dec 20 13:03:05 Castor org.gnome.keyring.SystemPrompter[4761]: Gtk-Message: 
GtkDialog mapped without a transient parent. This is discouraged.
  Dec 20 13:04:36 Castor systemd[1]: Stopping User Manager for UID 112...
  Dec 20 13:04:36 Castor systemd[4594]: Stopped target Default.
  Dec 20 13:04:36 Castor systemd[4594]: Stopped target Basic System.
  Dec 20 13:04:36 Castor systemd[4594]: Stopped target Sockets.
  Dec 20 13:04:36 Castor systemd[4594]: Reached target Shutdown.
  Dec 20 13:04:36 Castor systemd[4594]: Stopped target Timers.
  Dec 20 13:04:36 Castor systemd[4594]: Stopped target Paths.
  Dec 20 13:04:36 Castor systemd[4594]: Starting Exit the Session...
  Dec 20 13:04:36 Castor systemd[4594]: Received SIGRTMIN+24 from PID 5794 
(kill).
  Dec 20 13:04:36 Castor systemd[1]: Stopped User Manager for UID 112.
  Dec 20 13:04:36 Castor systemd[1]: Removed slice user-112.slice.
  
  ... with ~/.xsession-errors:
  
  upstart: upstart-event-bridge main process ended, respawning
  upstart: upstart-event-bridge main process (4822) terminated with status 1
  upstart: upstart-event-bridge main process ended, respawning
  upstart: upstart-event-bridge main process (4823) terminated with status 1
  upstart: upstart-event-bridge respawning too fast, stopped
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Dec 20 14:24:52 2015
  InstallationDate: Installed on 2014-12-07 (378 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-12-19 (0 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528011

Title:
  Apparently random crash out of desktop to login scree

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1528011/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1313279] Re: xHCI host not responding to stop endpoint command

2014-11-26 Thread ProfYaffle
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 specific xHCI commits in the last couple of rc
revisions, I wouldn't hold your breath).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313279

Title:
  xHCI host not responding to stop endpoint command

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1313279/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1313279] Re: xHCI host not responding to stop endpoint command

2014-11-19 Thread ProfYaffle
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 and linking it back?

** Bug watch added: Linux Kernel Bug Tracker #65021
   http://bugzilla.kernel.org/show_bug.cgi?id=65021

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313279

Title:
  xHCI host not responding to stop endpoint command

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1313279/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs