Re: [Bug 1173679] Re: Login to Flickr using Google ID
Well as Flickr are stopping login via anything other than a yahoo account this is now moot and perhaps the bug can be closed? Cheers, Mark On 4 Aug 2013 17:35, Leonardo Donelli leart...@gmail.com wrote: I have the same problem. Note: in the past there was a workaround for this, see lp:1041744, now there is not even that. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1173679 Title: Login to Flickr using Google ID Status in “account-plugins” package in Ubuntu: Confirmed Bug description: I login to Flickr via my Google account. When I try to connect through the online accounts the only option I have is to use a Yahoo! ID, which I don't have. The login should allow all valid Flickr sign in methods. (Ubuntu 13.04 64bit, Friends version 0.1.3daily13.04.17.1~13.04-0ubuntu1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1173679/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173679 Title: Login to Flickr using Google ID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1173679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303276] [NEW] gpgv crashed with SIGSEGV in __GI___libc_malloc()
Public bug reported: The computer was idling and the screen was off - I had perhaps been away for 20 to 30 minutes. On unlock of the screen I saw the error message (probably not as a result of unlocking the screen). Only thing running was Chrome. I had also just updated the latest patches etc for the 64bit 14.04 release. Perhaps this is relevant. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gpgv 1.4.16-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Sun Apr 6 08:55:59 2014 ExecutablePath: /usr/bin/gpgv InstallationDate: Installed on 2013-06-30 (279 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: /usr/bin/gpgv --ignore-time-conflict --status-fd 3 --keyring /etc/apt/trusted.gpg.d/steam.gpg --keyring /etc/apt/trusted.gpg.d/tiheum-equinox.gpg --keyring /etc/apt/trusted.gpg.d/shimmerproject-ppa.gpg --keyring /etc/apt/trusted.gpg.d/numix-ppa.gpg --keyring /etc/apt/trusted.gpg.d/satyajit-happy-themes.gpg --keyring /etc/apt/trusted.gpg.d/minecraft-installer-peeps-minecraft-installer.gpg --keyring /etc/apt/trusted.gpg.d/webupd8team-y-ppa-manager.gpg --keyring /etc/apt/trusted.gpg /var/lib/apt/lists/partial/ppa.launchpad.net_numix_ppa_ubuntu_dists_trusty_Release.gpg /var/lib/apt/lists/ppa.launchpad.net_numix_ppa_ubuntu_dists_trusty_Release ProcEnviron: LANG= PATH=(custom, no user) LC_MESSAGES= SegvAnalysis: Segfault happened at: 0x7fd06db035b3 __GI___libc_malloc+35: mov %fs:(%rax),%rbx PC (0x7fd06db035b3) ok source %fs:(%rax) (0xffc0) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnupg StacktraceTop: __GI___libc_malloc (bytes=1024) at malloc.c:2885 ?? () ?? () ?? () ?? () Title: gpgv crashed with SIGSEGV in __GI___libc_malloc() UpgradeStatus: Upgraded to trusty on 2014-03-15 (21 days ago) UserGroups: ** Affects: gnupg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303276 Title: gpgv crashed with SIGSEGV in __GI___libc_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1303276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303018] [NEW] file-roller crashed with SIGSEGV
*** This bug is a duplicate of bug 1299664 *** https://bugs.launchpad.net/bugs/1299664 Public bug reported: Opened a zip file contained a number of folders (with .fla and .mp3 files in it if that is relevant). Dragged the top level folder to my Music folder. Crash occurred - the files were not extracted or copied. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: file-roller 3.10.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 5 12:01:12 2014 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2013-06-30 (278 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: file-roller /home/username/Music/Pixies/EP3\ Digital\ Download.zip ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x44e690:movzbl (%rdx),%ecx PC (0x0044e690) ok source (%rdx) (0x) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: file-roller crashed with SIGSEGV UpgradeStatus: Upgraded to trusty on 2014-03-15 (20 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303018 Title: file-roller crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1303018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300392] [NEW] shotwell crashed with SIGABRT
Public bug reported: Viewing an event containing multiple pictures. Clicked on the left arrow to go to the previous picture when the app stopped responding (window went grey) and the crash occurred. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: shotwell 0.18.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Mar 31 18:50:57 2014 Disassembly: = 0x7f766ef70f79: Cannot access memory at address 0x7f766ef70f79 ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2013-06-30 (274 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: shotwell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: shotwell StacktraceTop: ?? () ?? () ?? () Title: shotwell crashed with SIGABRT UpgradeStatus: Upgraded to trusty on 2014-03-15 (16 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300392 Title: shotwell crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1300392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292936] [NEW] shotwell crashed with SIGABRT
Public bug reported: After update to Ubuntu 14.04 latest alpha (all packages up to date as at 15/3/2014) I opened the application. SHotwell launched and then went into the auto import (I had 9 new images in my library to import). The screen then went grey and the application stopped responding, although I could see the imported images in the greyed out window so they imported OK. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: shotwell 0.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 15 17:41:55 2014 Disassembly: = 0x7fea9bbcbf79: Cannot access memory at address 0x7fea9bbcbf79 ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2013-06-30 (258 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: shotwell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: shotwell StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: shotwell crashed with SIGABRT UpgradeStatus: Upgraded to trusty on 2014-03-15 (0 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292936 Title: shotwell crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1292936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236077] Re: shotwell crashed with SIGABRT
It happens often enough that I thought it worthwhile to report as a bug, but I can't reproduce it easily. I have an old Canon DLSR and the transfer speed via USB was terrible so I now do the transfer by taking the card out and putting it in a reader. What I have found is that often, but not predictably, Shotwell will stop responding whilst displaying the thumbnails - some times it will crash, some times it will recover and continue - and in other cases there is no issue (e.g. after restarting once crashed). This is all with the same card. Typically I transfer once I have more than 50 pictures on the card. I use a cheap generic USB2.0 card reader. I don't know why there's no stack trace. Let me know if there's anything else I can do to help. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236077 Title: shotwell crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1236077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239060] Re: Unity launcher does not remember icons position
To add a little to this. For those launchers that were present before update to 13.10, they remain in the same position. For those launchers added after update, they return to the bottom. For example I installed Fotoxx and it placed a launcher just above the workpalce chooser. I move it to be directly below the lens launcher and on next login it is back in the position just above the workplace chooser. There appear to be no errors reported (I can't see anything via dmesg or in the logs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239060 Title: Unity launcher does not remember icons position To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238960] [NEW] friends-dispatcher crashed with SIGSEGV in PyFrame_New()
Public bug reported: Opened the dash and clicked upon the social lens. A recent mention from Twitter appeared as a notification and then Apport told me about the crash. Sorry I don't have more information, but that's all I did! Ubuntu 13.10 final beta (+patches to 10/10/2013) 64 bit apt-cache policy friends-dispatcher: friends-dispatcher: Installed: 0.2.0+13.10.20130926-0ubuntu1 Candidate: 0.2.0+13.10.20130926-0ubuntu1 Version table: *** 0.2.0+13.10.20130926-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: friends-dispatcher 0.2.0+13.10.20130926-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 11 21:39:34 2013 Disassembly: = 0x7f528ef5404b: Cannot access memory at address 0x7f528ef5404b ExecutablePath: /usr/bin/friends-dispatcher InstallationDate: Installed on 2013-06-30 (103 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/friends-dispatcher -o ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f528ef5404b: Cannot access memory at address 0x7f528ef5404b PC (0x7f528ef5404b) ok SP (0x7a240590) ok Reason could not be automatically determined. Signal: 11 SourcePackage: friends StacktraceTop: ?? () ?? () ?? () ?? () PyFrame_New () Title: friends-dispatcher crashed with SIGSEGV in PyFrame_New() UpgradeStatus: Upgraded to saucy on 2013-09-29 (12 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers ** Affects: friends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash apport-failed-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1238960 Title: friends-dispatcher crashed with SIGSEGV in PyFrame_New() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1238960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236077] [NEW] shotwell crashed with SIGABRT
Public bug reported: Importing pictures from a 4GB Compact Flash card plugged in via a USB card reader. After displaying about a third of the pictures the app stopped responding and the crash occurred. Ubuntu 13.10 beta (patched to 6/10/2013), 64 bit. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: shotwell 0.15.0~pr3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sun Oct 6 16:52:14 2013 Disassembly: = 0x7fc69ab75f77: Cannot access memory at address 0x7fc69ab75f77 ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2013-06-30 (98 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: shotwell file:///media/username/753C-3741 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: shotwell StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: shotwell crashed with SIGABRT UpgradeStatus: Upgraded to saucy on 2013-09-29 (7 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236077 Title: shotwell crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1236077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177047] Re: friends-dispatcher crashed with TypeError in /usr/lib/python3/dist-packages/friends/main.py: threads_init() takes 0 positional arguments but 1 was given
Martin, yes, I had just updated to Saucy. This error occurred after re- boot, so I would have expected it to have all the saucy packages installed? In my message (#21) it states saucy as the package repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177047 Title: friends-dispatcher crashed with TypeError in /usr/lib/python3/dist- packages/friends/main.py: threads_init() takes 0 positional arguments but 1 was given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1177047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177047] Re: friends-dispatcher crashed with TypeError in /usr/lib/python3/dist-packages/friends/main.py: threads_init() takes 0 positional arguments but 1 was given
Seems to be. I haven't had the error since so I guess there's something awry on initial run that sorts itself out. I confirm when I looked in the file you linked to and there's no reference to threads_init. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177047 Title: friends-dispatcher crashed with TypeError in /usr/lib/python3/dist- packages/friends/main.py: threads_init() takes 0 positional arguments but 1 was given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1177047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203534] Re: update-manager crashes when trying to upgrade to 13.10
Just to add to this, I also get a message in the terminal that says Real-time signal 0. Note also that after 3 attempts to do this, it got a little further and then crashed again. The terminal output is: Checking for a new Ubuntu release WARNING:root:fetch result != continue (2) Traceback (most recent call last): File /usr/bin/do-release-upgrade, line 152, in module fetcher.run() File /usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py, line 278, in run _(Fetching the upgrade failed. There may be a network File /usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py, line 50, in error return error(self.window_main.window_main, summary, message) AttributeError: 'NoneType' object has no attribute 'window_main' Also I sent an apport error, but it didn't offer to show raise a bug, Note sure if this is wholly related to this bug, but I am posting here for those more knowledgeable to advise! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203534 Title: update-manager crashes when trying to upgrade to 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1203534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232711] [NEW] fc-cache crashed with SIGSEGV in IA__FcStrCmp()
Public bug reported: This error occurred during the upgrade to Ubuntu 13.10 final beta from a fully patched 13.04 ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: fontconfig 2.10.93-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sun Sep 29 11:33:18 2013 ExecutablePath: /usr/bin/fc-cache InstallationDate: Installed on 2013-06-30 (90 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: fc-cache -s -f -v SegvAnalysis: Segfault happened at: 0x7fca2c41ad04 FcStrSetMember+52: movzbl -0x1(%rax),%ecx PC (0x7fca2c41ad04) ok source -0x1(%rax) (0x0021) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: fontconfig StacktraceTop: FcStrSetMember () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 FcStrSetAdd () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 Title: fc-cache crashed with SIGSEGV in FcStrSetMember() UpgradeStatus: Upgraded to saucy on 2013-09-29 (0 days ago) UserGroups: ** Affects: fontconfig (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232711 Title: fc-cache crashed with SIGSEGV in IA__FcStrCmp() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1232711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232711] Re: fc-cache crashed with SIGSEGV in IA__FcStrCmp()
After looking at /var/log/fontconfig.log I see the last entry is /usr/share/fonts/truetype/google-fonts: Segmentation fault (core dumped) Removing this folder then lets fontconfig complete. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232711 Title: fc-cache crashed with SIGSEGV in IA__FcStrCmp() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1232711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177047] Re: friends-dispatcher crashed with TypeError in /usr/lib/python3/dist-packages/friends/main.py: threads_init() takes 0 positional arguments but 1 was given
I got redirected here too. Here's the info you requested. friends: Installed: 0.2.0+13.10.20130926-0ubuntu1 Candidate: 0.2.0+13.10.20130926-0ubuntu1 Version table: *** 0.2.0+13.10.20130926-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ saucy/main 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/1177047 Title: friends-dispatcher crashed with TypeError in /usr/lib/python3/dist- packages/friends/main.py: threads_init() takes 0 positional arguments but 1 was given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1177047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173679] [NEW] Login to Flickr using Google ID
Public bug reported: I login to Flickr via my Google account. When I try to connect through the online accounts the only option I have is to use a Yahoo! ID, which I don't have. The login should allow all valid Flickr sign in methods. (Ubuntu 13.04 64bit, Friends version 0.1.3daily13.04.17.1~13.04-0ubuntu1) ** Affects: account-plugins (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/1173679 Title: Login to Flickr using Google ID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1173679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067876] Re: Missing Safely Remove Drive option from Quicklists. Only have Eject.
Norbert, I have 13.04 beta running (64bit) and I only have the option to eject, not safely remove. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067876 Title: Missing Safely Remove Drive option from Quicklists. Only have Eject. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1067876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1106283] Re: [13.04]nautilus crashed with SIGABRT in g_assertion_message() when trying to open file/folder's property dialog as root where file/folder belongs to user with Unicode CJK name.
I had a similar problem too. I was trying to browse to another users
home folder to check disk usage. I launched a root nautilus through gksu
nautilus. When I right clicked on the folder (in this case 'pictures')
and selected properties I got the crash. Aport pointed me to this bug
rather than reporting a new one, so I'm adding a little bit more
information.
Firstly, the user in question is just a simple ASCII name ('betty')
rather than from the extended character set (but, of course, it may not
matter which part of the character set the characters come from). The
dialogue as reported in the original bug appeared, but I wasn't trying
to change the user and as I was running from a terminal it reported the
following:
ERROR:nautilus-properties-window.c:1836:schedule_owner_change_timeout:
assertion failed: (NAUTILUS_IS_FILE (file))
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1106283
Title:
[13.04]nautilus crashed with SIGABRT in g_assertion_message() when
trying to open file/folder's property dialog as root where file/folder
belongs to user with Unicode CJK name.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1106283/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1161916] Re: compiz crashed with SIGSEGV in sigc::internal::slot_call0unity::launcher::VolumeImp::Impl::Impl()
For me this happened when I safely removed a USB memory stick - much like Abhisek -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1161916 Title: compiz crashed with SIGSEGV in sigc::internal::slot_call0unity::launcher::VolumeImp::Impl::Impl() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1161916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016294] Re: ia32-libs-multiarch but it is not installable
I had the same issue when I was trying to install Crossover. I resolved this by changing the download server to main server within Software Sources (it was set to UK), I then ran synaptic and installed all the upgradeable packages (of which there were many but my system claimed it was up to date before I changed). Finally I ran sudo apt-get -f install which then picked up ia32-libs-multiarch and the other dependencies. So I guess that the change in download server caused the reload of the package lists helped resolve this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016294 Title: ia32-libs-multiarch but it is not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/1016294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058769] Re: In 12.10 beta2, VirtualBox has no access to network
Thanks for the suggestion. In fact I did what Scelt suggested and it works now. But at least I have another solution now too! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058769 Title: In 12.10 beta2, VirtualBox has no access to network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1058769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058769] Re: In 12.10 beta2, VirtualBox has no access to network
I can confirm the bug exists in 12.10 release (64 bit) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058769 Title: In 12.10 beta2, VirtualBox has no access to network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1058769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871777] Re: (oneiric) missing scrollbars
The latest version (3.2.1 received tonight) seems to have resolved this problem for me - Gwibber now can scroll! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871777 Title: (oneiric) missing scrollbars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/871777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 884214] Re: libreoffice is not updating
The latest update seems to have resolved this for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884214 Title: libreoffice is not updating To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/884214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871777] Re: (oneiric) missing scrollbars
Yes. I have the same problem. All other applications with overlay and/or scroll wheel work as I would expect. This is on 11.10 64bit (up to date) with Unity desktop. With Gwibber, I see the top two messages and that's it - even though I am told I have more messages. Resizing the window has done nothing. Running in a terminal gives: gwibber-preferences:31950): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion `!g_slist_find (group, radio_button)' failed gwibber (gwibber:32445): GLib-GObject-WARNING **: g_object_set_property: object class `GwibberAccount' has no property named `uid' ** (gwibber:32445): DEBUG: streams.vala:196: Getting non-transient model ** (gwibber:32445): DEBUG: streams.vala:198: stream_model from resources has 0 rows ** (gwibber:32445): DEBUG: streams.vala:205: COLS: 35 (gwibber:32445): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion `!g_slist_find (group, radio_button)' failed (gwibber:32445): GLib-GObject-WARNING **: g_object_set_valist: object class `TabWidgetsButton' has no property named `draw-indicator' (gwibber:32445): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed (gwibber:32445): GLib-GObject-WARNING **: g_object_set_property: object class `GwibberAccount' has no property named `uid' ** (gwibber:32445): DEBUG: tab-bar-widgets.vala:303: facebook not supported (gwibber:32445): GLib-GObject-WARNING **: g_object_set_property: object class `GwibberAccount' has no property named `uid' ** (gwibber:32445): DEBUG: streams.vala:263: refresh_model ** (gwibber:32445): DEBUG: streams.vala:277: Storing gwibber.stream_model ** (gwibber:32445): DEBUG: streams.vala:279: stream_model has 18 rows -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871777 Title: (oneiric) missing scrollbars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/871777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 636586] Re: dpkg complains about non-existing lines in /var/lib/dpkg/ files
$ sudo dpkg --clear-avail removed most of the warnings that I had however... $ dpkg -l /dev/null warning, in file '/var/lib/dpkg/status' near line 13284 package 'virtualbox': error in Version string '1.6.6-35336_Ubuntu_hardy': invalid character in revision number and so I try the tip above sudo apt-get purge virtualbox and I get a whole bunch of new errors because /etc/init.d/vboxdrv exists during rc.d purge grep -A8 virtualbox /var/lib/dpkg/status shows that virtualbox-3.2 replaces:virtualbox, provides: virtualbox and conflicts:virtualbox -- dpkg complains about non-existing lines in /var/lib/dpkg/ files https://bugs.launchpad.net/bugs/636586 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
