[Desktop-packages] [Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode

2021-04-01 Thread Bob Briscoe 
I'm adding the following, so searches of this symptom will also find
this thread:

Once the bug is triggered, it also repeatably affects LibreOffice Calc -
if you click-select a worksheet tab or drag-select a set of cells then
release mouse, it enters drag-and-drop mode, and (strangely) draws a
thick border around the selection, which you cannot undo or reformat.

I can exit DND mode with ESC. And temporarily remove the problem with the 
xinput solution, but 
I agree with #53 that disabling touch screen is insufficient - you need to 
re-enable too.

System details:
Lenovo Yoga 3 Pro with ATML1000:00 03EB:8A10 touch screen
20.04.1-Ubuntu (although this bug has been affecting previous versions for me)
Linux kernel 5.8.0-48-generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/402892

Title:
  Mouse cursor gets stuck in "drag and drop" mode

Status in OpenShot Video Editor:
  New
Status in X.Org X server:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in rapidsvn package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: rapidsvn

  When clicking on the Bookmark root or on one of the bookmarks below
  the mouse cursor gets stuck in "drag n drop" mode, blocking all
  keyboard entry and also mouse clicks for the the whole GUI
  (systemwide).

  Unfortunately I cannot provide any debug or other information, as I
  have to reboot everytime.

  I am running Ubuntu 9.04 with compiz enabled.

  Many thanks in advance for your help with this problem,
  /nxT

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-20 Thread Bob Briscoe 
PS. I double-checked that there were no nautilus processes hanging
around before removing nautilus-image-converter. And I double-checked
that the features of nautilus-image-converter were no longer showing
within nautilus before backtracing.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1887315

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-20 Thread Bob Briscoe 
Done `sudo apt remove nautilus-image-converter`.
Still crashes the same (tried first without gdb, then with).
backtrace attached (produced as before).


** Attachment added: "gdb backtrace output for nautilus bug #1887315"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+attachment/5394326/+files/gdb-nautilus2020-07-20.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1887315

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-18 Thread Bob Briscoe 
Do you want/need me to remove any of the extension packages, or can you
take it from here?

Regarding where to post my feedback on the DebuggingProgramCrash
instructions, I was really looking for some way to give feedback to the
authors of the wiki page, not a discussion forum. I've emailed the
person who last edited the page, but I was expecting a more systematic
way to collect wiki feedback.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1887315

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-17 Thread Bob Briscoe 
Att'd: nautilus extensions installed. The only one I'm aware of having
explicitly installed is nautilus-image-converter (and of course
nautilus-dbgsym).

** Attachment added: "nautilus extensions installed re. bug #1887315"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+attachment/5393608/+files/20200717-ra-nautilus-extensions.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1887315

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-17 Thread Bob Briscoe 
gdb output attached.

When overtyping the search field in nautilus within gdb, it didn't crash
in the same way: the nautilus window hung (whereas without gdb nautilus
crashed). So I did -C in gdb as instructed. But then I got [Wait /
Force Quit] over the nautilus window and gdb had become unresponsive,
with the nautilus process as a defunct child.

So, I killed gdb, ran it again, and this time, once I had got nautilus
in its hung state, I completed the gdb output without using -C.


PS. I would like to give review comments on the DebuggingProgramCrash 
instructions. I had to guess what was meant on a number of points. Where's the 
appropriate place to post a review?

** Attachment added: "gdb output for nautilus bug #1887315"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+attachment/5393586/+files/gdb-nautilus.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1887315

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-17 Thread Bob Briscoe 
I'm following the instructions to upload a backtrace. I've disable apport, but 
I've floundered on step 1 of Generating the backtrace.
"1. Please ensure you have packages with debug symbols installed. You can 
do this by following the instructions at DebuggingProgramCrash."

Can you give more specific instructions for this case? I can't find a
nautilus package with debug symbols installed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1887315

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-12 Thread Bob Briscoe 
Another way to type into the search field over a remote share that makes
nautilus crash: type the first character (incorrectly), backspace, then
re-type.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1887315

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  New

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1887315] [NEW] Nautilus crashes while over-typing search term on remote smb file system

2020-07-12 Thread Bob Briscoe 
Public bug reported:

==Impact==

nautilus crashes while typing the term to search a remote directory
within an NT file system over the smb protocol. The problem may affect
other remote file systems or protocols, but I have only tested these.

Repeatable.

==How to repeat==

1. Open Nautilus
2. In the sidebar, click Other Locations
3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
4. Click Connect
5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
6. Click the search icon and type a search string
7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

Nautilus crashes.

Typically, prior to the window disappearing the graphics freezes within
the search field showing both the previous and the current search terms
on top of each other.

Often it is necessary to kill the nautilus process and/or reboot the smb
daemon on the remote machine before being able to use the smb share
again.

Before typing a second search term, if instead of over-typing, you
delete the selection either i) with the  key; or ii) clicking
the (x) to clear the field; or iii) clicking the search icon twice to
remove and reinstate the search field; it is possible to search for a
second term without crashing.

It is possible that the crash depends on how fast the search term is
typed, because nautilus starts searching as you type. I have tried to
paste a search term over an existing term, which usually seems to work
without crashing. On the other hand, I have had nautilus crash when
typing a search term after having explicitly cleared the search field,
but before nautilus has displayed the full contents of the directory
again (about 150 files).

I have not had nautilus crash when over-typing the search field for a
local file system, whether ntfs or ext3.

==Related bugs==

Bug #1795028 seems to be identical, and claims to have been fixed in
package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be
fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more
precisely how to reproduce the crash.

==Crash Reports==

A typical crash report from my system is here:
https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 12 21:03:59 2020
InstallationDate: Installed on 2020-06-03 (38 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1887315

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  New

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  t

[Desktop-packages] [Bug 1507652] Re: thunderbird main window can't be started from unity starter icon if email compose window is opened

2015-11-19 Thread Bob Briscoe 
Solution: With the focus on the open compose window, select from menu:
Tools > Mail & Newsgroups [Ctrl+1]

There are related inconsistencies though.
* If an email is opened for reading in a new window, the shortcut key changes: 
Tools > Mail & Newsgroups [Alt+1]
* If only search, message filters, activity manager and preferences windows are 
open, no top level menus are visible and neither [Ctrl+1] nor [Alt+1] does 
anything.

The latter is a bug. However, there is a work-round that works in the other 
cases as well:
* Launcher > right click Thunderbird icon > "Compose New Message", which then 
gives access to the first solution above.

This problem is irritating for me, because I often have large numbers of
Thunderbird windows open, and until I found the above
solutions/workrounds, if I accidentally closed the main window (which I
have done many times),  in order to reopen it, I had to close all the
other windows, thus losing track of all my work-in-progress when I
restarted Thunderbird.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1507652

Title:
  thunderbird main window can't be started from unity starter icon if
  email compose window is opened

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  If the email compose window has been opened in the `thunderbird` main
  window and then the main window is closed so that the compose window
  stays open there's no way to open the main window again without
  closing the compose window.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: thunderbird 1:38.3.0+build1-0ubuntu0.15.04.1
  Uname: Linux 4.2.2-040202-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter3036 F pulseaudio
  BootDmesg: (Nothing has been logged yet.)
  BuildID: 20150930121410
  Channel: Unavailable
  Date: Mon Oct 19 17:18:53 2015
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-09-14 (34 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.179.1 dev eth2  proto static  metric 100 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev eth2  scope link  metric 1000 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
   192.168.179.0/24 dev eth2  proto kernel  scope link  metric 100
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  Plugins:
   IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (1.5.2-1ubuntu2)) - 
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-7-plugin)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=38.3.0/20150930121410 (In use)
  RelatedPackageVersions:
   icedtea-7-plugin  1.5.2-1ubuntu2
   rhythmbox-mozilla 3.1-1ubuntu3
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

2015-10-30 Thread Bob Briscoe 
Now it's gone back to how it was, with Ubuntu also throwing up an error
window asking if I want to report the segfault. Don't know why that
didn't happen the last couple of times even tho the segfault was in
syslog.

Summary:  libimobiledevice-utils has made no difference to this fault
for me. I shall uninstall.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1305699

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

2015-10-29 Thread Bob Briscoe 
Scrub that. Actually it's not solved (for me).  
upowerd still crashes when I connect my iPhone. It's just that Ubuntu doesn't 
complain that it has, but I hadn't checked whether the process was still 
running - it isn't. Also in syslog there's the following error:

upowerd[10490]: segfault at 3730 ip 7fe93b16ff8e sp 7ffd73132880
error 4 in libimobiledevice.so.4.0.1[7fe93b168000+1d000]

Without the iPhone connected, accessing something like the battery history GUI 
causes dbus-daemon to restart upowerd.
With the iPhone connected, the battery GUI cannot re-start upowerd, so it 
cannot display the battery history, etc.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1305699

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

2015-10-29 Thread Bob Briscoe 
@Andy_D, I installed libimobiledevice-utils. 
First time I connected my iPhone, the screen froze (except mouse pointer), 
rather than just crashing upowerd
syslog didn't log an obvious cause:

Subsequently, it seemed to be OK (I've tried once).

On the first occasion (when it crashed), my iPhone power was so depleted it had 
shut down. 
The log shows Ubuntu couldn't mount the iPhone's drive and couldn't connect to 
the iPhones network drivers. 
This is the only difference I can think of that might explain the freeze (?) 
other than that Ubuntu was also pending a restart following a software update. 
Whereas the subsequent time, it had had the restart.

I'll add to this post if it freezes again. Otherwise, thank you for
solving this for me (us?).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1305699

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

2015-10-20 Thread Bob Briscoe 
@pitti 
+1 to requests to back-port yr fix into 14.04 LTS
For all of us who are asking, what's the likelihood please?
The no. of people who say they have this problem has reached 42, which is the 
answer to everything (except knowing whether it will be back-ported)
I guess the number of people with an iPhone or iPod etc who might also be 
suffering, but in in silence, is more than that.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1305699

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp