[Bug 1227089] Re: gvfsd-mtp crashed with SIGSEGV in g_hash_table_lookup()

2013-09-26 Thread Paul Greindl
This bug is valid for the Samsung Galaxy SIII (running Android 4.1.2) as
well.

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

Title:
  gvfsd-mtp crashed with SIGSEGV in g_hash_table_lookup()

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

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


[Bug 1215098] Re: iPhone with iOS 7 does not work on Ubuntu

2013-09-23 Thread Paul Greindl
This bug is present in 13.10 as well. So it seems there hasn't been any
effort to fix this. What can be done?

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

Title:
  iPhone with iOS 7 does not work on Ubuntu

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

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


[Bug 1156012] [NEW] nautilus crashed with SIGSEGV when opening a folder with many files

2013-03-16 Thread Paul Greindl
Public bug reported:

When opening a folder with around 3 500 files (about 5-10 MB each)
Nautilus runs on 100 % CPU, and finally crashed when switching to list-
view. After killing the main nautilus process, starting nautilus and
switching to list view before entering the folder, the CPU stayed at
60-90% and it was possible to browse the files.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu9
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 16 18:56:44 2013
Disassembly: = 0x7fbe987c6f89: Cannot access memory at address 0x7fbe987c6f89
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b'956x597+1431+306'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2013-01-21 (53 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130121)
MarkForUpload: True
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7fbe987c6f89:  Cannot access memory at address 
0x7fbe987c6f89
 PC (0x7fbe987c6f89) ok
 SP (0x7fff557e6d70) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0  0x7fbe987c6f89 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff557e6d70
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 6 (LWP 5085):
 #0  0x7fbe97d6705e in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fbe68aa2b60
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace raring

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV when opening a folder with many files

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

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


[Bug 1132901] [NEW] empathy-chat crashed with SIGABRT

2013-02-25 Thread Paul Greindl
Public bug reported:

Tried to reopen the chat-window and instead got the crash and the
preferences-dialog opened. Killing and restarting the empathy process
fixed it for a while, then it happened again.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: empathy 3.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Mon Feb 25 10:32:33 2013
Disassembly: = 0x7fad9d048037: Cannot access memory at address 0x7fad9d048037
ExecutablePath: /usr/lib/empathy/empathy-chat
InstallationDate: Installed on 2013-01-21 (34 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130121)
MarkForUpload: True
ProcCmdline: /usr/lib/empathy/empathy-chat
Signal: 6
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: empathy-chat crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace raring running-unity

** Information type changed from Private to Public

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

Title:
  empathy-chat crashed with SIGABRT

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

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