[Bug 1429524] Re: nautilus crashed with SIGSEGV in g_slice_free1()
*** This bug is a duplicate of bug 1424818 *** https://bugs.launchpad.net/bugs/1424818 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1424818, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429524/+attachment/4337632/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1429524/+attachment/4337634/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1429524/+attachment/4337636/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1429524/+attachment/4337637/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1429524/+attachment/4337638/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1429524/+attachment/4337639/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429524/+attachment/4337640/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1424818 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1429524 Title: nautilus crashed with SIGSEGV in g_slice_free1() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1429524/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1093185] Re: Nautilus browse network broken pipe on AFP after suspend
Same problem here 14.04 synology DS214 -- 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/1093185 Title: Nautilus browse network broken pipe on AFP after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1093185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1429354] [NEW] Systemd takes very long to boot with error in swap mounting and nvidia persistenced
Public bug reported: My system boots almost instantly with upstart. Today i tried booting with systemd via the additional grub option. However, with systemd it takes really long to boot but – so long that i forced a reboot once because i thought i got stuck. Looking in to boot journal, i found the following error concerning the swap: Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, code=exited status=255 Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition. Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state. And this concerning nvidia-persistenced Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433) Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 116 has read and write permissions for thos Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced I checked that /dev/sda3 exists and is a swap partition and i check for the /dev/nvidia files: $ ls -Alst /dev/nvidia0 0 crw-rw-rw- 1 root root 195, 0 Mär 7 09:29 /dev/nvidia0 However, the interesting part is here, where nothing seems to happen for a minute: (see the timestamps): Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization. Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 messages. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start timed out. Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 messages. Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for /dev/mapper/cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap. Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes. Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start failed with result 'timeout'. Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 09:31:09 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-05 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 init=/lib/systemd/systemd systemd.debugshell SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H97 Performance dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429354 Title: Systemd takes very long to boot with error in swap mounting and nvidia persistenced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429354/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com
[Bug 1429391] [NEW] Rhythmbox crash when jumping to playing song
Public bug reported: Hello, Using Rhythmbox 3.0.2 on Ubuntu 14.04, when I use ctrl+j (or menu option jump to playing song), rhythmbox crashes with this error: Rhythmbox:ERROR:rb-display-page-tree.c:497:rb_display_page_tree_select: assertion failed: (rb_display_page_model_find_page (display_page_tree-priv-page_model, page, iter)) Unable to open ~/.mtpz-data for reading, MTPZ disabled.Abandon (core dumped) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1429391 Title: Rhythmbox crash when jumping to playing song To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1429391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1429279] Re: Evince -pdf close only using Force Quit
stop sending me emails On Sat, Mar 7, 2015 at 10:36 AM, Monsta 1429...@bugs.launchpad.net wrote: ** Project changed: linuxmint = evince (Ubuntu) ** Tags added: trusty -- You received this bug notification because you are subscribed to Linux Mint. Matching subscriptions: Raven https://bugs.launchpad.net/bugs/1429279 Title: Evince -pdf close only using Force Quit Status in evince package in Ubuntu: New Bug description: When using Evince to view PDFs it is working but closing PDFs causes Force Quit window to appear. Worked properly with 14.04.1 Problem always happens closing PDFs Using Ubuntu 14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1429279/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1429279 Title: Evince -pdf close only using Force Quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1429279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1429391] Re: Rhythmbox crash when jumping to playing song
Your bug is actually this one: https://bugzilla.gnome.org/show_bug.cgi?id=729373 This has been fixed in Rhythmbox 3.1. The commit can be directly applied to 3.0.2 - thus you could submit the patch ... or upgrade to RB 3.1 ** Bug watch added: GNOME Bug Tracker #729373 https://bugzilla.gnome.org/show_bug.cgi?id=729373 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1429391 Title: Rhythmbox crash when jumping to playing song To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1429391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1425350] Re: Ubuntu GNOME Vivid - password won't unlock screen
If you are still experiencing this bug, please set status back to confirmed. ** Changed in: gnome-session (Ubuntu) Status: Confirmed = Fix Released ** Changed in: ubuntu-gnome Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1425350 Title: Ubuntu GNOME Vivid - password won't unlock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1425350/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1425779] Re: Ubuntu GNOME Vivid logs out to a blank screen
If you are still experiencing this bug, please set status back to confirmed. ** Changed in: gdm (Ubuntu) Importance: Undecided = Critical ** Changed in: gdm (Ubuntu) Status: New = Fix Released ** Changed in: ubuntu-gnome Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1425779 Title: Ubuntu GNOME Vivid logs out to a blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1425779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
This can be EASILY RECREATED with the Super Start 7.3.3 extension in Firefox. Just right click on any tab to add to Super Start, click Add this tab to Super Start and the problem will occur in 12.04 as well as 14.04. In 14.04 the processor saturates 100%. In 12.04 the processor doesn't sat 100% but there is some kinda infinite disk activity. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1214352] Re: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in Trusty Tahr, Utopic Unicorn, and the development release, Vivid Vervet. If upgrading is an option, please know that upgrading to Trusty (Ubuntu 14.04 - also an LTS) will fix this issue for you. The fix for this bug appears to have been released in GLib 2.35.9, according to this: http://upstream.rosalinux.ru/changelogs/glib/2.40.0/changelog.html - Newer versions of glib are available in official repositories of Trusty, Utopic, and Vivid. If you would like to request a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. Please be advised, it may not be possible to push an update a component like this due to regression potential. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure The Stable Release Update Procedure is the proper method to bring these requests to developers. Please refrain from posting complaints that bugs are not fixed to the developer mailing lists. Please read our suggested bug reporting etiquette [2]. [2]: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette ** Changed in: glib2.0 (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
** Summary changed: - GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses + [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses ** Description changed: + [Impact] + * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). + * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. + + [Test Case] + 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. + 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. + 2a.2. Double click on 'test.odt' + 3. Get error message from LibreOffice: + The file 'test.odt' is corrupt and therefore cannot be opened. + LibreOffice can try to repair the file. + + The corruption could be the result of document manipulation or of + structural document damage due to data transmission. + We recommend that you do not trust the content of the repaired document. + Execution of macros is disabled for this document. + + Should LibreOffice repair the file? + + Yes No + 4a. If I click 'Yes', the file is opened, but the title of the document + is Untitled 1 (repaired document), not original name. + 4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text: + The file 'test.odt' could not be repaired and therefore cannot be opened. + OK + + I click 'OK' here, the next window LibreOffice 4.4.1.2 is opened with text: + General Error. + General input/output error. + + OK + + If I click OK here - no files are opened. + + While step 3 gvfsd-smb process eats CPU then terminates with error. This + error is caused by bug in Glib (wrong type conversion in macros). + + [Regression Potential] + + * This functionality is essential. Please fix this bug. + I (and you) can't tell Windows users, that they should not open office files from network shares in GNU/Linux. + + * The patch has two lines + (https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4) + and well-tested at upstream. + + * This bug may cause potential loss of data. + + [Other Info] + + * Corresponding links to LibO bugs are: +https://bugs.freedesktop.org/show_bug.cgi?id=67527 +https://bugs.documentfoundation.org/show_bug.cgi?id=72337 + + + [Original description] On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details ** Description changed: - [Impact] - * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). + [Impact] + * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. [Test Case] - 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. - 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. - 2a.2. Double click on 'test.odt' - 3. Get error message from LibreOffice: - The file 'test.odt' is corrupt and therefore cannot be opened. - LibreOffice can try to repair the file. - - The corruption could be the result of document manipulation or of - structural document damage due to data transmission. - We recommend that you do not trust the content of the repaired document. - Execution of macros is disabled for this document. + 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. + 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. + 2a.2. Double click on 'test.odt' + 2b. Launch terminal and send 'libreoffice smb://server_name/share_name/test.odt' command. + 3. Get error message from LibreOffice: + The file 'test.odt' is corrupt and therefore cannot be opened. + LibreOffice can try to repair the file. - Should LibreOffice repair the file? + The corruption could be the result of document
[Bug 1429279] Re: Evince -pdf close only using Force Quit
** Project changed: linuxmint = evince (Ubuntu) ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1429279 Title: Evince -pdf close only using Force Quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1429279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1429279] [NEW] Evince -pdf close only using Force Quit
You have been subscribed to a public bug: When using Evince to view PDFs it is working but closing PDFs causes Force Quit window to appear. Worked properly with 14.04.1 Problem always happens closing PDFs Using Ubuntu 14.04.2 ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- Evince -pdf close only using Force Quit https://bugs.launchpad.net/bugs/1429279 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1425879] Re: elitebook 840G1 restarts when he is told to shut down
** Changed in: evince (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1425879 Title: elitebook 840G1 restarts when he is told to shut down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1425879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1406239] Re: Evince PDF print generates blank pages on the printer.
*** This bug is a duplicate of bug 1397516 *** https://bugs.launchpad.net/bugs/1397516 ** This bug has been marked a duplicate of bug 1397516 Evince prints blank pages with attached PDF -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1406239 Title: Evince PDF print generates blank pages on the printer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1406239/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1415320] Re: gedit acts like it has some internal runaway code active while a cut-buffer is active
** Package changed: evince (Ubuntu) = gedit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1415320 Title: gedit acts like it has some internal runaway code active while a cut- buffer is active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1415320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1419856] Re: Long Delay When Pressing Volume Up/Down Keys
It happens to me as well. When i open system setting on ubuntu(14.10), it starts to work again. But it is really annoying. Hope it is fixed soon. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1419856 Title: Long Delay When Pressing Volume Up/Down Keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1419856/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201393] Re: gvfsd-trash crashed with SIGSEGV in g_slice_alloc()
It is in vivid development branch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/201393 Title: gvfsd-trash crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/201393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212601] Re: nautilus crashed with SIGSEGV in discovered_cb()
** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1212601 Title: nautilus crashed with SIGSEGV in discovered_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1212601/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1429462] Re: nautilus crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1212601 *** https://bugs.launchpad.net/bugs/1212601 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1212601, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429462/+attachment/4337491/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1429462/+attachment/4337493/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1429462/+attachment/4337494/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1429462/+attachment/4337495/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1429462/+attachment/4337496/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1429462/+attachment/4337497/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429462/+attachment/4337498/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1212601 nautilus crashed with SIGSEGV in discovered_cb() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1429462 Title: nautilus crashed with SIGSEGV in ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1429462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
If Firefox is launched gksudo firefox in a terminal (superuser) Super Start has no problem with gvsfd-metadata in 12.04 or 14.04. There is apparently a privilege issue with this system call. This should be enough information to make considerable progress with this long standing bug. Unless the problem is INHERENT in the design. of course. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Can somebody escalate the priority? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
See the remote bug watches on the right here. It links to gnome-bugs #637095 https://bugzilla.gnome.org/show_bug.cgi?id=637095 , which is FIXED. Given that this bug can trash SSDs on hardware level, by making so many writes that the lifespan is considerably reduced, by doing billions of write calls in a matter of hours, I'm asking for a hotfix in Ubuntu 12.04 precise. Given that SSDs are silent, a user wouldn't even notice this unless he has a CPU or disk meter or similar showing. I do, but I still missed this once and it ran for 10 hours overnight IIRC. How can we escalate this for a hotfix in a stable distro? I don't know launchpad well enough. Could somebody please make some noise? There's already a straight-forward fix, and commited to the GNOME repo, it's just a matter of shipping it for the stable Ubuntu distros. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
Also affected. In my case, a Samsung Galaxy S SCL GT-I9003 Ubuntu 14.04 ships libmtp 1.1.6. I wonder if a higher, or lower version of this lib, would fix these problems? (I said lower in my previous sentence, because many people claim here that it worked with Ubuntu 12.04.) Apparently Ubuntu 12.04 included libmtp-1.1.3-1, and Ubuntu 15.04 includes latest libmtp, which is 1.1.8. Has anyone of you tried to run Ubuntu 15.04? Or downgrade your libmtp to 1.1.3 in your 14.04? For the record, my mtp-detect log: $ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. -- 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/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
So I've found a workaround. In a terminal, do: $ killall gvfs-gphoto2-volume-monitor $ killall gvfs-mtp-volume-monitor Then reconnect your device. Now mtp-detect works, and other players that use libmtp. -- 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/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Can somebody confirm the Super Start recreation? The more the merrier! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1429497] Re: evolution-source-registry crashed with signal 5 in g_main_context_new()
*** This bug is a duplicate of bug 1379354 *** https://bugs.launchpad.net/bugs/1379354 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1379354, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429497/+attachment/4337560/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1429497/+attachment/4337562/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1429497/+attachment/4337564/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1429497/+attachment/4337565/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1429497/+attachment/4337566/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1429497/+attachment/4337567/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429497/+attachment/4337568/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1379354 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1429497 Title: evolution-source-registry crashed with signal 5 in g_main_context_new() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1429497/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
Interestingly enough, I removed all my mtp packages, and installed libmtp-code from the git's source (tried both 1.1.8 and 1.1.6) and it made suddenly mtp-detect to start working (in both versions). So I'm wondering what to do next, to keep on pinpointing the problem. -- 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/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
I would like to add that I don't think that the original bug reported with this bug report, is identical with the way this gvfs-metadata bug behaves in its later version as running rm -rf ~/.local/share/gvfs- metadata stops the infinite disk writing for just few minutes and that it starts again. Not only does it put the HDD under a strain (especially SSDs), it also kills the battery on laptop devices quicker especially when an ordinary HDD is used. The finding that the bug is easily reproducible with the Super Start firefox extension is interesting. I'm using a similar extension on both my machines where this bug appears; it's Speed DIal [FWD] in my case. Some previous bug reports mention that the bug is triggered when using HTML5 Video Everywhere - another firefox plugin. Is it possible that some of the libraries used by firefox produce files (or do something else) that than somehow confuse gvfs-metadata and force it to go into infinite writing loop?! If so, can this be also a firefox bug? Not that gvfs-metadata shouldn't be able to handle such situations. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Also, I don;t think that the current incarnation of this bug is filling my HDD. When I open the ~/.local/share/gvfs-metadata folder in the file browser it is evident that a few files are constantly being generated and then erased ad nauseam. So there is no disk space eating problem, just the HDD (and laptop battery) straining problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Philip, the reproduction using Firefox has been investigated and confirmed to be a gvfs bug (not Firefox bug), and has already been FIXED (!) in the GNOME bug that I've been linking above. This is just Ubuntu being inactive in shipping the fix. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
This has gotta be rampant in the world if it's happening in Firefox in any number of ways! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Description changed: Binary package hint: gvfs My disk space was really full at one moment, no byte left free. People say, that does corrupt the files in the ~/.local/share/gvfs-metadata folder, so the gvfsd-metadata can't read it without being screwed up. Workaround: run rm -rf ~/.local/share/gvfs-metadata Expected results: gvfsd-metadata should be able to handle the no space left situation. - --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Description changed: Binary package hint: gvfs - My disk space was really full at one moment, no byte left free. People say, that does corrupt the files in the ~/.local/share/gvfs-metadata folder, so the gvfsd-metadata can't read it without being screwed up. - Workaround: run rm -rf ~/.local/share/gvfs-metadata + Failure to write metadata results in an infinite loop that keeps trying + to write, thousands of times per second. - Expected results: - gvfsd-metadata should be able to handle the no space left situation. + Steps to reproduce: + 1. Open Firefox + 2. Save a data: URL (very long URL, usually generated by webapps or extensions) as file + + Actual result: + - File is saved + - 100% CPU + - Extremely high number of file operations by gvfs - billions + - Never stops + + Expected result: + Failure to write metadata should just fail, not try again + + Fix: + Patch available and accepted by GNOME + https://bugzilla.gnome.org/show_bug.cgi?id=637095 + --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. ** Description changed: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox - 2. Save a data: URL (very long URL, usually generated by webapps or extensions) as file + 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file + + (There are other ways to run into this problem, e.g. disk full or other + error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 - --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
