[Bug 987028] Re: cant boot.says stoping crash report generation failed
** Changed in: nautilus (Ubuntu) Status: New = Fix Released -- 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/987028 Title: cant boot.says stoping crash report generation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/987028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1210938] Re: No window decoration on GNOME Fallback
Show here: ~$ compiz --replace compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Info: Starting plugin: ccp compizconfig - Info: Backend : gsettings compizconfig - Info: Integration : true compizconfig - Info: Profile : unity compiz (core) - Info: Loading plugin: composite compiz (core) - Info: Starting plugin: composite compiz (core) - Info: Loading plugin: opengl compiz (core) - Info: Unity is fully supported by your hardware. compiz (core) - Info: Unity is fully supported by your hardware. compiz (core) - Info: Starting plugin: opengl OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table OpenGL Warning: glVertexArrayRangeNV not found in mesa table OpenGL Warning: glCombinerInputNV not found in mesa table OpenGL Warning: glCombinerOutputNV not found in mesa table OpenGL Warning: glCombinerParameterfNV not found in mesa table OpenGL Warning: glCombinerParameterfvNV not found in mesa table OpenGL Warning: glCombinerParameteriNV not found in mesa table OpenGL Warning: glCombinerParameterivNV not found in mesa table OpenGL Warning: glFinalCombinerInputNV not found in mesa table OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table OpenGL Warning: glDeleteFencesNV not found in mesa table OpenGL Warning: glFinishFenceNV not found in mesa table OpenGL Warning: glGenFencesNV not found in mesa table OpenGL Warning: glGetFenceivNV not found in mesa table OpenGL Warning: glIsFenceNV not found in mesa table OpenGL Warning: glSetFenceNV not found in mesa table OpenGL Warning: glTestFenceNV not found in mesa table OpenGL Warning: No pincher, please call crStateSetCurrentPointers() in your SPU compiz (core) - Info: Loading plugin: imgjpeg compiz (core) - Info: Starting plugin: imgjpeg compiz (core) - Info: Loading plugin: compiztoolbox compiz (core) - Info: Starting plugin: compiztoolbox compiz (core) - Info: Loading plugin: decor compiz (core) - Info: Starting plugin: decor compiz (core) - Info: Loading plugin: gnomecompat compiz (core) - Info: Starting plugin: gnomecompat compiz (core) - Info: Loading plugin: copytex compiz (core) - Info: Starting plugin: copytex compiz (core) - Info: Loading plugin: move compiz (core) - Info: Starting plugin: move compiz (core) - Info: Loading plugin: mousepoll compiz (core) - Info: Starting plugin: mousepoll compiz (core) - Info: Loading plugin: text compiz (core) - Info: Starting plugin: text compiz (core) - Info: Loading plugin: place compiz (core) - Info: Starting plugin: place compiz (core) - Info: Loading plugin: vpswitch compiz (core) - Info: Starting plugin: vpswitch compiz (core) - Info: Loading plugin: imgpng compiz (core) - Info: Starting plugin: imgpng compiz (core) - Info: Loading plugin: imgsvg compiz (core) - Info: Starting plugin: imgsvg compiz (core) - Info: Loading plugin: regex compiz (core) - Info: Starting plugin: regex compiz (core) - Info: Loading plugin: animation compiz (core) - Info: Starting plugin: animation compiz (core) - Info: Loading plugin: grid compiz (core) - Info: Starting plugin: grid compiz (core) - Info: Loading plugin: resize compiz (core) - Info: Starting plugin: resize compiz (core) - Info: Loading plugin: wobbly compiz (core) - Info: Starting plugin: wobbly compiz (core) - Info: Loading plugin: session compiz (core) - Info: Starting plugin: session I/O warning : failed to load external entity /home/opa/.compiz/session/10a72398353bc280711376466860491750033570008 compiz (core) - Info: Loading plugin: workarounds compiz (core) - Info: Starting plugin: workarounds compiz (core) - Info: Loading plugin: kdecompat compiz (core) - Info: Starting plugin: kdecompat compiz (core) - Info: Loading plugin: fade compiz (core) - Info: Starting plugin: fade compiz (core) - Info: Loading plugin: cube compiz (core) - Info: Starting plugin: cube compiz (core) - Info: Loading plugin: td compiz (core) - Info: Starting plugin: td compiz (core) - Info: Loading plugin: rotate compiz (core) - Info: Starting plugin: rotate compiz (core) - Info: Loading plugin: unitymtgrabhandles compiz (core) - Info: Starting plugin: unitymtgrabhandles compiz (core) - Info: Loading plugin: expo compiz (core) - Info: Starting plugin: expo compiz (core) - Info: Loading plugin: scale compiz (core) - Info: Starting plugin: scale compiz (core) - Info: Loading plugin: ezoom compiz (core) - Info: Starting plugin: ezoom compiz (core) - Info: Loading plugin: unityshell compiz (core) - Info: Starting plugin: unityshell WARN 2013-08-14 09:56:17 unity.glib.dbus.server GLibDBusServer.cpp:580
[Bug 1211937] Re: Nautilus leaks memory right after system start
I had expected ubuntu-bug adds more detailed/valuable information about the bug. If there is more info needed, I could reproduce it and give what ever info requested. This was after a fresh install of Ubuntu, but with old user configuration imported. Turning of Nautilus to manage the desktop does indeed workaround the issue, although it shouldn't happen at all. In any case I see this not only as a problem in this nautilus build, but also in resource/RAM management in the OS: A process that requires more RAM than can be afforded to maintain the system's responsiveness should be halted or killed. -- 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/1211937 Title: Nautilus leaks memory right after system start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1211937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
Valgrind isn't showing anything particularly relevant. The uninitialised value error is present in all bzr revisions of whoopsie when using this version of libc (2.17-91ubuntu1 - probably earlier ones too as I just upgraded it). ** Attachment added: vgdump.txt https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1211417/+attachment/3772239/+files/vgdump.txt -- 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/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 351496] Re: totem-plugin-viewer crashed with SIGSEGV in mms_connect()
** Changed in: totem Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/351496 Title: totem-plugin-viewer crashed with SIGSEGV in mms_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/351496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 642792] Re: ALT+PrtSc not recognised: breaks built-in screenshot function
Alan Pope, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux replace-with-bug-number Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.11-rc5 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: kernel-unable-to-test-upstream kernel-unable-to-test-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/642792 Title: ALT+PrtSc not recognised: breaks built-in screenshot function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/642792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 642792] Re: ALT+PrtSc not recognised: breaks built-in screenshot function
Maverick EOL - Won't Fix. ** Changed in: linux (Ubuntu Maverick) Status: Confirmed = Invalid ** Tags added: bios-outdated-1903 needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/642792 Title: ALT+PrtSc not recognised: breaks built-in screenshot function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/642792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212221] [NEW] empathy crashed with SIGSEGV in ffi_call_unix64()
Public bug reported: I was double clicking a contact in the roster ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Wed Aug 14 13:56:27 2013 Disassembly: = 0x0001: Cannot access memory at address 0x0001 ExecutablePath: /usr/bin/empathy InstallationDate: Installed on 2013-06-18 (57 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: empathy SegvAnalysis: Segfault happened at: 0x0001: Cannot access memory at address 0x0001 PC (0x0001) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, args_list=optimized out, marshal_data=0x422310, n_params=2, param_types=0xed0f00) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1550 _g_closure_invoke_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, args=0x707b2f88, n_params=2, param_types=0xed0f00) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840 Title: empathy crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf ** Affects: empathy (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 empathy in Ubuntu. https://bugs.launchpad.net/bugs/1212221 Title: empathy crashed with SIGSEGV in ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1212221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212221] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1212221/+attachment/3772354/+files/StacktraceSource.txt -- 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/1212221 Title: empathy crashed with SIGSEGV in ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1212221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212221]
StacktraceTop: ?? () ffi_call_unix64 () at ../src/x86/unix64.S:76 ffi_call (cif=cif@entry=0x707b2c50, fn=fn@entry=0x422310 event_activated_cb, rvalue=0x707b2b80, avalue=avalue@entry=0x707b2b20) at ../src/x86/ffi64.c:522 g_cclosure_marshal_generic_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, args_list=optimized out, marshal_data=0x422310 event_activated_cb, n_params=2, param_types=0xed0f00) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1550 _g_closure_invoke_va (closure=0xf0ed40, return_value=0x0, instance=0xd6f010, args=0x707b2f88, n_params=2, param_types=0xed0f00) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840 -- 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/1212221 Title: empathy crashed with SIGSEGV in ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1212221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212221] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1212221/+attachment/3772355/+files/ThreadStacktrace.txt ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1212221/+attachment/3772344/+files/CoreDump.gz ** Changed in: empathy (Ubuntu) Importance: Undecided = Medium ** Tags removed: need-amd64-retrace -- 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/1212221 Title: empathy crashed with SIGSEGV in ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1212221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212221] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1212221/+attachment/3772353/+files/Stacktrace.txt -- 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/1212221 Title: empathy crashed with SIGSEGV in ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1212221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages
** Description changed: Binary package hint: nautilus What happens - I open the Personal file sharing preferences dialog via system-preferences or via nautilus, and Im told that the network sharing feature can not be enabled because the required packages are not on your pc. I, as a tech user, went to synaptic, found the package, looked for its recommends and got the functionality. A normal user wont be able to do so, and so a button to install those packages is needed for usabilty's sake. -- Desired resolution: - Remove the Sharing Options right click menu option from Nautilus. + - Remove the 'Share' tab from the Nautilus 'Properties' window - If a advanced user chooses to install the required packages, the menu should re-appear in Nautilus. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/536766 Title: Personal file sharing preferences dialog does not offer to install needed packages To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/536766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212270] [NEW] freeze
Public bug reported: zzz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution 3.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 14 16:08:54 2013 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug saucy ** Changed in: evolution (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1212270 Title: freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1212270/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212269] Re: nautilus crashed with SIGSEGV in gtk_action_get_name()
*** This bug is a duplicate of bug 1193522 *** https://bugs.launchpad.net/bugs/1193522 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 #1193522, 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/1212269/+attachment/3772479/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1212269/+attachment/3772481/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1212269/+attachment/3772482/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1212269/+attachment/3772483/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1212269/+attachment/3772484/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1212269/+attachment/3772485/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1212269/+attachment/3772486/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1193522 nautilus crashed with SIGSEGV in gtk_action_get_name() ** 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/1212269 Title: nautilus crashed with SIGSEGV in gtk_action_get_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1212269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1083811] Re: Duplicated panels using separate x screens
Uploaded to precise-proposed. Please add the SRU information fields before it can be accepted: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. ** Also affects: gnome-panel (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1083811 Title: Duplicated panels using separate x screens To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1083811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 164120] Re: file manager hangs when mounted nfs drive is no longer accessible
** Changed in: thunar Importance: Low = Unknown ** Changed in: thunar Status: Invalid = Unknown ** Changed in: thunar Remote watch: None = Xfce Bugzilla #6185 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/164120 Title: file manager hangs when mounted nfs drive is no longer accessible To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/164120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212298] Re: file-roller crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 723841 *** https://bugs.launchpad.net/bugs/723841 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 #723841, 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/1212298/+attachment/3772550/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1212298/+attachment/3772552/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1212298/+attachment/3772554/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1212298/+attachment/3772555/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1212298/+attachment/3772556/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1212298/+attachment/3772557/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1212298/+attachment/3772558/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 723841 file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event() ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1212298 Title: file-roller crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1212298/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 164120] Re: file manager hangs when mounted nfs drive is no longer accessible
I see this issue in Thunar on Xubuntu 12.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/164120 Title: file manager hangs when mounted nfs drive is no longer accessible To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/164120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212320] [NEW] nautilus crashed with SIGSEGV in gtk_action_get_name()
*** This bug is a duplicate of bug 1193522 *** https://bugs.launchpad.net/bugs/1193522 Public bug reported: Just installed Dropbox and tried to open it's folder (/home/uzername/Dropbox/) ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 14 18:29:27 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2013-08-14 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130814) MarkForUpload: True ProcCmdline: nautilus --new-window SegvAnalysis: Segfault happened at: 0x7f0456e53dd6 gtk_action_get_name+22: cmp %rax,(%rdx) PC (0x7f0456e53dd6) ok source %rax ok destination (%rdx) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () ?? () ?? () Title: nautilus crashed with SIGSEGV in gtk_action_get_name() 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 saucy ** 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/1212320 Title: nautilus crashed with SIGSEGV in gtk_action_get_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1212320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212320] Re: nautilus crashed with SIGSEGV in gtk_action_get_name()
*** This bug is a duplicate of bug 1193522 *** https://bugs.launchpad.net/bugs/1193522 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 #1193522, 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/1212320/+attachment/3772594/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1212320/+attachment/3772596/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1212320/+attachment/3772598/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1212320/+attachment/3772599/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1212320/+attachment/3772600/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1212320/+attachment/3772601/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1212320/+attachment/3772602/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1193522 nautilus crashed with SIGSEGV in gtk_action_get_name() ** 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/1212320 Title: nautilus crashed with SIGSEGV in gtk_action_get_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1212320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212339] Re: nautilus crashed with SIGSEGV in gtk_action_get_name()
*** This bug is a duplicate of bug 1193522 *** https://bugs.launchpad.net/bugs/1193522 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 #1193522, 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/1212339/+attachment/3772685/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1212339/+attachment/3772687/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1212339/+attachment/3772688/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1212339/+attachment/3772689/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1212339/+attachment/3772690/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1212339/+attachment/3772691/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1212339/+attachment/3772692/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1193522 nautilus crashed with SIGSEGV in gtk_action_get_name() ** 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/1212339 Title: nautilus crashed with SIGSEGV in gtk_action_get_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1212339/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212340] Re: nautilus crashed with SIGSEGV in gtk_action_get_name()
*** This bug is a duplicate of bug 1193522 *** https://bugs.launchpad.net/bugs/1193522 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 #1193522, 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/1212340/+attachment/3772693/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1212340/+attachment/3772695/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1212340/+attachment/3772696/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1212340/+attachment/3772697/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1212340/+attachment/3772698/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1212340/+attachment/3772699/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1212340/+attachment/3772700/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1193522 nautilus crashed with SIGSEGV in gtk_action_get_name() ** 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/1212340 Title: nautilus crashed with SIGSEGV in gtk_action_get_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1212340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 998491] Re: window icon does not work with all dialogs
According to strace here, zenity --info --window-icon /usr/share/zenity/zenity.png makes a successful call to open() on the supplied filename (/usr/share/zenity/zenity.png), but then also calls open() on -- and displays -- the standard white i on a blue disc icon from /usr/share/icons/Humanity/status/48/dialog-information.svg. Changing the supplied filename to one more similar to the file displayed above, e.g. to /usr/share/icons/Humanity/status/48/dialog-error.svg, makes no difference to this behaviour. Ubuntu 12.04.2 LTS zenity 3.4.0-0ubuntu4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/998491 Title: window icon does not work with all dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/998491/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1211902] [NEW] Starting playing a song from recently does not work in Totem
You have been subscribed to a public bug: After starting Totem I wanted to play a song in the recently list but it did not start, Totem just froze. But when opening the same song directly from the place it is no problem at all. This happens frequently when I want to start from recently in Totem. Otherwise no single problem with it, every kind of format is played flawlessly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48 Uname: Linux 3.2.0-51-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moorgott 2081 F pulseaudio /dev/snd/controlC0: moorgott 2081 F pulseaudio /dev/snd/pcmC0D0p: moorgott 2081 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe520 irq 44' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,1458a002,0011' Controls : 46 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xe300 irq 17' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Tue Aug 13 19:36:10 2013 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Internes Audio - HDA Intel Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [EG41MF-US2H, Realtek ALC888, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: EG41MF-US2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd11/04/2009:svnGigabyteTechnologyCo.,Ltd.:pnEG41MF-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG41MF-US2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EG41MF-US2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- Starting playing a song from recently does not work in Totem https://bugs.launchpad.net/bugs/1211902 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 998491] Re: window icon does not work with all dialogs
Further to the above, this also fails when supplying one of the short arguments to --window-icon, as mentioned in the man page. For me, passing in a value from the list given (error, info, question, or warning) results in one of the files /usr/share/icons/Humanity/status/22/dialog-error.svg /usr/share/icons/Humanity/status/22/dialog-information.svg /usr/share/icons/Humanity/status/22/dialog-question.svg /usr/share/icons/Humanity/status/22/dialog-warning.svg being accessed with open(), but then following that the file /usr/share/icons/Humanity/status/48/dialog-information.svg is still loaded and displayed, as before. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/998491 Title: window icon does not work with all dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/998491/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153934] Re: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 or higher due a gvfs bug
** Changed in: gvfs Status: Incomplete = Confirmed -- 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/1153934 Title: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 or higher due a gvfs bug To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1153934/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1211902] Re: Starting playing a song from recently does not work in Totem
Yes of course, sorry, the Ubuntu crash report assigned it to alsa-driver and I did not check it before logging in here and letting Ubuntu post it. Did change that now. Thank you for the hint! ** Package changed: alsa-driver (Ubuntu) = totem (Ubuntu) -- 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/1211902 Title: Starting playing a song from recently does not work in Totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1211902/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 92661] Re: Make the toolbar/statusbar font smaller
** Changed in: gtk Status: New = Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/92661 Title: Make the toolbar/statusbar font smaller To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/92661/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1197271] Re: gdm-session-worker crashed with SIGSEGV in g_simple_async_result_complete()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm (Ubuntu) Status: New = Confirmed -- 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/1197271 Title: gdm-session-worker crashed with SIGSEGV in g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1197271/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212378] Re: RB crashes every time I try to play a song
** Changed in: rhythmbox (Ubuntu) Importance: Undecided = High ** Changed in: rhythmbox (Ubuntu) Assignee: (unassigned) = Sebastien Bacher (seb128) -- 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/1212378 Title: RB crashes every time I try to play a song To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1212378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212378] [NEW] RB crashes every time I try to play a song
Public bug reported: I'm not getting any apport of whoopsie dialogs, so not sure how to get the debug info for this. I just upgraded from Raring to Saucy today. Just synced all my music from U1. I can browse to music but rather than playing, RB crashes. I get a notification that the song is playing, but RB disappears. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 14 14:06:04 2013 InstallationDate: Installed on 2013-04-23 (112 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: Upgraded to saucy on 2013-08-14 (0 days ago) ** Affects: rhythmbox (Ubuntu) Importance: High Assignee: Sebastien Bacher (seb128) Status: New ** Tags: amd64 apport-bug saucy -- 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/1212378 Title: RB crashes every time I try to play a song To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1212378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 531692] Re: Support for Video Acceleration API (VA API) VaAPI
** Changed in: gstreamer Status: In Progress = Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/531692 Title: Support for Video Acceleration API (VA API) VaAPI To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/531692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1174576] Re: Totem does not save screenshot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: totem (Ubuntu) Status: New = Confirmed -- 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/1174576 Title: Totem does not save screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1174576/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212378] Re: RB crashes every time I try to play a song
** Attachment added: _usr_bin_rhythmbox.1000.crash https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1212378/+attachment/3772892/+files/_usr_bin_rhythmbox.1000.crash -- 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/1212378 Title: RB crashes every time I try to play a song To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1212378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212378] Re: RB crashes every time I try to play a song
rick@rick-K53SV:~$ rhythmbox (rhythmbox:15716): GStreamer-CRITICAL **: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_object_unref: assertion 'object != NULL' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_object_unref: assertion 'object != NULL' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_element_link_many: assertion 'GST_IS_ELEMENT (element_2)' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (rhythmbox:15716): GStreamer-CRITICAL **: gst_object_unref: assertion 'object != NULL' failed (rhythmbox:15716): GStreamer-CRITICAL **: Trying to dispose element autoaudiosink0, but it is in READY instead of the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. This problem may also be caused by a refcounting bug in the application or some element. ** (rhythmbox:15716): WARNING **: can't find typefind element, decodebin will not work Bus error (core dumped) -- 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/1212378 Title: RB crashes every time I try to play a song To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1212378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1192744] Re: Zoom Level using the key combination Ctrl++ does not appear to work
Thanks for your response. No, it should not be necessary to add the shortcut explicitly, and it works out of the box here. I wonder whether some other application interfering with/reacting to the ctrl++ instead of gnome-terminal could cause this, but I have no idea what that would be. (Especially since zoom out works without issues.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1192744 Title: Zoom Level using the key combination Ctrl++ does not appear to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1192744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164263] Re: user-specific and possible private files are written to a global location
This bug was fixed in the package libimobiledevice - 1.1.4-1ubuntu6.2 --- libimobiledevice (1.1.4-1ubuntu6.2) raring-security; urgency=low * SECURITY UPDATE: insecure /tmp usage (LP: #1164263) - debian/patches/CVE-2013-2142.patch: fall back to getpwuid_r instead of using /tmp in src/userpref.c. Added string_concat() function in src/Makefile.am, src/utils.c, src/utils.h. - added new symbol to debian/libimobiledevice3.symbols. - CVE-2013-2142 -- Marc Deslauriers marc.deslauri...@ubuntu.com Wed, 14 Aug 2013 11:56:31 -0400 -- 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/1164263 Title: user-specific and possible private files are written to a global location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1164263/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212386] Re: rhythmbox crashed with SIGSEGV in g_object_unref()
*** This bug is a duplicate of bug 1196278 *** https://bugs.launchpad.net/bugs/1196278 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 #1196278, 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/1212386/+attachment/3772903/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1212386/+attachment/3772905/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1212386/+attachment/3772909/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1212386/+attachment/3772910/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1212386/+attachment/3772911/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1212386/+attachment/3772912/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1212386/+attachment/3772913/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1196278 ** 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 rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1212386 Title: rhythmbox crashed with SIGSEGV in g_object_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1212386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212387] Re: gnome-settings-daemon crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 1201854 *** https://bugs.launchpad.net/bugs/1201854 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 #1201854, 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/1212387/+attachment/3772915/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1212387/+attachment/3772917/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1212387/+attachment/3772918/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1212387/+attachment/3772919/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1212387/+attachment/3772920/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1212387/+attachment/3772921/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1212387/+attachment/3772922/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1201854 ** 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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1212387 Title: gnome-settings-daemon crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1212387/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164263] Re: user-specific and possible private files are written to a global location
This bug was fixed in the package libimobiledevice - 1.1.4-1ubuntu3.2 --- libimobiledevice (1.1.4-1ubuntu3.2) quantal-security; urgency=low * SECURITY UPDATE: insecure /tmp usage (LP: #1164263) - debian/patches/CVE-2013-2142.patch: fall back to getpwuid_r instead of using /tmp in src/userpref.c. Added string_concat() function in src/Makefile.am, src/utils.c, src/utils.h. - added new symbol to debian/libimobiledevice3.symbols. - CVE-2013-2142 -- Marc Deslauriers marc.deslauri...@ubuntu.com Wed, 14 Aug 2013 11:56:31 -0400 ** Changed in: libimobiledevice (Ubuntu) Status: Confirmed = Fix Released ** Changed in: libimobiledevice (Ubuntu) Status: Confirmed = Fix Released -- 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/1164263 Title: user-specific and possible private files are written to a global location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1164263/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1083811] Re: Duplicated panels using separate x screens
Where should I add SRU information fields? In this bug description? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1083811 Title: Duplicated panels using separate x screens To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1083811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1201854] Re: gnome-settings-daemon crashed with signal 5 in _XReply()
** 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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1201854 Title: gnome-settings-daemon crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1201854/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212400] [NEW] flush after copy
Public bug reported: I think every day-to-day Linux user has come across the problem quite frequently by now, as it's by now means specific to elementary OS (and thus, I must admit I'm not certain whether I filed this report under the right project). Insert a USB drive (in this case a 4GB one with a FAT32 file system), copy a large file like a movie to it. Result: The copy dialog will show up, and within 10 seconds or so the bar is at 100% and it says 0 seconds remaining. After that you still have to wait ~5 minutes for the data to actually be copied. When looking at iotop during tis time you can see a process called flush is still actively working (the weird thing is that it's often more like 80%+ IO for a while, then nothing for a while, and repeat until finished). When it's finally done, the file copy dialog will disappear and you can safely unmount the storage media. This is a longstanding problem preset in many distro's, and I think it's about time something was done about it. Although I don't really know whether it's related to the file manager or something else. But seeing as I wouldn't have a clue what else it'd be related to, I chose to file it as a bug in the file manager. ** Affects: nautilus Importance: Undecided Status: New ** Affects: pantheon-files Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: copy cut external-media file media paste usb ** Attachment added: Screenshot from 2013-08-14 21:12:03.png https://bugs.launchpad.net/bugs/1212400/+attachment/3772988/+files/Screenshot%20from%202013-08-14%2021%3A12%3A03.png ** Also affects: nautilus Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1212400 Title: flush after copy To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1212400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212400] Re: flush after copy
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New = Confirmed -- 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/1212400 Title: flush after copy To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1212400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212400] Re: flush after copy
I think the problem is with what the percentage presents : It uses the amount read and cached in memory instead of the amount which is actually written to the destination. -- 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/1212400 Title: flush after copy To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1212400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1083811] Re: Duplicated panels using separate x screens
** Description changed: I'm trying to use separate x screens on nvidia card with 3 monitors. I'm expecting one top panel + one bottom panel on each screen, but instead i have got all panels on one screen. Restarting gnome panel (gnome-panel --replace) it will create two extra (blank) panel pairs on same screen, but new applets will be added on first panel pair. Screenshot ilustrating problem can be found here - http://askubuntu.com/questions/177226/duplicated-menu-panel-indicators- and-taskbar I tried to manualy set screen key (org-gnome-gnome- panel-layout-toplevels-top-panel-screen) on wich screen panel should appear with dconf Editor. But restarting gnome-panel that key will be reseted. Downloaded gnome-panel source code (apt-get source gnome-panel), spend some time trying to find problem, and probably i found it in file panel- toplevel.c. Line 4458: if (!screen || GDK_IS_SCREEN (screen)) Line 4459: screen = gdk_screen_get_default (); These lines are responsible for resetting screen key. It will reset screen to default if currenct screen exist, but its not what we want. We want reset screen to default if screen dosnt exist, so line 4458 should be - if (!screen || !GDK_IS_SCREEN (screen)) After compiling and installing new package, gnome panel works as expected. + + [Impact] + + This bug is important for me and from time to time I see bugs where + people write that there is problem with separate x screens. This is one + of the problems. + + I have made working fix and It would be nice if it is included in our + current LTS release. + + First part of fix is simple. It was missing ! in if statement. This fix + is included already in raring and in saucy. + + Second part is fix for unique id generation for gnome-panels. Now id is + generated with screen number included in its name. It is required to set + objects to correct panel. + + [Test Case] + + * To reproduce the bug you need at least two monitors. Than you need + configure x to use each monitor as separate x screen. + + * When you will login gnome-panels will be created on first screen. So + if you have 2 screens than on first screen will be 4 panels (2 top and 2 + bottom). If you have 3 screens than on first screen will be 6 panels (3 + top and 2 bottom) + + * It is posilbe to change panels settings, changing screen setting to + correct screen would allow to put gnome-panel on correct screen. Bet it + will be rest next time gnome-panels starts. + + [Regression Potential] + + * There is not any regression potential I can think of. It simply fix + probably typo bug now allowing gnome panels to be created on correct + screens. Gnome panel generates new id only when creating new panel, so + it should not affect exsisting gnome panels. + + * I am using fixed gnome panel. In this bug report is one user who have + confirmed that this works. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1083811 Title: Duplicated panels using separate x screens To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1083811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 885989] Re: white screen on second monitor when using two xsessions
** Branch linked: lp:~albertsmuktupavels/nautilus/white-screen-fix- precise ** Branch linked: lp:~albertsmuktupavels/nautilus/white-screen-fix -- 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/885989 Title: white screen on second monitor when using two xsessions To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/885989/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1212431] [NEW] gnome-terminal is installed but not shown in unity
Public bug reported: Fresh daily iso (2013-08-14) install on real hardware. And updated to latest updates ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 14 23:48:53 2013 InstallationDate: Installed on 2013-08-14 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130814) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1212431 Title: gnome-terminal is installed but not shown in unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1212431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1173886] Re: Wrong background colour for nautilus icon in Unity launcher
You can for example open the update-manager.desktop file located either in /usr/share/applications/ or ~/.local/share/applications with gedit and delete the line starting with X-Unity-IconBackgroundColor. This gives you back the chameleonic colour for the specific launcher icon. -- 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/1173886 Title: Wrong background colour for nautilus icon in Unity launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1173886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 10905] Re: Keyboard shortcuts, window management - Can't use any global keyboard shortcuts or hotkeys when applet/menu is open
** Changed in: unity Milestone: None = 7.1.1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/10905 Title: Keyboard shortcuts, window management - Can't use any global keyboard shortcuts or hotkeys when applet/menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/10905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1193595] [NEW] gnome-keyring problem effects power manager
You have been subscribed to a public bug: I'm reporting this as further info for this gnome-keyring error: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877 (Couldn'd add this report to that bug because Launchpad couldn't find any gnome keyring errors when I asked it to check. I presume it was only prepared to look for xfce4-power-manager bugs. This is neverthless a report of further failures related to this keyring problem.) This happened: Machine idle without much ado for some minutes after startup. Clicked icon to permit software updates. Entered PASSWORD. Pressed install. Left computer. Came back. Keyring PASSWORD request window was active. Software Updater had left an ERROR MESSAGE: update failed. Yet the Software Updater icon indicated 'restart required'. Entered PASSWORD for the keyring form. Pressed the Software Updater's restart icon. The reboot then asked for a PASSWORD as well. The PASSWORD request came with an ERROR MESSAGE: System policy prevents reboot when other users are logged in. Paused just a few moments while contemplating my distrust of all this PASSWORD gubbins and now this business of other users being logged in. (for further distrust and dismay over the keyring problem, see bug #575877). The reboot form was impatient. It disappeared. Another ERROR MESSAGE appeared: Reboot failed. Failed to request reboot. Please shutdown manually. The authentication log had this to say about it: see attached. (It's now 11.18am. I've been doing this report for about half an hour. You can see that CRON has meanwhile been opening and closing a root session like it was doing the can-can.) Is this bug a security vulnerability? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xfce4-power-manager 1.2.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Sat Jun 22 10:47:23 2013 InstallationDate: Installed on 2012-11-28 (205 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to raring on 2013-05-14 (38 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- gnome-keyring problem effects power manager https://bugs.launchpad.net/bugs/1193595 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1192744] Re: Zoom Level using the key combination Ctrl++ does not appear to work
Strange - this behavior is seen on my dev env. also - 12.10. I think I added all the debug dump when I filed this report. I am running a system76 gazelle pro notebook which has ubuntu specific keys built into it. On Wed, Aug 14, 2013 at 11:21 AM, Hans Joachim Desserud 1192...@bugs.launchpad.net wrote: Thanks for your response. No, it should not be necessary to add the shortcut explicitly, and it works out of the box here. I wonder whether some other application interfering with/reacting to the ctrl++ instead of gnome-terminal could cause this, but I have no idea what that would be. (Especially since zoom out works without issues.) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1192744 Title: Zoom Level using the key combination Ctrl++ does not appear to work Status in “gnome-terminal” package in Ubuntu: New Bug description: Open the Terminal application Click on Edit, select Profiles, select Edit and select Colors Using the options contained in the Colors tab modify the color palette, choosing some non-default colors or a different color scheme The colors in your terminal match your modifications Click on Edit, select Profiles, select Edit and select Background Set the terminal choosing the option Background Image Terminal background changes to the current wallpaper Change the Zoom Level using the key combination Ctrl++ and Ctrl-- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Wed Jun 19 16:25:39 2013 InstallationDate: Installed on 2013-06-17 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130523.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1192744/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1192744 Title: Zoom Level using the key combination Ctrl++ does not appear to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1192744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1011209] Re: eog crashes when navigation-keys are pressed continuously
** Description changed: - Eye of Gnome 3.4.1 crashes when a navigation key like the arrow-key or - enter is pressed continuously. Pressing the keys with high frequency - works fine, but when holding the key pressed, eog shows 3-5 images and - than disappears form the screen. - - DistroRelease: Ubuntu 12.04 - 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux - - Running eog from the terminal produces this output: - - - *** glibc detected *** eog: double free or corruption (!prev): 0x01529920 *** - === Backtrace: = - /lib/x86_64-linux-gnu/libc.so.6(+0x7e626)[0x7f6345ec3626] - /usr/lib/eog/plugins/libexif-display.so(+0x3005)[0x7f632f9f6005] - /usr/lib/eog/plugins/libexif-display.so(+0x3cf7)[0x7f632f9f6cf7] - /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0xfeca)[0x7f634693aeca] - /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x421)[0x7f6346953741] - /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f6346954242] - eog[0x424bac] - /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x16a)[0x7f634667dc9a] - /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x48060)[0x7f634667e060] - /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x34)[0x7f634667e124] - /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_application_run+0x1a4)[0x7f6347bfeb94] - eog(main+0x20c)[0x41dcfc] - /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f6345e6676d] - eog[0x41de19] - === Memory map: - 0040-00475000 r-xp 08:03 1050258 /usr/bin/eog - 00674000-00676000 r--p 00074000 08:03 1050258 /usr/bin/eog - 00676000-00679000 rw-p 00076000 08:03 1050258 /usr/bin/eog - 00d7-017aa000 rw-p 00:00 0 [heap] - 7f6329a67000-7f6329a6b000 r-xp 08:03 1312115 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so - 7f6329a6b000-7f6329c6b000 ---p 4000 08:03 1312115 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so - 7f6329c6b000-7f6329c6c000 r--p 4000 08:03 1312115 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so - 7f6329c6c000-7f6329c6d000 rw-p 5000 08:03 1312115 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so - 7f6329c6d000-7f6329d12000 r--p 08:03 1836864 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf - 7f6329d12000-7f6329d14000 r-xp 08:03 1312478 /usr/lib/x86_64-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so - 7f6329d14000-7f6329f13000 ---p 2000 08:03 1312478 /usr/lib/x86_64-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so - 7f6329f13000-7f6329f14000 r--p 1000 08:03 1312478 /usr/lib/x86_64-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so - 7f6329f14000-7f6329f15000 rw-p 2000 08:03 1312478 /usr/lib/x86_64-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so - 7f6329f15000-7f6329fc5000 r--p 08:03 1836865 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf - 7f6329fc5000-7f632e22a000 r--p 08:03 2248144 /usr/share/icons/gnome/icon-theme.cache - 7f632e22a000-7f632f7f r--p 08:03 2228739 /usr/share/icons/hicolor/icon-theme.cache - 7f632f7f-7f632f7f2000 r-xp 08:03 1050266 /usr/lib/eog/plugins/libfit-to-width.so - 7f632f7f2000-7f632f9f1000 ---p 2000 08:03 1050266 /usr/lib/eog/plugins/libfit-to-width.so - 7f632f9f1000-7f632f9f2000 r--p 1000 08:03 1050266 /usr/lib/eog/plugins/libfit-to-width.so - 7f632f9f2000-7f632f9f3000 rw-p 2000 08:03 1050266 /usr/lib/eog/plugins/libfit-to-width.so - 7f632f9f3000-7f632f9f9000 r-xp 08:03 1050280 /usr/lib/eog/plugins/libexif-display.so - 7f632f9f9000-7f632fbf8000 ---p 6000 08:03 1050280 /usr/lib/eog/plugins/libexif-display.so - 7f632fbf8000-7f632fbf9000 r--p 5000 08:03 1050280 /usr/lib/eog/plugins/libexif-display.so - 7f632fbf9000-7f632fbfa000 rw-p 6000 08:03 1050280 /usr/lib/eog/plugins/libexif-display.so - 7f632fbfa000-7f632fbfc000 r-xp 08:03 1050263 /usr/lib/eog/plugins/libreload.so - 7f632fbfc000-7f632fdfb000 ---p 2000 08:03 1050263 /usr/lib/eog/plugins/libreload.so - 7f632fdfb000-7f632fdfc000 r--p 1000 08:03 1050263 /usr/lib/eog/plugins/libreload.so - 7f632fdfc000-7f632fdfd000 rw-p 2000 08:03 1050263 /usr/lib/eog/plugins/libreload.so - 7f632fdfd000-7f632fdff000 r-xp 08:03 1050262
[Bug 397028] Re: rhythmbox freezes if internet drops while listening to internet radio
** Changed in: gst-plugins-bad Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/397028 Title: rhythmbox freezes if internet drops while listening to internet radio To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-bad/+bug/397028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
