[Bug 1298210] Re: Yelp does not show man pages
Any of us may close the report by changing its status from New to Invalid. But I think there may be value to this report: as I mentioned on AU (http://askubuntu.com/questions/439801/man-command-does-not-work- with-yelp?noredirect=1#comment574556_439839), I'm not sure why the legacy behavior cannot also be supported. That would make this a feature request though (but if it's accepted, the triager can take that into account in assigning severity). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1298210 Title: Yelp does not show man pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1298210/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1203755] [NEW] file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Public bug reported: In a Saucy amd64 system I opened a .tar.xz archive (which I'd previously created myself on another system with tar cf ... followed by xz -9v ...) and double-clicked on the single folder it contained, to view its contents in file-roller itself before performing any extractions. file- roller crashed. I believe this is bug 723841 but I am not 100% sure without looking at a good symbolic trace, so I'm posting this just in case. I'll try to compare the trace as soon as there's a good one, unless someone else (or the Apport retracing service bot) does so first. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: file-roller 3.8.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1 Uname: Linux 3.10.0-4-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Sat Jul 20 22:21:49 2013 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2013-07-17 (5 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64 (20130716) MarkForUpload: True ProcCmdline: file-roller file:///home/username/Downloads/Maplesoft.Maple.v13.0.LINUX.x64-TBE.tar.xz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x41cb30:mov(%rbx),%rsi PC (0x0041cb30) ok source (%rbx) (0x0048) not located in a known VMA region (needed readable region)! destination %rsi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () _gtk_marshal_BOOLEAN__BOXED (closure=0x2998cb0, return_value=0x7fff97fb62e0, n_param_values=optimized out, param_values=0x7fff97fb6390, invocation_hint=optimized out, marshal_data=optimized out) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkmarshalers.c:85 g_closure_invoke (closure=0x2998cb0, return_value=0x7fff97fb62e0, n_param_values=2, param_values=0x7fff97fb6390, invocation_hint=0x7fff97fb6330) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777 signal_emit_unlocked_R (node=node@entry=0x265a990, detail=detail@entry=0, instance=instance@entry=0x27be610, emission_return=emission_return@entry=0x7fff97fb6460, instance_and_params=instance_and_params@entry=0x7fff97fb6390) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3582 g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=var_args@entry=0x7fff97fb6528) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3336 Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1203755 Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1203755/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1202847] Re: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
*** This bug is a duplicate of bug 723841 *** https://bugs.launchpad.net/bugs/723841 Comparison of symbolic stack traces indicates this is bug 723841. Other descriptive information supports this (see the description of that bug and of various duplicates). As for the different title, there may be some variation in the function where SIGSEGV occurs, but this appears to arise from (in)consistency between different symbolic stack traces (it tends to change across a symbolic trace, in either direction). Marking as duplicate; of course please comment if you think I might be wrong (and feel free to un-dupe it if you're pretty sure I am). ** This bug has been marked a duplicate of bug 723841 file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event() -- 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/1202847 Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1202847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1203755] Re: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
*** This bug is a duplicate of bug 723841 *** https://bugs.launchpad.net/bugs/723841 Comparison of the stack trace here to https://bugs.launchpad.net/ubuntu/+source/file- roller/+bug/723841/comments/3, in combination with the similarity in circumstances triggering the crash, is sufficient to convince me this is the same bug. -- 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/1203755 Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1203755/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1162928] [NEW] totem-video-thumbnailer crashed with SIGSEGV in oil_init()
Public bug reported: I was viewing a couple folders of video files in pcmanfm on a Lubuntu 11.10 i386 system. One folder was of .mkv files; the other was of .avi files. Nothing seemed to go wrong--pcmanfm did not itself crash, and all the files were properly thumbnailed. I was not using Totem itself to open any of the files, but I was playing some with VLC. Apport informed me that totem had crashed, and when I saw the crash was in the binary totem-video-thumbnailer, I assumed it happened because of some problem thumbnailing the videos in pcmanfm. This crash resembles these other two bugs: https://bugs.launchpad.net/ubuntu/+source/liboil/+bug/403110 https://bugs.launchpad.net/ubuntu/+source/totem/+bug/980651 But I cannot yet tell if it is really the same as either. It's also a little similar to these bugs: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/184536 https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10-ffmpeg/+bug/420930 ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: totem 3.4.3-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39 Uname: Linux 3.2.0-39-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Sun Mar 31 21:57:34 2013 ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationDate: Installed on 2012-08-21 (222 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True ProcCmdline: /usr/bin/totem-video-thumbnailer -s 128 file:///media/username/Noether/TV/Freaks%20and%20Geeks/freaks.and.geeks.s01e08-vrs.avi /home/username/.thumbnails/normal/10a9af21a855a1ab87b2c5ede83465c2.png ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x1d98ce28: mov0x10(%eax),%edx PC (0x1d98ce28) ok source 0x10(%eax) (0x0010) not located in a known VMA region (needed readable region)! destination %edx ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/liboil-0.3.so.0 oil_init () from /usr/lib/i386-linux-gnu/liboil-0.3.so.0 ?? () from /usr/lib/i386-linux-gnu/gstreamer-0.10/libgstflump3dec.so ?? () from /usr/lib/i386-linux-gnu/gstreamer-0.10/libgstflump3dec.so ?? () from /usr/lib/i386-linux-gnu/gstreamer-0.10/libgstflump3dec.so Title: totem-video-thumbnailer crashed with SIGSEGV in oil_init() UpgradeStatus: Upgraded to quantal on 2013-03-21 (11 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace quantal ** 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 totem in Ubuntu. https://bugs.launchpad.net/bugs/1162928 Title: totem-video-thumbnailer crashed with SIGSEGV in oil_init() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1162928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 773368] Re: Could not open certain PNG images
*** This bug is a duplicate of bug 172416 *** https://bugs.launchpad.net/bugs/172416 @Kushal This is happening because eog uncritically assumes filetype from filename. Most other modern image viewers look inside the image file to figure out what kind of image it is, which is why they do not have this bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/773368 Title: Could not open certain PNG images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/773368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 773368] Re: Could not open certain PNG images
*** This bug is a duplicate of bug 172416 *** https://bugs.launchpad.net/bugs/172416 @Kushal It is no longer necessary for you to attach any files or provide anymore information--there is already a bug for this (bug 172416), and I'm setting this as a duplicate of it. ** This bug has been marked a duplicate of bug 172416 eog determines image type from filename -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/773368 Title: Could not open certain PNG images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/773368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 773368] Re: Could not open certain PNG images
The original reporter (Kushal) indicates that this bug still occurs with Precise, so I am changing this back from Expired to New. @Kushal Can you attach a few .png images (or at least one) that cause this problem on your system, and a few .png images (or at least one) that do not? Such attachments may make it a lot easier to figure out what is going wrong. Please also add technical information to this bug about your current system by opening a Terminal window (Ctrl+Alt+T) and running: apport-collect 773368 ** Changed in: eog (Ubuntu) Status: Expired = New ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/773368 Title: Could not open certain PNG images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/773368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 459851] Re: can't use CTRL + C for copy'n'paste
Fixed x64 tag to amd64 (the correct architecture name for any 64-bit x86-compatible PC or Mac) and added names of all the Ubuntu releases in the duplicates. ** Tags removed: x64 ** Tags added: amd64 lucid maverick natty oneiric -- 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/459851 Title: can't use CTRL + C for copy'n'paste To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/459851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 827414] Re: gedit fails to start on first try, but does on the second
I still have this in Unity 2D as well, in Precise, still as described in bug 808918. (I haven't tested in Oneiric in a while.) -- 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/827414 Title: gedit fails to start on first try, but does on the second To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/827414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 887189] Re: gnome-panel crashed with SIGABRT in __kernel_vsyscall()
*** This bug is a duplicate of bug 507062 *** https://bugs.launchpad.net/bugs/507062 This is almost certainly bug 507062, see https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/507062/comments/94. ** This bug has been marked a duplicate of bug 507062 synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed. -- 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/887189 Title: gnome-panel crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/887189/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 876799] Re: gnome-panel crashed with SIGABRT in __kernel_vsyscall()
*** This bug is a duplicate of bug 507062 *** https://bugs.launchpad.net/bugs/507062 This is almost certainly bug 507062, see https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/507062/comments/94. ** This bug has been marked a duplicate of bug 507062 synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed. -- 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/876799 Title: gnome-panel crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/876799/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 887189] Re: gnome-panel crashed with SIGABRT in __kernel_vsyscall()
** Visibility changed to: Public -- 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/887189 Title: gnome-panel crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/887189/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 887189] Re: gnome-panel crashed with SIGABRT in __kernel_vsyscall()
** Description changed: On a Precise i386 system with ubuntu-desktop 1.245, gnome-session- fallback 3.2.1-0ubuntu1, and gnome-panel 1:3.2.0-0ubuntu1, I had installed gnome-session-fallback (which installed gnome-panel as a dependency) while in a Unity 2D session, and then I had logged out and logged in to a GNOME Classic session, and then I had logged out again and logged in to a GNOME Classic (no effects) session. Since this is a VMware Workstation 8.0.0 build-741780 virtual machine with no graphics acceleration, I wonder if perhaps the latter two sessions were equivalent. In any case, while there had been no crash prior to entering the GNOME Classic (no effects) session, shortly after the start of that session I was informed by Apport that gnome-panel had crashed with SIGABRT in __kernel_vsyscall(). The stack trace has no more symbols and doesn't look very good, but perhaps the Apport retracing service will be able to make something of it. + + I did not see any other incorrect or undesirable behaviour from gnome- + panel; the panel seemed to work fine, and did not even visibly flicker + momentarily. This might be the same as invalid bug 876799 (which occurred under somewhat similar circumstances and could not be effectively retraced), and/or as any one of a few valid bugs: bug 759451, bug 850113, or bug 507062. Hopefully a retracing will provide the necessary information to tell. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-panel 1:3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.1.0-2.3-generic 3.1.0 Uname: Linux 3.1.0-2-generic i686 ApportVersion: 1.25-0ubuntu1 Architecture: i386 Date: Sun Nov 6 11:33:04 2011 ExecutablePath: /usr/bin/gnome-panel InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcCmdline: gnome-panel Signal: 6 SourcePackage: gnome-panel StacktraceTop: - __kernel_vsyscall () - ?? () - ?? () - ?? () - ?? () + __kernel_vsyscall () + ?? () + ?? () + ?? () + ?? () Title: gnome-panel crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- 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/887189 Title: gnome-panel crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/887189/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 664886] Re: can not sign into msn protocol
@Erasmo Thank you for your proposed fix/workaround for this bug. This bug does not meet the criteria for the Opinion status. From the description, it appears to be a real bug (assuming it can be reproduced), and no reason has been provided for it not to be. See https://wiki.ubuntu.com/Bugs/Status and https://help.launchpad.net/Bugs/Statuses. Please read those carefully before changing any more bug statuses. (And also http://blog.launchpad.net/general/of-bugs-and-statuses, even though that doesn't discuss the Opinion status specifically.) @Atuzyk Normally I'd change this bug's status back to New, but since so much time is passed, before doing that I want to check with you to see if your're still experiencing it. If you are no longer able to produce this bug on any Ubuntu system, please change the status to Invalid. If you are able to produce it, please change the status back to New and tell us what Ubuntu release and empathy package version you're currently using (it's OK if it's the same as back then, but it might be different). If you applied the workaround provided by Erasmo and that fixed or did not fix the problem, please make sure to indicate that. ** Changed in: empathy (Ubuntu) Status: Opinion = Incomplete -- 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/664886 Title: can not sign into msn protocol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/664886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 795332] Re: nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb()
@Cristian Aravena This crash is in nautilus, rather than file-roller. Are you sure you are experiencing the same bug? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/795332 Title: nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/795332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 795332] Re: nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb()
@Cristian Aravena Sorry, please disregard my previous post. I was confusing this with another, different bug. Again, my apologies. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/795332 Title: nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/795332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877735] Re: gnome-panel mix with unity after upgrade from 11.04 to 11.10
@Valezan After you continue investigating the matter, it would be useful (whether or not you ind a solution) to report it as a bug -- it probably is one. (Of course, you might choose not to file a big, which is your prerogative -- there exists no obligation to do so.) -- 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/877735 Title: gnome-panel mix with unity after upgrade from 11.04 to 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/877735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 838404] Re: opening existing file with gksu gedit creates untitled document
*** This bug is a duplicate of bug 796076 *** https://bugs.launchpad.net/bugs/796076 I don't dispute that this bug is a duplicate of bug 796076, but I am posting here to address some advice from david6 which is potentially dangerous if applied. It is a bad idea to run graphical programs that save user-specific configuration data, like gedit, with sudo (without special flags to make it behave like those programs[1]) rather than gksu/gksudo/kdesudo. But not for security reasons. This is a bad idea because such programs often create or modify configuration data in such a way that the configuration files are accessible only by root, and then the application is fully or partially broken when run by the user unprivileged. (This could then become a security problem if the configuration data contained secret information which was then oversimplistically changed back to be owned by the non-root user, but I am not aware of any situation where this has been a problem, especially since such users are usually administrators who are permitted to read the data anyway.) See https://help.ubuntu.com/community/RootSudo for details. [1] Actually, those programs are graphical frontends for sudo, and they make sudo behave properly by passing special flags such as -H. (But it is a bit more complex than that, so you may still experience some problems if you run sudo -H instead of gksu/gksudo/kdesudo.) -- 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/838404 Title: opening existing file with gksu gedit creates untitled document To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/838404/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 796076] Re: When run as root [gksudo gedit whatever] gedit tries to open a 2nd 'untitled document 1'
This also occurs in Precise (see duplicate bug 880038). ** Tags added: precise -- 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/796076 Title: When run as root [gksudo gedit whatever] gedit tries to open a 2nd 'untitled document 1' To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/796076/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 723841] Re: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
** Tags added: oneiric -- 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/723841 Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/723841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878486] Re: gsd-printer crashed with SIGABRT in __kernel_vsyscall()
This also affects Precise (see duplicate bug 879953). ** Tags added: precise -- 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/878486 Title: gsd-printer crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/878486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878065] Re: gsd-printer crashed with SIGABRT in on_pdi_bus_acquired(): npn_registration_id 0
*** This bug is a duplicate of bug 878486 *** https://bugs.launchpad.net/bugs/878486 Now that bug 878486 is public, comparison of this bug's stack trace indicates that it is the same bug. Since that bug has been marked Triaged and submitted upstream (and has more people watching it, due to its numerous duplicates), I am marking this bug a duplicate of it, even though this bug was reported first. ** This bug has been marked a duplicate of bug 878486 gsd-printer crashed with SIGABRT in __kernel_vsyscall() -- 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/878065 Title: gsd-printer crashed with SIGABRT in on_pdi_bus_acquired(): npn_registration_id 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/878065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878065] Re: gsd-printer crashed with SIGABRT in on_pdi_bus_acquired(): npn_registration_id 0
*** This bug is a duplicate of bug 878486 *** https://bugs.launchpad.net/bugs/878486 (Bug 878486 also has a more complete symbolic 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/878065 Title: gsd-printer crashed with SIGABRT in on_pdi_bus_acquired(): npn_registration_id 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/878065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877735] Re: gnome-panel mix with unity after upgrade from 11.04 to 11.10
@Raphael Camus Also, you indicated that you upgraded from Ubuntu 10.04 to Ubuntu 11.10. But a direct upgrade from 10.04 to 11.10 is not supported. Did you upgrade from 10.04 to 10.10, and then to 11.04, and then to 11.10? Or did you upgrade using some other manner? Or are you actually not running Ubuntu 11.10? -- 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/877735 Title: gnome-panel mix with unity after upgrade from 11.04 to 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/877735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877735] Re: gnome-panel mix with unity after upgrade from 11.04 to 11.10
The central (and possibly only) element of this bug as it is described by Raphael Camus is the absence of window borders--windows cannot be resized, moved, or maximized/minimized. That indicates that the problem is with the window manager. The problem occurs in GNOME Classic, which uses metacity as its window manager, and it does not occur in 3D Unity, which uses compiz as its window manager. So this is a bug in metacity. If an affected system has the same problem in Unity 2D, which also uses metacity, and does not have the problem in GNOME (not GNOME Classic, but GNOME, installable via the package called gnome-shell), which also uses compiz, that would provide further confirmation. Valezan's problem description sounds completely different from this. Therefore, I am assuming it is a different problem. So in addition to changing the affected package from gnome-panel to metacity, I am also setting this bug back from Confirmed to New. @Valezan, if you believe you really are experiencing this bug, please explain. @Raphael Camus, if you are sure this bug should have Confirmed status, then please feel free to set it back to Confirmed, but please explain in detail why you think it should have that status. ** Package changed: gnome-panel (Ubuntu) = metacity (Ubuntu) ** Changed in: metacity (Ubuntu) Status: Confirmed = New ** Tags added: oneiric -- 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/877735 Title: gnome-panel mix with unity after upgrade from 11.04 to 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/877735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877735] Re: gnome-panel mix with unity after upgrade from 11.04 to 11.10
@Raphael Camus Unless you disagree with the above analysis, then assuming you still have a system that is affected by this bug, please provide more information about the metacity setup on the affected system by opening a Terminal window on it and running apport-collect 877735 (without the quotes). -- 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/877735 Title: gnome-panel mix with unity after upgrade from 11.04 to 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/877735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878486] Re: gsd-printer crashed with SIGABRT in __kernel_vsyscall()
** Bug watch added: Red Hat Bugzilla #747318 https://bugzilla.redhat.com/show_bug.cgi?id=747318 ** Also affects: gnome-settings-daemon (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=747318 Importance: Unknown Status: Unknown -- 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/878486 Title: gsd-printer crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/878486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877735] Re: gnome-panel mix with unity after upgrade from 11.04 to 11.10
@Valezan No problem. Have you filed a bug about this (different) problem that is affecting you? (If you do so, please read https://help.ubuntu.com/community/ReportingBugs carefully first.) I'm not sure what package *your* bug is in, so you might want to ask and see if anybody knows what package to file it against (you can post a question about this at https://answers.launchpad.net/ubuntu/+addquestion -- make sure that it's clear that you are asking what package to report it against, rather than asking whether or not it is a bug, or the first inclination of many responders will be simply to tell you to file a bug without giving any other info). -- 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/877735 Title: gnome-panel mix with unity after upgrade from 11.04 to 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/877735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877735] Re: gnome-panel mix with unity after upgrade from 11.04 to 11.10
Thanks, that is useful information. And yes, it would still be helpful for you to run apport-collect 877735. In addition, can you attach an archive of your ~/.local/share/applications folder (the version with which the problem does occur)? All this can certainly be provided tomorrow--there is no need for you to rush. Once you do provide all this information, you can change the bug's status back from Incomplete to New. ** Changed in: metacity (Ubuntu) Status: New = 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/877735 Title: gnome-panel mix with unity after upgrade from 11.04 to 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/877735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878065] Re: gsd-printer crashed with SIGABRT in on_pdi_bus_acquired(): npn_registration_id 0
I reported bug 879953, which looks similar to this bug, and which was automatically marked as a duplicate of private bug 878486. Can someone with access to bug 878486 look and see if it is the same as this bug? -- 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/878065 Title: gsd-printer crashed with SIGABRT in on_pdi_bus_acquired(): npn_registration_id 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/878065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 808918] Re: gedit usually sleeps indefinitely when launched by unity-2d-places
*** This bug is a duplicate of bug 827414 *** https://bugs.launchpad.net/bugs/827414 ** Tags added: precise -- 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/808918 Title: gedit usually sleeps indefinitely when launched by unity-2d-places To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/808918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 879953] Re: gsd-printer crashed with SIGABRT in __kernel_vsyscall()
*** This bug is a duplicate of bug 878486 *** https://bugs.launchpad.net/bugs/878486 ** Visibility changed to: Public ** Description changed: On a fully updated Precise i386 system (obtained by replacing oneiric with precise in sources.list, dist-upgrading, and rebooting) running on a VMware Workstation 8.0.0 build-471780 virtual machine, with gnome- settings-daemon 3.2.1-0ubuntu2, I was informed about 30 seconds after logging in to a unity-2d session that gsd-printer had crashed with SIGABRT in __kernel_vsyscall(). Before Apport told me about the crash, I had inserted the virtual VMware Tools CD (but I had not installed VMware Tools), and I had opened a Nautilus window, but I doubt either of those things is related to the crash. + + I do not have any printers attached to the affected (virtual) machine. + (By default, a VMware virtual machine is created with a virtual printer + device, but I deleted this device before the first boot of the virtual + machine.) There are also no printers attached to the host machine, which + runs Oneiric amd64 with kernel 3.0.0-12-generic. I suspect this is a duplicate of bug 878065 (which would indicate that bug 878065 affects Precise as well as Oneiric). The forthcoming automated symbolic retrace should make it possible to determine that with adequate certainty. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.1.0-1.1-generic 3.1.0-rc10 Uname: Linux 3.1.0-1-generic i686 ApportVersion: 1.24-0ubuntu1 Architecture: i386 Date: Sat Oct 22 10:54:56 2011 ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-printer InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-printer ProcEnviron: - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash Signal: 6 SourcePackage: gnome-settings-daemon StacktraceTop: - __kernel_vsyscall () - raise () from /lib/i386-linux-gnu/libc.so.6 - abort () from /lib/i386-linux-gnu/libc.so.6 - g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 + __kernel_vsyscall () + raise () from /lib/i386-linux-gnu/libc.so.6 + abort () from /lib/i386-linux-gnu/libc.so.6 + g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: gsd-printer crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- 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/879953 Title: gsd-printer crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/879953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 827414] Re: gedit fails to start on first try, but does on the second
Similar bug 808918 has been marked as a duplicate of this bug, but the behavior is a bit different and it persists even though this bug has been fixed (it seems reliably reproducible on a fully updated Precise system), so I suspect that it is not really a duplicate. I have commented in bug 808918 (https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/808918/comments/9) with details. -- 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/827414 Title: gedit fails to start on first try, but does on the second To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/827414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 808918] Re: gedit usually sleeps indefinitely when launched by unity-2d-places
*** This bug is a duplicate of bug 827414 *** https://bugs.launchpad.net/bugs/827414 I suspect that this may *not* be a duplicate of bug 827414. This just happened with on a fully updated Precise i386 system (obtained by replacing oneiric with precise in sources.list, dist-upgrading, and rebooting) with gedit 3.2.1-0ubuntu1 and unity-2d 4.12.0-0ubuntu1. Here's process information for gedit: ek@Gnar:~$ ps ax | grep -v grep | grep gedit 15906 ?Sl 0:00 gedit Running gedit a second time from unity-2d-places (or the launcher, or the Terminal) is successful. But running gedit a first time from the launcher or the Terminal is also successful, whereas running it the first time from unity-2d-places is not. This seems to be reproducible. -- 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/808918 Title: gedit usually sleeps indefinitely when launched by unity-2d-places To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/808918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 880038] [NEW] gedit opens unnecessary blank document when used to open a file as root
Public bug reported: On a fully updated Precise i386 system (obtained by replacing oneiric with precise in sources.list, dist-upgrading, and rebooting) with gedit 3.2.1-0ubuntu1, I created a test file and opened it in gedit: ek@Gnar:~$ echo test foo ek@Gnar:~$ gedit foo This behaved exactly as expected. Then I quit gedit and opened the file in gedit as root: ek@Gnar:~$ gksu gedit foo This opened the file, but opened a new untitled document as well, as shown in the attached screenshot. This also happens on Oneiric (same gedit version, test machine amd64). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.1.0-1.1-generic 3.1.0-rc10 Uname: Linux 3.1.0-1-generic i686 ApportVersion: 1.24-0ubuntu1 Architecture: i386 Date: Sat Oct 22 13:51:01 2011 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug i386 oneiric precise -- 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/880038 Title: gedit opens unnecessary blank document when used to open a file as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/880038/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 880038] Re: gedit opens unnecessary blank document when used to open a file as root
** Attachment added: gksu-gedit-extra-new-document.png https://bugs.launchpad.net/bugs/880038/+attachment/2567004/+files/gksu-gedit-extra-new-document.png -- 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/880038 Title: gedit opens unnecessary blank document when used to open a file as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/880038/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 653630] Re: brasero crashed with SIGSEGV in g_type_instance_get_private()
The upstream bug (https://bugzilla.gnome.org/show_bug.cgi?id=636431) has been marked as a duplicate of upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=644011. That bug is RESOLVED with status OBSOLETE, since it is believed not to occur on a GNOME 3 system (developer David King said: This was probably fixed in the port to GApplication from libunique in Brasero 3.0, so closing as OBSOLETE.) Is there anyone here who experiences this bug in Oneiric? Running two concurrent instances of Brasero is *not* the only way to produce this crash, and I am wondering if the bug is fixed for the less contrived and actually-important (but less well understood) way in which this bug sometimes occurs. I am guessing it is, but zero work on the natural ways this bug manifests seems to have been done upstream. (Which is not a criticism--perhaps not enough people get this bug without multiple instances for such work to be done.) Also, is there anyone here who always or usually experiences this bug when running Brasero, on any supported release of Ubuntu (Lucid, Maverick, Natty, or Oneiric, though probably not Oneiric since that has GNOME 3)? If so, then even though this bug will (probably) not be fixed upstream, it would then probably qualify to be fixed as an SRU (see https://wiki.ubuntu.com/StableReleaseUpdates). ** Bug watch added: GNOME Bug Tracker #644011 https://bugzilla.gnome.org/show_bug.cgi?id=644011 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/653630 Title: brasero crashed with SIGSEGV in g_type_instance_get_private() To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/653630/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872074] Re: Can't load pictures from new Kodak Camera to Ubuntu
For technical assistance, you may want to post a question (https://answers.launchpad.net/ubuntu/+source/nautilus/+addquestion for questions about your camera; https://answers.launchpad.net/ubuntu/+source/firefox/+addquestion for questions about your web browser). As for this bug, are you able to provide the information that Sebastien Bacher has requested? -- 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/872074 Title: Can't load pictures from new Kodak Camera to Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/872074/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 876799] Re: gnome-panel crashed with SIGABRT in __kernel_vsyscall()
** Visibility changed to: Public -- 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/876799 Title: gnome-panel crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/876799/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 446211] Re: yelp doesn't show some line breaks in alltray man page
** Changed in: yelp (Ubuntu) Status: Expired = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/446211 Title: yelp doesn't show some line breaks in alltray man page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/446211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 409706] Re: gnome-help excessive CPU usage
** Tags added: oneiric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/409706 Title: gnome-help excessive CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/409706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872074] Re: Can't load pictures from new Kodak Camera to Ubuntu
** Summary changed: - Can't load pictures from new Koday Camera to unbutu + Can't load pictures from new Kodak Camera to Ubuntu -- 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/872074 Title: Can't load pictures from new Kodak Camera to Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/872074/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 865407] Re: gnome terminal becomes very slow after a few days of intense usage
*** This bug is a duplicate of bug 784519 *** https://bugs.launchpad.net/bugs/784519 It looks like bug 784519 should have been marked back to New from Incomplete when you provided the information that the bug did not affect terminator. This would have prevented it expiring. I will change that bug back from Expired to New, explain my reasoning for doing so, and then mark this as a duplicate of that bug. After I do that, if there is any information here that has not been provided there, please provide it there. -- 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/865407 Title: gnome terminal becomes very slow after a few days of intense usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/865407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 865407] Re: gnome terminal becomes very slow after a few days of intense usage
*** This bug is a duplicate of bug 784519 *** https://bugs.launchpad.net/bugs/784519 I have read and considered in more detail, and since the answer was not definitive, I will mark bug 784519 back to Incomplete instead, resubscribe Pedro Villavicencio, and ask what if any additional information would be required for a developer to begin work on the bug. I will still mark this as a duplicate of that bug, which is appropriate. (There was really no reason to create a new bug report. A bug's status can always be changed back from Expired if more information can be provided to work on the bug.) ** This bug has been marked a duplicate of bug 784519 Natty: performance regression of Gnome terminal -- 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/865407 Title: gnome terminal becomes very slow after a few days of intense usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/865407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 784519] Re: Natty: performance regression of Gnome terminal
Also, there is someone who is interested in writing a patch for this, though I am at this point unsure if there is enough information available to fix the bug. (See https://answers.launchpad.net/ubuntu/+source/gnome- terminal/+question/173876, specifically post #4.) -- 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/784519 Title: Natty: performance regression of Gnome terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/784519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 784519] Re: Natty: performance regression of Gnome terminal
Duplicate bug 865407 indicates that the original poster is/was still interested in working on this bug. Is there any more information that can be provided to make progress here? (Marking back from Expired to Incomplete.) Also, can anyone check and see if this bug occurs on Oneiric? ** Changed in: gnome-terminal (Ubuntu) Status: Expired = Incomplete -- 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/784519 Title: Natty: performance regression of Gnome terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/784519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 871133] Re: Ubuntu Oneric Volume Step Can Not be Changed
@Josh Burghandy On the affected machine, please open a Terminal window (Ctrl+Alt+T) and run this command: apport-collect 871133 After doing so, please verify that information was automatically attached to this bug report and that the apport-collected tag was automatically added (please do *not* manually add it yourself). If this is the case, then you can go ahead and change this bug's status back from Incomplete to Confirmed. The automatically attached information should hopefully make this report complete enough to be worked on by a developer. @Sam_ Was there additional information you had wanted attached as well? You may want to clarify your request from https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/871133/comments/1. ** Tags added: oneiric ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed = Incomplete -- 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/871133 Title: Ubuntu Oneric Volume Step Can Not be Changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/871133/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 784519] Re: Natty: performance regression of Gnome terminal
If it can, then in addition to searching for and reporting the bug on the openSUSE's tracker, it would also be useful to search for and report it against gnome-terminal upstream (on the GNOME bug tracker). -- 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/784519 Title: Natty: performance regression of Gnome terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/784519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859622] Re: nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb()
*** This bug is a duplicate of bug 795332 *** https://bugs.launchpad.net/bugs/795332 ** Visibility changed to: Public ** This bug has been marked a duplicate of bug 795332 nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb() -- 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/859622 Title: nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/859622/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 795332] Re: nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb()
I've found that this still occurs with nautilus 1:3.1.92-0ubuntu3 (see duplicate bug 859622). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/795332 Title: nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/795332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 858887] Re: gvfsd-http crashed with SIGSEGV in g_settings_schema_get_string()
*** This bug is a duplicate of bug 839828 *** https://bugs.launchpad.net/bugs/839828 ** Visibility changed to: Public -- 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/858887 Title: gvfsd-http crashed with SIGSEGV in g_settings_schema_get_string() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/858887/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 858887] Re: gvfsd-http crashed with SIGSEGV in g_settings_schema_get_string()
*** This bug is a duplicate of bug 839828 *** https://bugs.launchpad.net/bugs/839828 This is /var/log/dpkg.log from, which includes entries from the upgrade operation during which this crash occurred. ** Attachment added: dpkg.log https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/858887/+attachment/2457824/+files/dpkg.log -- 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/858887 Title: gvfsd-http crashed with SIGSEGV in g_settings_schema_get_string() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/858887/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 858887] Re: gvfsd-http crashed with SIGSEGV in g_settings_schema_get_string()
*** This bug is a duplicate of bug 839828 *** https://bugs.launchpad.net/bugs/839828 In case it is useful, here is the Terminal text from the upgrade operation. It is not complete, but it should contain the relevant entries. ** Attachment added: PartialAptTerminalLog.txt https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/858887/+attachment/2457825/+files/PartialAptTerminalLog.txt -- 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/858887 Title: gvfsd-http crashed with SIGSEGV in g_settings_schema_get_string() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/858887/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816299] Re: gnome-terminal crashed with SIGSEGV in g_variant_unref()
I got this bug after an update that had not completed successfully, and the crash occurred every time I tried launching gnome-terminal. Then I ran sudo apt-get -f install, and now I am able to launch gnome- terminal without problems. In the upstream bug (https://bugzilla.gnome.org/show_bug.cgi?id=655366), a developer has said that this seems specific to Ubuntu. Do other people who experience this bug have similar experiences? -- 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/816299 Title: gnome-terminal crashed with SIGSEGV in g_variant_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/816299/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665552] Re: CTRL-C does not work in irc chat window
I am able to reproduce this problem in IRC in empathy 3.1.92-0ubuntu1 on an Oneiric i386 system in a 3D Unity session, so no, this is not fixed. (I have not tested with other session types, but I will do so on request.) It occurs in an IRC channel window but not in an AIM chat window. Right-clicking and clicking Copy works, but Ctrl+C does not. ** Tags added: oneiric -- 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/665552 Title: CTRL-C does not work in irc chat window To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/665552/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 845051] Re: gnome-settings-daemon crashed with SIGSEGV in g_main_context_dispatch()
I reported bug 853618, which is a duplicate of this bug and contains a more complete stack trace. Like this bug, I do not yet know if it can be reproduced with gnome-settings-daemon 3.1.92. (I do not know what specific steps triggered the bug in the first place, so it would be difficult for me to attempt to reproduce it deliberately.) I am not sure if my stack traces are sufficient to enable a developer to determine if the bug is still present in version 3.1.92, so I am not changing this bug's status back from Incomplete on the basis of this, but perhaps that should be done. Bug 853618's symbolically retraced nearly complete stack traces: https://launchpadlibrarian.net/80299474/Stacktrace.txt https://launchpadlibrarian.net/80299475/ThreadStacktrace.txt The stack traces in the other two public duplicate (bug 834284) look pretty good too. -- 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/845051 Title: gnome-settings-daemon crashed with SIGSEGV in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/845051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 853618] Re: gnome-settings-daemon crashed with SIGSEGV in call_in_idle_cb()
** Visibility changed 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/853618 Title: gnome-settings-daemon crashed with SIGSEGV in call_in_idle_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/853618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 449614] Re: Text in Quotes is not visible in man-Pages
This is no longer occurring for me, running yelp 3.0.0-0ubuntu2 on Natty amd64. Does the suggestion to requested a fix in -backports apply only to Lucid and Maverick? (Has this bug ever actually affected Natty, since Natty's release?) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/449614 Title: Text in Quotes is not visible in man-Pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/449614/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 828993] [NEW] package libglib2.0-0 2.29.16-0ubuntu2 failed to install/upgrade: error writing to 'standard output': Success
Public bug reported: I was updating an Oneiric i386 system in a 3D Unity session from the command-line (in gnome-terminal) with sudo apt-get dist-upgrade (and also accessing Launchpad using Chromium for an unrelated reason, which I doubt is relevant) when suddenly X.org terminated. I switch to tty1, logged in, and checked to see if apt-get was still running. It was running, when dpkg performing work. I waited for it to finish, then rebooted the machine, and was prompted to report this bug upon logging back in. I'll attach ~/.xsession-errors.old and /var/log/Xorg.0.log.old. In case it is helpful, here's the current output of apt-get -s -f install: ek@mk-laptop:~$ apt-get -s -f install NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfolks-telepathy24 libfolks24 libgck0 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 219 not fully installed or removed. Conf libc-bin (2.13-16ubuntu4 Ubuntu:11.10/oneiric [i386]) Conf udev (173-0ubuntu2 Ubuntu:11.10/oneiric [i386]) Conf initramfs-tools (0.99ubuntu2 Ubuntu:11.10/oneiric [all]) Conf dmsetup (2:1.02.48-4ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf libdevmapper1.02.1 (2:1.02.48-4ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf ntfs-3g (1:2011.4.12AR.4-2ubuntu2 Ubuntu:11.10/oneiric [i386]) Conf libqt4-declarative (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf libqtgui4 (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf libqt4-opengl (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf libqt4-svg (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf ubuntu-minimal (1.240 Ubuntu:11.10/oneiric [i386]) Conf apt-transport-https (0.8.16~exp5ubuntu6 Ubuntu:11.10/oneiric [i386]) Conf geoip-database (20110709-1 Ubuntu:11.10/oneiric [all]) Conf libaccountsservice0 (0.6.13-1ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf accountsservice (0.6.13-1ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf language-selector-common (0.46 Ubuntu:11.10/oneiric [all]) Conf libgeoip1 (1.4.8+dfsg-1ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf mlocate (0.23.1-1ubuntu2 Ubuntu:11.10/oneiric [i386]) Conf ubuntu-standard (1.240 Ubuntu:11.10/oneiric [i386]) Conf libabiword-2.8 (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf glib-networking (2.29.15-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libsoup2.4-1 (2.35.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf abiword-common (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [all]) Conf abiword (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf abiword-plugin-grammar (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf abiword-plugin-mathview (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf python-problem-report (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf python-apport (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf apport (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf dconf-gsettings-backend (0.9.0-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libgtk-3-common (3.1.12-0ubuntu1 Ubuntu:11.10/oneiric [all]) Conf libgtk-3-0 (3.1.12-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf gir1.2-gtk-3.0 (3.1.12-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf apport-gtk (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf computer-janitor (2.1.0-0ubuntu6 Ubuntu:11.10/oneiric [all]) Conf computer-janitor-gtk (2.1.0-0ubuntu6 Ubuntu:11.10/oneiric [all]) Conf libgs9-common (9.04~dfsg-0ubuntu6 Ubuntu:11.10/oneiric [all]) Conf libgs9 (9.04~dfsg-0ubuntu6 Ubuntu:11.10/oneiric [i386]) Conf ghostscript (9.04~dfsg-0ubuntu6 Ubuntu:11.10/oneiric [i386]) Conf cups-common (1.5.0-3 Ubuntu:11.10/oneiric [all]) Conf cups-client (1.5.0-3 Ubuntu:11.10/oneiric [i386]) Conf cups-ppdc (1.5.0-3 Ubuntu:11.10/oneiric [i386]) Conf cups (1.5.0-3 Ubuntu:11.10/oneiric [i386]) Conf libedataserver1.2-15 (3.1.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libcamel-1.2-28 (3.1.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libedataserver1.2-14 (3.1.4-0ubuntu7 Ubuntu:11.10/oneiric [i386]) Conf libebook1.2-11 (3.1.4-0ubuntu7 Ubuntu:11.10/oneiric [i386]) Conf libfolks25 (0.6.0-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libfolks-telepathy25 (0.6.0-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libp11-kit0 (0.3-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libgck-1-0 (3.1.4-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libgcr-3-1 (3.1.4-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf empathy-common (3.1.5-1ubuntu1 Ubuntu:11.10/oneiric [all]) Conf libmission-control-plugins0 (1:5.9.1-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf telepathy-mission-control-5 (1:5.9.1-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf empathy (3.1.5-1ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libebackend-1.2-1 (3.1.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libebook1.2-12 (3.1.5-0ubuntu1
[Bug 828993] Re: package libglib2.0-0 2.29.16-0ubuntu2 failed to install/upgrade: error writing to 'standard output': Success
** Attachment added: .xsession-errors.old https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/828993/+attachment/2289914/+files/.xsession-errors.old -- 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/828993 Title: package libglib2.0-0 2.29.16-0ubuntu2 failed to install/upgrade: error writing to 'standard output': Success To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/828993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 828993] Re: package libglib2.0-0 2.29.16-0ubuntu2 failed to install/upgrade: error writing to 'standard output': Success
** Description changed: I was updating an Oneiric i386 system in a 3D Unity session from the command-line (in gnome-terminal) with sudo apt-get dist-upgrade (and also accessing Launchpad using Chromium for an unrelated reason, which I doubt is relevant) when suddenly X.org terminated. I switch to tty1, logged in, and checked to see if apt-get was still running. It was running, when dpkg performing work. I waited for it to finish, then rebooted the machine, and was prompted to report this bug upon logging back in. - I'm attaching /var/log/dpkg.log and will attach ~/.xsession-errors.old - and /var/log/Xorg.0.log.old. + I'll attach ~/.xsession-errors.old and /var/log/Xorg.0.log.old. In case it is helpful, here's the current output of apt-get -s -f install: ek@mk-laptop:~$ apt-get -s -f install NOTE: This is only a simulation! - apt-get needs root privileges for real execution. - Keep also in mind that locking is deactivated, - so don't depend on the relevance to the real current situation! + apt-get needs root privileges for real execution. + Keep also in mind that locking is deactivated, + so don't depend on the relevance to the real current situation! Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: - libfolks-telepathy24 libfolks24 libgck0 + libfolks-telepathy24 libfolks24 libgck0 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 219 not fully installed or removed. Conf libc-bin (2.13-16ubuntu4 Ubuntu:11.10/oneiric [i386]) Conf udev (173-0ubuntu2 Ubuntu:11.10/oneiric [i386]) Conf initramfs-tools (0.99ubuntu2 Ubuntu:11.10/oneiric [all]) Conf dmsetup (2:1.02.48-4ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf libdevmapper1.02.1 (2:1.02.48-4ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf ntfs-3g (1:2011.4.12AR.4-2ubuntu2 Ubuntu:11.10/oneiric [i386]) Conf libqt4-declarative (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf libqtgui4 (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf libqt4-opengl (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf libqt4-svg (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf ubuntu-minimal (1.240 Ubuntu:11.10/oneiric [i386]) Conf apt-transport-https (0.8.16~exp5ubuntu6 Ubuntu:11.10/oneiric [i386]) Conf geoip-database (20110709-1 Ubuntu:11.10/oneiric [all]) Conf libaccountsservice0 (0.6.13-1ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf accountsservice (0.6.13-1ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf language-selector-common (0.46 Ubuntu:11.10/oneiric [all]) Conf libgeoip1 (1.4.8+dfsg-1ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf mlocate (0.23.1-1ubuntu2 Ubuntu:11.10/oneiric [i386]) Conf ubuntu-standard (1.240 Ubuntu:11.10/oneiric [i386]) Conf libabiword-2.8 (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf glib-networking (2.29.15-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libsoup2.4-1 (2.35.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf abiword-common (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [all]) Conf abiword (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf abiword-plugin-grammar (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf abiword-plugin-mathview (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf python-problem-report (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf python-apport (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf apport (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf dconf-gsettings-backend (0.9.0-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libgtk-3-common (3.1.12-0ubuntu1 Ubuntu:11.10/oneiric [all]) Conf libgtk-3-0 (3.1.12-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf gir1.2-gtk-3.0 (3.1.12-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf apport-gtk (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf computer-janitor (2.1.0-0ubuntu6 Ubuntu:11.10/oneiric [all]) Conf computer-janitor-gtk (2.1.0-0ubuntu6 Ubuntu:11.10/oneiric [all]) Conf libgs9-common (9.04~dfsg-0ubuntu6 Ubuntu:11.10/oneiric [all]) Conf libgs9 (9.04~dfsg-0ubuntu6 Ubuntu:11.10/oneiric [i386]) Conf ghostscript (9.04~dfsg-0ubuntu6 Ubuntu:11.10/oneiric [i386]) Conf cups-common (1.5.0-3 Ubuntu:11.10/oneiric [all]) Conf cups-client (1.5.0-3 Ubuntu:11.10/oneiric [i386]) Conf cups-ppdc (1.5.0-3 Ubuntu:11.10/oneiric [i386]) Conf cups (1.5.0-3 Ubuntu:11.10/oneiric [i386]) Conf libedataserver1.2-15 (3.1.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libcamel-1.2-28 (3.1.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libedataserver1.2-14 (3.1.4-0ubuntu7 Ubuntu:11.10/oneiric [i386]) Conf libebook1.2-11 (3.1.4-0ubuntu7 Ubuntu:11.10/oneiric [i386]) Conf libfolks25 (0.6.0-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libfolks-telepathy25 (0.6.0-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libp11-kit0 (0.3-0ubuntu1 Ubuntu:11.10/oneiric
[Bug 828993] Re: package libglib2.0-0 2.29.16-0ubuntu2 failed to install/upgrade: error writing to 'standard output': Success
** Attachment added: Xorg.0.log.old https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/828993/+attachment/2289924/+files/Xorg.0.log.old -- 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/828993 Title: package libglib2.0-0 2.29.16-0ubuntu2 failed to install/upgrade: error writing to 'standard output': Success To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/828993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 828993] Re: package libglib2.0-0 2.29.16-0ubuntu2 failed to install/upgrade: error writing to 'standard output': Success
** Description changed: I was updating an Oneiric i386 system in a 3D Unity session from the command-line (in gnome-terminal) with sudo apt-get dist-upgrade (and also accessing Launchpad using Chromium for an unrelated reason, which I doubt is relevant) when suddenly X.org terminated. I switch to tty1, logged in, and checked to see if apt-get was still running. It was running, when dpkg performing work. I waited for it to finish, then rebooted the machine, and was prompted to report this bug upon logging back in. + + This resembles bug 807863, but this happened with libglib2.0-0 rather + than libglib2.0-doc. I'll attach ~/.xsession-errors.old and /var/log/Xorg.0.log.old. In case it is helpful, here's the current output of apt-get -s -f install: ek@mk-laptop:~$ apt-get -s -f install NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfolks-telepathy24 libfolks24 libgck0 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 219 not fully installed or removed. Conf libc-bin (2.13-16ubuntu4 Ubuntu:11.10/oneiric [i386]) Conf udev (173-0ubuntu2 Ubuntu:11.10/oneiric [i386]) Conf initramfs-tools (0.99ubuntu2 Ubuntu:11.10/oneiric [all]) Conf dmsetup (2:1.02.48-4ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf libdevmapper1.02.1 (2:1.02.48-4ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf ntfs-3g (1:2011.4.12AR.4-2ubuntu2 Ubuntu:11.10/oneiric [i386]) Conf libqt4-declarative (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf libqtgui4 (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf libqt4-opengl (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf libqt4-svg (4:4.7.3-4ubuntu5 Ubuntu:11.10/oneiric [i386]) Conf ubuntu-minimal (1.240 Ubuntu:11.10/oneiric [i386]) Conf apt-transport-https (0.8.16~exp5ubuntu6 Ubuntu:11.10/oneiric [i386]) Conf geoip-database (20110709-1 Ubuntu:11.10/oneiric [all]) Conf libaccountsservice0 (0.6.13-1ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf accountsservice (0.6.13-1ubuntu3 Ubuntu:11.10/oneiric [i386]) Conf language-selector-common (0.46 Ubuntu:11.10/oneiric [all]) Conf libgeoip1 (1.4.8+dfsg-1ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf mlocate (0.23.1-1ubuntu2 Ubuntu:11.10/oneiric [i386]) Conf ubuntu-standard (1.240 Ubuntu:11.10/oneiric [i386]) Conf libabiword-2.8 (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf glib-networking (2.29.15-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libsoup2.4-1 (2.35.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf abiword-common (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [all]) Conf abiword (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf abiword-plugin-grammar (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf abiword-plugin-mathview (2.8.6-0.3ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf python-problem-report (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf python-apport (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf apport (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf dconf-gsettings-backend (0.9.0-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libgtk-3-common (3.1.12-0ubuntu1 Ubuntu:11.10/oneiric [all]) Conf libgtk-3-0 (3.1.12-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf gir1.2-gtk-3.0 (3.1.12-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf apport-gtk (1.21.3-0ubuntu4 Ubuntu:11.10/oneiric [all]) Conf computer-janitor (2.1.0-0ubuntu6 Ubuntu:11.10/oneiric [all]) Conf computer-janitor-gtk (2.1.0-0ubuntu6 Ubuntu:11.10/oneiric [all]) Conf libgs9-common (9.04~dfsg-0ubuntu6 Ubuntu:11.10/oneiric [all]) Conf libgs9 (9.04~dfsg-0ubuntu6 Ubuntu:11.10/oneiric [i386]) Conf ghostscript (9.04~dfsg-0ubuntu6 Ubuntu:11.10/oneiric [i386]) Conf cups-common (1.5.0-3 Ubuntu:11.10/oneiric [all]) Conf cups-client (1.5.0-3 Ubuntu:11.10/oneiric [i386]) Conf cups-ppdc (1.5.0-3 Ubuntu:11.10/oneiric [i386]) Conf cups (1.5.0-3 Ubuntu:11.10/oneiric [i386]) Conf libedataserver1.2-15 (3.1.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libcamel-1.2-28 (3.1.5-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libedataserver1.2-14 (3.1.4-0ubuntu7 Ubuntu:11.10/oneiric [i386]) Conf libebook1.2-11 (3.1.4-0ubuntu7 Ubuntu:11.10/oneiric [i386]) Conf libfolks25 (0.6.0-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libfolks-telepathy25 (0.6.0-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libp11-kit0 (0.3-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libgck-1-0 (3.1.4-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf libgcr-3-1 (3.1.4-0ubuntu1 Ubuntu:11.10/oneiric [i386]) Conf empathy-common (3.1.5-1ubuntu1 Ubuntu:11.10/oneiric [all]) Conf libmission-control-plugins0 (1:5.9.1-0ubuntu1 Ubuntu:11.10/oneiric
[Bug 446211] Re: yelp doesn't show some line breaks in alltray man page
I have a system with Oneiric i386 installed, with yelp 3.1.2-0ubuntu1 and alltray 0.71b-1, so I tested it on that. (I doubt this problem is machine-specific, and in any case, the machine on which I had previously produced this problem is a VM which I have since deleted.) I was not able to produce the problem. Yelp appears to render the relevant section of alltray's manpage correctly (see attached screenshot). I suppose that this can be closed as Fix Released if it is not considered to qualify for an SRU. ** Attachment added: yelp-alltray-manpage-oneiric.png https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/446211/+attachment/2283310/+files/yelp-alltray-manpage-oneiric.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/446211 Title: yelp doesn't show some line breaks in alltray man page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/446211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 808918] Re: gedit usually sleeps indefinitely when launched by unity-2d-places
Since it is very difficult for me to produce this bug by running gedit from the Terminal (or by any means other than from unity-2d-places), Jean-Baptiste Lallement will probably have to obtain the strace log. -- 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/808918 Title: gedit usually sleeps indefinitely when launched by unity-2d-places To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/808918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 723841] Re: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Should this be set back from In Progress to Triaged? -- 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/723841 Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/723841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 821442] Re: Nokia CS-18 segfaults after working previously
This may be due to a kernel problem as discussed in https://answers.launchpad.net/ubuntu/+source/gnome- nettool/+question/165390, but this is not a kernel bug report (it contains no information about your kernel and is not really written as a bug report at all, and it does not conform to the guidelines at https://help.ubuntu.com/community/ReportingBugs). It seems that perhaps you converted your original question to a bug to create this bug report; while that is sometimes appropriate, your original question did not contain the necessary information to be a bug report, so that was not a good way of going about things in this case. So I am marking this bug as Invalid. (This does not mean that this problem is not really caused by a bug, but rather that it will be best handled in a different form--either in the already existing question, or in a new bug report filed with ubuntu-bug against linux in Ubuntu and containing all the necessary information to make it possible for a developer to work on the problem. See http://blog.launchpad.net/general /of-bugs-and-statuses for an explanation of the Invalid bug status.) You may want to post the new information you've posted here at https://answers.launchpad.net/ubuntu/+source/gnome- nettool/+question/165390. If the problem you are experiencing is a segmentation fault in some program, then it is probably not a kernel bug at all. Let's continue discussing this in https://answers.launchpad.net/ubuntu/+source/gnome- nettool/+question/165390, where the discussion began originally. If you believe a segmentation fault is involved, please explain why you suspect this. Your question currently has Expired status, but you can reopen the question by posting and clicking the button indicating that you are still having a problem. ** Changed in: gnome-nettool (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-nettool in Ubuntu. https://bugs.launchpad.net/bugs/821442 Title: Nokia CS-18 segfaults after working previously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/821442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 819821] Re: users-admin crashed with signal 5 in do_pre_parse_initialization()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/819821 Title: users-admin crashed with signal 5 in do_pre_parse_initialization() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/819821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 814060] Re: shares-admin crashed with signal 5 in g_option_context_parse()
I am able to reproduce this bug on Oneiric with gnome-system-tools 2.32.0-0ubuntu7 (also on an i386 system running 3D Unity, but there is no reason to think this bug does not affect all Oneiric systems). I mention this even though the bug has already been confirmed and marked triaged because, contrary to https://bugs.launchpad.net/ubuntu/+source /gnome-system-tools/+bug/814060/comments/5, this cannot technically be reproduced by attempting to use Users and Groups. This is shares-admin, whereas Users and Groups actually runs users-admin. Reproducing a crash like this running Users and Groups can be taken to confirm bug 819821 (but I won't mark my own bug Confirmed). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/814060 Title: shares-admin crashed with signal 5 in g_option_context_parse() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/814060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 819821] Re: users-admin crashed with signal 5 in do_pre_parse_initialization()
*** This bug is a duplicate of bug 789333 *** https://bugs.launchpad.net/bugs/789333 I am not sure Apport retracing service is correct in marking this as a duplicate of bug 789333, since bug 789333 is currently being considered to be a GNOME3 PPA bug and this bug is not a GNOME3 PPA bug. See https://bugs.launchpad.net/ubuntu/+source/gnome-system- tools/+bug/789333/comments/8 (and possible future comments). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/819821 Title: users-admin crashed with signal 5 in do_pre_parse_initialization() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/819821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 789333] Re: users-admin crashes on start because of mixed GTK2 and 3 symbols
Apport retracing service has marked bug 819821, which is *not* a GNOME3 PPA bug (c.f. similar bug 814060 which is also not a GNOME3 PPA bug), as a duplicate of this bug (and removed all the useful attachments). Should I reverse that operation and manually attach a stack trace to bug 819821? Or should this bug be elevated to High (like bug 814060) and no longer considered a GNOME3 PPA bug? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/789333 Title: users-admin crashes on start because of mixed GTK2 and 3 symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/789333/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 819879] Re: time-admin crashed with signal 5 in do_pre_parse_initialization()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/819879 Title: time-admin crashed with signal 5 in do_pre_parse_initialization() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/819879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 819889] Re: network-admin crashed with signal 5 in do_pre_parse_initialization()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/819889 Title: network-admin crashed with signal 5 in do_pre_parse_initialization() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/819889/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 819879] Re: time-admin crashed with signal 5 in do_pre_parse_initialization()
*** This bug is a duplicate of bug 818990 *** https://bugs.launchpad.net/bugs/818990 ** Description changed: Like shares-admin (bug 814060) and users-admin (bug 819821), which are - provided by binary package gnome-system-tools, time-admin, which is - provided by binary package gnome-time-admin, crashes due to GTK+2/3 - incompatibility. I tested this on an Oneiric i386 system with gnome- - time-admin 2.32.0-0ubuntu7; the following was printed to the Terminal: + provided by binary package gnome-system-tools, and network-admin (bug + 819889), which is provided by binary package gnome-network-admin, time- + admin, which is provided by binary package gnome-time-admin, crashes due + to GTK+2/3 incompatibility. I tested this on an Oneiric i386 system with + gnome-time-admin 2.32.0-0ubuntu7; the following was printed to the + Terminal: Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported Trace/breakpoint trap (core dumped) If the shares-admin and users-admin crashes are to be considered the - same bug, then perhaps this should be considered the same bug too, even - though time-admin is provided by a different binary package (same source - package). + same bug, then perhaps this (and bug 819889) should be considered the + same bug too, even though time-admin (like network-admin) is provided by + a different binary package (same source package). ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-time-admin 2.32.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0 Uname: Linux 3.0.0-7-generic i686 Architecture: i386 Date: Tue Aug 2 11:02:43 2011 ExecutablePath: /usr/bin/time-admin InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcCmdline: time-admin ProcEnviron: - SHELL=/bin/bash - LANG=en_US.UTF-8 + SHELL=/bin/bash + LANG=en_US.UTF-8 Signal: 5 SourcePackage: gnome-system-tools StacktraceTop: - do_pre_parse_initialization (context=0x8895938, group=0x8898390, data=0x8895968, error=0xbf9410ec) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:676 - pre_parse_hook (context=0x8895938, group=0x8898390, data=0x8895968, error=0xbf9410ec) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:787 - g_option_context_parse (context=0x8895938, argc=0xbf941174, argv=0xbf941178, error=0xbf9410ec) at /build/buildd/glib2.0-2.29.14/./glib/goption.c:1773 - IA__gtk_parse_args (argc=0xbf941174, argv=0xbf941178) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:958 - IA__gtk_init_check (argc=0xbf941174, argv=0xbf941178) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:994 + do_pre_parse_initialization (context=0x8895938, group=0x8898390, data=0x8895968, error=0xbf9410ec) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:676 + pre_parse_hook (context=0x8895938, group=0x8898390, data=0x8895968, error=0xbf9410ec) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:787 + g_option_context_parse (context=0x8895938, argc=0xbf941174, argv=0xbf941178, error=0xbf9410ec) at /build/buildd/glib2.0-2.29.14/./glib/goption.c:1773 + IA__gtk_parse_args (argc=0xbf941174, argv=0xbf941178) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:958 + IA__gtk_init_check (argc=0xbf941174, argv=0xbf941178) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:994 Title: time-admin crashed with signal 5 in do_pre_parse_initialization() UpgradeStatus: Upgraded to oneiric on 2011-06-18 (44 days ago) UserGroups: adm admin dialout lpadmin plugdev sambashare -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/819879 Title: time-admin crashed with signal 5 in do_pre_parse_initialization() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/819879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 814060] Re: shares-admin crashed with signal 5 in g_option_context_parse()
To clarify my motivation in https://bugs.launchpad.net/ubuntu/+source /gnome-system-tools/+bug/814060/comments/6: The original bug report here sought to report both the users-admin and shares-admin crashes, but it characterized the executables as two scripts, whereas in fact they are separate ELF binaries with nonidentical contents. If this bug is to be taken to apply to both users-admin and shares-admin, then of course the original confirmation was correct and bug 819821 (and perhaps bug 789333, pertaining to the GNOME3 PPA in Natty) can be marked as a duplicate of this bug. Furthermore, time-admin and network-admin are provided by separate binary packages but the same source package; perhaps the corresponding crashes in those utilities (bug 819879 and bug 819889) should be marked duplicates of this bug as well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/814060 Title: shares-admin crashed with signal 5 in g_option_context_parse() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/814060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 819821] Re: users-admin crashed with signal 5 in do_pre_parse_initialization()
*** This bug is a duplicate of bug 814060 *** https://bugs.launchpad.net/bugs/814060 ** This bug is no longer a duplicate of bug 789333 users-admin crashes on start because of mixed GTK2 and 3 symbols ** This bug has been marked a duplicate of bug 814060 shares-admin crashed with signal 5 in g_option_context_parse() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/819821 Title: users-admin crashed with signal 5 in do_pre_parse_initialization() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/819821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 814060] Re: shares-admin crashed with signal 5 in g_option_context_parse()
I'm going to take that as indicating that it was not a mistake to have considered the related shares-admin and users-admin crashes as the same bug (even though the crashes are not in the same binary, as the wording in this bug report had implied). So I'll mark bug 819821 as a duplicate of this bug. Should bug 819879 (time-admin) and bug 819889 (network- admin) also be considered the same as this? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/814060 Title: shares-admin crashed with signal 5 in g_option_context_parse() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/814060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 742516] Re: gimp-2.6 crashed with SIGSEGV in g_closure_invoke() (with oxygen GTK theme)
@iLugo I cannot speak for Martin Pitt, nor for Canonical, but I believe I can explain why this bug is (and should be) of Medium rather than High importance. Importance for bugs in Ubuntu is assigned according to the priority in the Ubuntu project as a whole, and the effect of the bugs on Ubuntu users generally. This bug affects only a minority of Ubuntu users using GIMP, and GIMP is itself not nearly as heavily used a package as many other packages. If you search Launchpad to see what bugs *are* marked High, you'll see that they tend to be much broader in scope or have much more serious and unmitigable effects. The more bugs are marked High, the less meaningful it is for a bug to be marked High. This bug simply does not warrant that label. There is no parallel between GIMP in Ubuntu and Adobe Photoshop running on Windows and Mac OS X, and that topic is irrelevant to what this bug's importance should be. Those operating systems do not provide Photoshop (nor hardly any applications) as a component of the system, and they take no responsibility at all for whether or not Photoshop works. Photoshop could break for *all* users of Mac OS X or Windows and it is unlikely that Apple or Microsoft would be considered responsible in the slightest. Adobe is considered to be fully responsible for whether or not Photoshop works in any particular situation. However, if Microsoft or Apple provided support for Photoshop and it stopped working for a minority of users, and the OS vendor provided information about how to easily work around the problem, it seems unlikely that anyone would criticize the OS vendor for failing to prioritize fixing the problem. Actually, it seems unlikely that anyone would expect the OS vendor to make any effort at all to fix a problem with an easy workaround that affected so few users. (Fortunately, the standard to which Ubuntu's user community holds Canonical and the Ubuntu project is much higher than the standard to which most desktop OS vendors' customers hold them.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/742516 Title: gimp-2.6 crashed with SIGSEGV in g_closure_invoke() (with oxygen GTK theme) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/742516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 775590] Re: gimp in natty appears to depend on old, non-installable package libpoppler-glib4
@Ryan Are you still experiencing this problem? If not, you can mark this bug as Invalid (or just leave it Expired). If so, can you provide the information requested in https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/775590/comments/11? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/775590 Title: gimp in natty appears to depend on old, non-installable package libpoppler-glib4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/775590/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 808918] [NEW] gedit usually sleeps indefinitely when launched by unity-2d-places
Public bug reported: In a unity-2d session on an Oneiric i386 system with gedit 3.1.1-0ubuntu4 and unity-2d/unity-2d-places 3.8.10-0ubuntu2, running gedit from unity-2d-places (by clicking the home button, typing in gedit, and clicking Text Editor in the search results; or by pressing Alt+F2, typing in gedit, and pressing enter) almost always results in gedit sleeping indefinitely and never becoming usable or creating any visible windows: ek@Zim:~$ ps ax | grep -v grep | grep gedit 1911 ?Sl 0:00 gedit When this happens, I see the gedit icon appear in the unity-2d launcher for a short time, but then the icon disappears (and gedit continues running nonfunctionally in the background). Usually, gedit can be killed by SIGTERM; occasionally, it seems that SIGKILL is required. On rare occasion, gedit runs successfully when launched in this way. When I run gedit from a Terminal window (by running the command: gedit), it almost always works correctly, but on rare occasion, it sleeps indefinitely (in these cases, ps shows it as having state Sl+ rather than Sl, but I don't think that's a relevant difference). In these cases, SIGINT (from Ctrl+C) and SIGTERM have always been successful at terminating it, but I have only gotten the problem to occur a few times when running gedit from the Terminal. I strongly suspect that this is due to a deadlock. I would be pleased to attempt to furnish any further information required for the investigation of this bug. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gedit 3.1.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-4.5-generic 3.0.0-rc6 Uname: Linux 3.0.0-4-generic i686 Architecture: i386 Date: Mon Jul 11 13:15:44 2011 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110705.1) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric unity-2d -- 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/808918 Title: gedit usually sleeps indefinitely when launched by unity-2d-places To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/808918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 808918] Re: gedit usually sleeps indefinitely when launched by unity-2d-places
-- 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/808918 Title: gedit usually sleeps indefinitely when launched by unity-2d-places To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/808918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 808918] Re: gedit usually sleeps indefinitely when launched by unity-2d-places
** Description changed: In a unity-2d session on an Oneiric i386 system with gedit 3.1.1-0ubuntu4 and unity-2d/unity-2d-places 3.8.10-0ubuntu2, running gedit from unity-2d-places (by clicking the home button, typing in gedit, and clicking Text Editor in the search results; or by pressing Alt+F2, typing in gedit, and pressing enter) almost always results in gedit sleeping indefinitely and never becoming usable or creating any visible windows: ek@Zim:~$ ps ax | grep -v grep | grep gedit - 1911 ?Sl 0:00 gedit + 1911 ?Sl 0:00 gedit When this happens, I see the gedit icon appear in the unity-2d launcher for a short time, but then the icon disappears (and gedit continues running nonfunctionally in the background). Usually, gedit can be killed by SIGTERM; occasionally, it seems that SIGKILL is required. On rare occasion, gedit runs successfully when launched in this way. When I run gedit from a Terminal window (by running the command: gedit), it almost always works correctly, but on rare occasion, it sleeps indefinitely (in these cases, ps shows it as having state Sl+ rather than Sl, but I don't think that's a relevant difference). In these cases, SIGINT (from Ctrl+C) and SIGTERM have always been successful at terminating it, but I have only gotten the problem to occur a few times when running gedit from the Terminal. + When I run gedit from unity-2d-launcher (I am able to pin it to the + launcher when it is running from the Terminal), it also works OK. I have + not run it from the launcher frequently enough to know if it ever fails + when launched that way, though I suppose it probably does. + I strongly suspect that this is due to a deadlock. I would be pleased to attempt to furnish any further information required for the investigation of this bug. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gedit 3.1.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-4.5-generic 3.0.0-rc6 Uname: Linux 3.0.0-4-generic i686 Architecture: i386 Date: Mon Jul 11 13:15:44 2011 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110705.1) ProcEnviron: - SHELL=/bin/bash - LANG=en_US.UTF-8 + SHELL=/bin/bash + LANG=en_US.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) -- 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/808918 Title: gedit usually sleeps indefinitely when launched by unity-2d-places To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/808918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 795382] Re: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID__INT()
No, I have not experienced this anytime recently. -- 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/795382 Title: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID__INT() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/795382/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 685215] Re: users-admin hangs immediately when run as root
@alainpannetier You have misunderstood. Non-administrators cannot create user accounts (nor can they perform other administrative tasks). Being root is not the same thing as being an administrator. And the security model you are misunderstanding does not apply to Linux-based operating systems as a whole (just to some distributions, including Ubuntu), nor does it apply only to Linux-based operating systems. (For example, openSUSE doesn't use this security model, but Mac OS X does. And Debian formally supports this security model but also formally supports a different model.) I Ubuntu, for many administrative tasks, administrators run programs as root with sudo (or its graphical frontends, gksu, gksudo, and kdesudo). Only administrators can do this--regular users cannot. For other administrative tasks, like creating/managing user accounts with users- admin, the PolicyKit daemon (which itself runs as root) is asked to perform administrative operations--it will only agree to perform them if the user who is asking is an administrator. This bug is not a good place to discuss the general issue of how authentication is performed for administrative tasks. Please read https://help.ubuntu.com/community/RootSudo and http://en.wikipedia.org/wiki/PolicyKit if you have not done so already, and if you are still want to discuss or ask about this matter, please post a question (https://answers.launchpad.net/ubuntu/+addquestion). You can post a link to the question here, and I'll make sure to subscribe to the question and to attend to it (if nobody else does first), but since the issue you have raised is not specifically about this bug, it should not be discussed further here. If you have questions about why this bug was marked Won't Fix, posting a question would also be the most appropriate way to ask about that. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/685215 Title: users-admin hangs immediately when run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/685215/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 803631] Re: gnome-control-center crashed with SIGSEGV
** Description changed: In a 3D Unity session on the Oneiric i386 20110629 daily-live, I opened the Network control panel in gnome-control-center 1:3.0.2-1ubuntu5 by using Unity to search for network and clicking on the search result called Network. I configured a network connection with WPA2 encryption, but it did not appear to connect--instead, gnome-control-center crashed with SIGSEGV (in an unspecified function). When I re-entered the Control Center by typing gnome-control-center (without the quotes) in the Unity search box and pressing enter, I was able to return to the Network control panel, where my settings were remembered, and I was able to connect successfully just by re-selecting the network name. - - I am keeping this marked private while CoreDump.gz remains attached, in - case it contains network access credentials or other sensitive - information. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.0.2-1ubuntu5 ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4 Uname: Linux 3.0-2-generic i686 Architecture: i386 Date: Wed Jun 29 16:13:18 2011 Disassembly: = 0x101a3dff: Cannot access memory at address 0x101a3dff ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110629) ProcCmdline: gnome-control-center network ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x101a3dff:Cannot access memory at address 0x101a3dff PC (0x101a3dff) ok SP (0xbf885c20) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/803631 Title: gnome-control-center crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/803631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 742516] Re: gimp-2.6 crashed with SIGSEGV in g_closure_invoke()
This bug has a good stack trace, is indicated to affect 18 people, and has 32 duplicates (one of which, bug 757653, is indicated to affect 10 people, which might or might not overlap with the 18 people here). The bug has been extensively discussed and the circumstance under which it occurs are at least reasonably well understood and expressed. Therefore, I think there is far more than enough justification for marking this as Confirmed. ** Changed in: gimp (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/742516 Title: gimp-2.6 crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/742516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 797486] Re: gnome-power-manager crashed with signal 5 in g_object_newv()
*** This bug is a duplicate of bug 607999 *** https://bugs.launchpad.net/bugs/607999 In case anyone is wondering, the reason this bug is a duplicate of bug 607999 is because this bug was re-reported as bug 797712, and bug 797712 has just been found to be a duplicate of bug 607999. In the (unlikely) event that anyone thinks this isn't really a duplicate of bug 607999, they should post in/about bug 797712 instead of this bug. -- 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/797486 Title: gnome-power-manager crashed with signal 5 in g_object_newv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/797486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 607999] Re: gsettings-data-convert crashed with signal 5 in g_object_newv()
This bug is still happening with Oneiric i386 (see duplicate bug 797712)--this happens every time I start a Lubuntu Desktop session on a Lubuntu Oneiric system. Also tagging powerpc (from duplicate bug 608486). @sam tygier You can manually (re)enable apport on a stable system. See https://wiki.ubuntu.com/Apport#How_to_enable_apport. If the issue is that a crash has occurred more than a certain number of times and therefore is not reported, you can fix that by moving the relevant .crash file out of /var/crash (or you can just delete the file, but sometimes it's useful to have a .crash file so you can perform operations on it, like retracing with apport-retrace). ** Tags added: i386 oneiric powerpc -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/607999 Title: gsettings-data-convert crashed with signal 5 in g_object_newv() To manage notifications about this bug go to: https://bugs.launchpad.net/gconf/+bug/607999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 796088] Re: SMTP timout on sending mail
No, because you have not posted the results of performing the testing described in the second-to-last paragraph of https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/796088/comments/1. (You appear simply to have run apport-collect three more times, which doesn't add any more information that was added the first time you ran it, and is in any case completely irrelevant to the requested tests.) If you have performed that testing, please describe what happened in detail. -- 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/796088 Title: SMTP timout on sending mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/796088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 801507] Re: gnome-control-center crashed with SIGSEGV in deja_dup_config_widget_set_from_config()
** Visibility changed to: Public ** Description changed: I updated and rebooted an Oneiric i386 system (gnome-control-center - 1:3.0.2-1ubuntu4, deja-dup 19.2.1-0ubuntu1), and after a short time, I - was asked if I wanted to configure backup settings. I clicked yes - (actually I don't remember the wording of the dialog box), and a window - labeled Backup with blank white contents came up, then closed after - several seconds, and I was informed that gnome-control-center crashed - with SIGSEGV in deja_dup_config_widget_set_from_config(). + 1:3.0.2-1ubuntu4, deja-dup 19.2.1-0ubuntu1) into a unity-2d session, and + after a short time, I was asked if I wanted to configure backup + settings. I clicked yes (actually I don't remember the wording of the + dialog box), and a window labeled Backup with blank white contents came + up, then closed after several seconds, and I was informed that gnome- + control-center crashed with SIGSEGV in + deja_dup_config_widget_set_from_config(). Subsequently, when I manually went to System Settings and click on Backup (under System), I was able to view and change backup settings in detail, and no crash occurred. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.0.2-1ubuntu4 ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3 Uname: Linux 3.0-1-generic i686 Architecture: i386 Date: Fri Jun 24 06:13:55 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110604) ProcCmdline: gnome-control-center deja-dup ProcEnviron: - LANGUAGE=en_US:en - PATH=(custom, no user) - LANG=en_US.utf8 - LC_MESSAGES=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + PATH=(custom, no user) + LANG=en_US.utf8 + LC_MESSAGES=en_US.UTF-8 + SHELL=/bin/bash Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - deja_dup_config_widget_set_from_config (self=0x21ae2d40, _callback_=0, _user_data_=0x0) at ConfigWidget.c:164 - deja_dup_config_widget_key_changed (w=0x21ae2d40) at ConfigWidget.c:158 - deja_dup_config_widget_key_changed_wrapper (w=0x21ae2d40) at ConfigWidget.c:150 - g_cclosure_marshal_VOID__STRING (closure=0x21cf1790, return_value=0x0, n_param_values=2, param_values=0x21bc04c8, invocation_hint=0xbff593e0, marshal_data=0x0) at /build/buildd/glib2.0-2.29.8/./gobject/gmarshal.c:498 - g_closure_invoke (closure=0x21cf1790, return_value=0x0, n_param_values=2, param_values=0x21bc04c8, invocation_hint=0xbff593e0) at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c:771 + deja_dup_config_widget_set_from_config (self=0x21ae2d40, _callback_=0, _user_data_=0x0) at ConfigWidget.c:164 + deja_dup_config_widget_key_changed (w=0x21ae2d40) at ConfigWidget.c:158 + deja_dup_config_widget_key_changed_wrapper (w=0x21ae2d40) at ConfigWidget.c:150 + g_cclosure_marshal_VOID__STRING (closure=0x21cf1790, return_value=0x0, n_param_values=2, param_values=0x21bc04c8, invocation_hint=0xbff593e0, marshal_data=0x0) at /build/buildd/glib2.0-2.29.8/./gobject/gmarshal.c:498 + g_closure_invoke (closure=0x21cf1790, return_value=0x0, n_param_values=2, param_values=0x21bc04c8, invocation_hint=0xbff593e0) at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c:771 Title: gnome-control-center crashed with SIGSEGV in deja_dup_config_widget_set_from_config() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/801507 Title: gnome-control-center crashed with SIGSEGV in deja_dup_config_widget_set_from_config() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/801507/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 799384] Re: gnome-settings-daemon crashed with SIGSEGV in __run_exit_handlers()
*** This bug is a duplicate of bug 788710 *** https://bugs.launchpad.net/bugs/788710 Manual inspection of the original stack trace in this report reveals that this is the same as bug 788710. (Comparing to the stack trace in duplicate bug 796497 is most illustrative.) ** This bug has been marked a duplicate of bug 788710 gnome-settings-daemon crashed with SIGSEGV in exit() -- 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/799384 Title: gnome-settings-daemon crashed with SIGSEGV in __run_exit_handlers() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/799384/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 746958] Re: brasero burn operation fails with Power calibration area error
This still occurs on the same machine running brasero 2.32.1-0ubuntu2 on Natty amd64. The error message is exactly the same. This is with the same hardware (including the same internal burner) and media type as before (the DVD+R is from the same spindle). The log of the new burn attempt is attached. ** Attachment added: brasero-session-natty.log https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178657/+files/brasero-session-natty.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/746958 Title: brasero burn operation fails with Power calibration area error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 746958] Re: brasero burn operation fails with Power calibration area error
ek@Apok:~$ uname -a Linux Apok 2.6.38-10-generic #44-Ubuntu SMP Thu Jun 2 21:32:22 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: lspci.natty.txt https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178658/+files/lspci.natty.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/746958 Title: brasero burn operation fails with Power calibration area error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 746958] Re: brasero burn operation fails with Power calibration area error
** Attachment added: lshw.natty.txt https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178659/+files/lshw.natty.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/746958 Title: brasero burn operation fails with Power calibration area error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 746958] Re: brasero burn operation fails with Power calibration area error
** Attachment added: lsmod.natty.txt https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178660/+files/lsmod.natty.txt ** Tags added: natty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/746958 Title: brasero burn operation fails with Power calibration area error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 700975] Re: Power calibration area error
In case it's relevant, similar (quite possibly identical) bug 746958 does still occur on Natty. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/700975 Title: Power calibration area error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/700975/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 800065] Re: gnome-settings-daemon crashed with SIGSEGV
** Visibility changed 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/800065 Title: gnome-settings-daemon crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/800065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 798722] Re: gnome-settings-daemon crashed with SIGSEGV
*** This bug is a duplicate of bug 800065 *** https://bugs.launchpad.net/bugs/800065 ** This bug has been marked a duplicate of bug 800065 gnome-settings-daemon crashed with SIGSEGV -- 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/798722 Title: gnome-settings-daemon crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/798722/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 796465] Re: gnome-settings-daemon crashed with SIGSEGV
*** This bug is a duplicate of bug 800065 *** https://bugs.launchpad.net/bugs/800065 ** This bug is no longer a duplicate of bug 798722 gnome-settings-daemon crashed with SIGSEGV ** This bug has been marked a duplicate of bug 800065 gnome-settings-daemon crashed with SIGSEGV -- 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/796465 Title: gnome-settings-daemon crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/796465/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
