[Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?
Another thread relevant, at least for the gnucash aspect of this bug: https://lists.gnucash.org/pipermail/gnucash-user/2018-March/075769.html -- 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/1765401 Title: gtk+ toolbar style setting ignored in bionic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?
Linking Jonathan's mailing list thread for reference: https://lists.gnucash.org/pipermail/gnucash-user/2018-April/076587.html -- 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/1765401 Title: gtk+ toolbar style setting ignored in bionic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 995189] Re: Ejecting network drive causes nautilus to close
Discusses this from the other angle, looks like the behaviour changed between 12.04 and 13.04: http://ubuntuforums.org/showthread.php?t=2156088 -- 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/995189 Title: Ejecting network drive causes nautilus to close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/995189/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 995189] Re: Ejecting network drive causes nautilus to close
Just noticed this on 12.04 too. Looks like a difficult issue, because there are some situations where closing the window seems to make sense, e.g. if the window automatically opened when USB/optical media was inserted. OTOH, if I open a nautilus window by hand, double-click a DAV share, then eject the share, closing seems the wrong thing to do. Would it be possible to keep track of the reason the window was originally opened, and change the behaviour based on that? -- 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/995189 Title: Ejecting network drive causes nautilus to close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/995189/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1193309] [NEW] package gnome-session-flashback 1:3.6.2-0ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: Getting update-alternatives: error: alternative path /usr/bin/gnome- session-fallback doesn't exist on configuration. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: gnome-session-flashback 1:3.6.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 ApportVersion: 2.10.2-0ubuntu2 AptOrdering: gnome-session-flashback: Configure Architecture: i386 Date: Fri Jun 21 12:02:27 2013 DpkgTerminalLog: Setting up gnome-session-flashback (1:3.6.2-0ubuntu9) ... update-alternatives: error: alternative path /usr/bin/gnome-session-fallback doesn't exist dpkg: error processing gnome-session-flashback (--configure): subprocess installed post-installation script returned error exit status 2 DuplicateSignature: package:gnome-session-flashback:1:3.6.2-0ubuntu9:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 GsettingsChanges: MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-panel Title: package gnome-session-flashback 1:3.6.2-0ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to saucy on 2013-06-09 (11 days ago) ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 saucy third-party-packages -- 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/1193309 Title: package gnome-session-flashback 1:3.6.2-0ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1193309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1193317] [NEW] gnome-panel crashed with SIGSEGV in gtk_container_forall()
Public bug reported: Possibly a dupe of bug #808776. Running saucy with all packages up-to- date. Rebooted, logged in using GNOME Flashback/Fallback, flipped through the menus, logged out, logged back in using Fallback (no effects), flipped through the menus again, logged out, logged in using default Unity session - this crash report was waiting. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-panel 1:3.6.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 ApportVersion: 2.10.2-0ubuntu2 Architecture: i386 Date: Fri Jun 21 12:15:30 2013 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: MarkForUpload: True ProcCmdline: gnome-panel SegvAnalysis: Segfault happened at: 0xb74ebe85: mov0x64(%eax),%edx PC (0xb74ebe85) ok source 0x64(%eax) (0xab0e) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 gtk_container_forall () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 Title: gnome-panel crashed with SIGSEGV in gtk_container_forall() UpgradeStatus: Upgraded to saucy on 2013-06-09 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace saucy third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1193317 Title: gnome-panel crashed with SIGSEGV in gtk_container_forall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1193317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 382379] Re: pdftops CUPS filter has several problems
Martin wrote on ubuntu-devel: I'm actually more concerned about also testing printers which work fine in Jaunty. I can help out with a Samsung ML-1610, and I guess Till can throw his armada of printers at it which he has at home, but we should send out an extra call for testing in blogs and ubuntu-devel. Everyday printing tasks (web pages, short letters, etc.) seem to work fine on my ancient HP DeskJet 840C with Karmic. I never hit the multiple page sizes problem, and I never got around to installing Jaunty, so I can't specifically confirm that those problems are fixed, but FWIW I can say that everything seems to work at least as well in Karmic as in Hardy. -- pdftops CUPS filter has several problems https://bugs.launchpad.net/bugs/382379 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 181788] Re: File chooser not working in current folder
I think gnome-bugs #540788 (http://bugzilla.gnome.org/show_bug.cgi?id=540788) is related, if not exactly the same. If anybody's grovelling around in the code, could they take a peek at this as well? From my comment on gnome-bugs: This bug drives me nuts on a fairly regular basis, I think the usual scenario is when you want to save a file in the parent directory of the default directory (the one which is displayed when the file selector is first shown): clicking on the parent in the path bar (is that the right terminology?) changes directory but leaves the subdir selected, so clicking save changes to the subdir instead. However, this doesn't happen consistently - it's only a problem if the focus is on the file list and not the file name entry box, and I don't understand why this is sometimes different. Is it something to do with the application behaviour? ** Bug watch added: GNOME Bug Tracker #540788 http://bugzilla.gnome.org/show_bug.cgi?id=540788 -- File chooser not working in current folder https://bugs.launchpad.net/bugs/181788 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 376145] Re: gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()
I've just seen this in VBox using an alternate CD install (using today's snapshot - 20090621): Jun 21 21:33:04 ubuntu kernel: [ 152.508292] gvfs-gdu-volume[3546]: segfault at c ip 003ebfda sp bfc4d680 error 4 in libgdu.so.0.0.0[3e3000+22000] For some reason apport is still disabled by default with an alternate CD install, and I haven't managed to reproduce this since I enabled it. It seemed to happen immediately after start-up / login. I can conform devicekit-disks is installed. -- gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables() https://bugs.launchpad.net/bugs/376145 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377426] Re: gvfs-gdu-volume segfault in libgdu.so.0.0.0
1) If you read my original report you'll see that apport didn't catch the crash. There is no crash file. I tried to attach with gdb but the process doesn't run continuously. I have however provided steps to reproduce which seem to work reliably (here at least.) 2) I haven't tested the bleeding edge - I thought the point of the alpha releases was to get a few more people testing than those that have time to continually follow the development release. If not, what _is_ the point of them? Or is there some other route for reporting alpha bugs that I don't know about - and isn't mentioned at www.ubuntu.com/testing ? I have a fair bit of linux knowledge and have done development in the past but I'm increasingly regressing to just being a user, albeit a user with a fair bit of (possibly slightly out of date) background knowledge. I wonder if some thought should be put into drawing up a short list of different categories of users and clarifying what methods each category should use to interact with the developers -- if any? -- gvfs-gdu-volume segfault in libgdu.so.0.0.0 https://bugs.launchpad.net/bugs/377426 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377426] Re: gvfs-gdu-volume segfault in libgdu.so.0.0.0
Just updated my VM to the current state of karmic, this is still happening. The nautilus windows no longer close themselves but the segfault is still logged by the kernel. This is still gvfs-backends 1.3git20090512-0ubuntu1. libgdu0 is 0.3.0-0ubuntu2. Attached is a manually updated Dependencies.txt (is there no way to get apport / ubuntu-bug to spit this out without filing a new report?) ** Attachment added: newdep.txt http://launchpadlibrarian.net/26854136/newdep.txt ** Changed in: gvfs (Ubuntu) Status: Invalid = New -- gvfs-gdu-volume segfault in libgdu.so.0.0.0 https://bugs.launchpad.net/bugs/377426 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377426] Re: gvfs-gdu-volume segfault in libgdu.so.0.0.0
*** This bug is a duplicate of bug 376145 *** https://bugs.launchpad.net/bugs/376145 If you are running the _Ubuntu Stable Release_ you might need to enable apport in /etc/default/apport and restart. Karmic is hardly the stable release, but you're right, having checked, apport is not enabled for some reason. I wonder if some thought should be put into drawing up a short list of different categories of users and clarifying what methods each category should use to interact with the developers -- if any? what do you mean exactly? Bug reports and testing are solicited from end-users but do not always seem to be welcomed with opened arms! I understand that bug herding is a very time consuming job, but bug reporting also requires a certain investment of time. If there is an intended audience for, say, alpha releases, perhaps that should be mentioned somewhere so we don't waste each other's time. If I'm testing a particular alpha release, mentioning that in the bug title doesn't seem like an obvious breach of ettiquette .. -- gvfs-gdu-volume segfault in libgdu.so.0.0.0 https://bugs.launchpad.net/bugs/377426 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377426] Re: gvfs-gdu-volume segfault in libgdu.so.0.0.0
*** This bug is a duplicate of bug 376145 *** https://bugs.launchpad.net/bugs/376145 OK, it does look like a duplicate of bug #376145. ** This bug has been marked a duplicate of bug 376145 gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables() -- gvfs-gdu-volume segfault in libgdu.so.0.0.0 https://bugs.launchpad.net/bugs/377426 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 376145] Re: gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()
I seem to have steps to reproduce this listed in bug #377426. -- gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables() https://bugs.launchpad.net/bugs/376145 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 377426] Re: gvfs-gdu-volume segfault in libgdu.so.0.0.0
*** This bug is a duplicate of bug 376145 *** https://bugs.launchpad.net/bugs/376145 On Sun, May 17, 2009 at 11:59:00AM -, Martin Olsson wrote: However, right now on karmic with all updates up to may 17th I consistently see 3 gvfs-gdu-volume crashes in my dmesg after every single reboot and none of these get detected by apport (could it be that they are supressed because I previously submitted that gvfs-gdu-volume? afaik apport does not work that way? There's a checkbox in the dialog that comes up that allows you to ignore future crashes for that program, but even though I didn't tick it I see the following in /var/log/apport.log: apport (pid 3511) Sun May 17 13:29:43 2009: this executable already crashed 2 times, ignoring (I got a slew of apport dialogs when I logged in and cancelled them because I didn't want to deal with them at that point. Didn't apport used to quietly display a notification icon when there were crash reports that needed sending, or am I imagining it?) -- gvfs-gdu-volume segfault in libgdu.so.0.0.0 https://bugs.launchpad.net/bugs/377426 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377426] [NEW] [karmic alpha1] gvfs-gdu-volume segfault in libgdu.so.0.0.0
Public bug reported: Binary package hint: gvfs [ 943.171002] gvfs-gdu-volume[3675]: segfault at c ip 00700fda sp bfb35f60 error 4 in libgdu.so.0.0.0[6f8000+22000] [ 1071.837061] gvfs-gdu-volume[3717]: segfault at c ip 00668fda sp bf8767c0 error 4 in libgdu.so.0.0.0[66+22000] This is Karmic Alpha 1, installed in Virtualbox. I seem to be reproducing it at the moment by doing the following from a fresh boot: 1. Start CD creator (Apps - Access.) 2. Open my home folder (Places - Home) and follow the examples link. 3. Add one of the documents to CD by right clicking and using send to, and choosing to zip the file. [another CD creator window opens] 4. Close the new CD creator window [all nautilus windows close, and the above message gets dumped in the kernel log] Apport's not picking up on this, and as the crashing process doesn't seem to run continually I can't attach to it with gdb or strace. This might be duplicate of bug #377276 or bug #376145, but I'm not sure. This is gvfs-backends 1.3git20090512-0ubuntu1. ProblemType: Bug Architecture: i386 Date: Sat May 16 22:53:42 2009 DistroRelease: Ubuntu 9.10 Package: gvfs 1.3git20090512-0ubuntu1 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-5.6-generic SourcePackage: gvfs Uname: Linux 2.6.30-5-generic i686 ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- [karmic alpha1] gvfs-gdu-volume segfault in libgdu.so.0.0.0 https://bugs.launchpad.net/bugs/377426 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377426] Re: [karmic alpha1] gvfs-gdu-volume segfault in libgdu.so.0.0.0
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/26830368/Dependencies.txt -- [karmic alpha1] gvfs-gdu-volume segfault in libgdu.so.0.0.0 https://bugs.launchpad.net/bugs/377426 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 218834] Re: dvd or cd does not mount
Given that this bug seems to a have tracked down a particular (timeout?) issue with hal that is being worked on, perhaps those having slightly different problem might get more joy over at Bug #293570 ? -- dvd or cd does not mount https://bugs.launchpad.net/bugs/218834 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 92680] Re: Vista partitions don't show on My Computer
This looks like a duplicate of bug #73227. -- Vista partitions don't show on My Computer https://launchpad.net/bugs/92680 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73227] Re: [feisty] some partitions do not appear in Places menu
Bug #92680 looks like a duplicate of this bug. -- [feisty] some partitions do not appear in Places menu https://launchpad.net/bugs/73227 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94111] gnome-sound-recorder crash with multiple windows
Public bug reported: Binary package hint: gnome-media I've reproduced this a couple of times, couldn't say /exactly/ what triggers it, but it seems to be to do with having multiple windows (created with File - new) open. I ran g-s-r, opened a .wav (ripped from CD, so 50-100meg), opened a new window and loaded a different version of the file (I was listening for ripping artifacts from different invocations of cdparanoia, not really relevant.) ** Affects: gnome-media (Ubuntu) Importance: Undecided Status: Unconfirmed -- gnome-sound-recorder crash with multiple windows https://launchpad.net/bugs/94111 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94111] Re: gnome-sound-recorder crash with multiple windows
Here's another instance. ** Attachment added: problem report2 http://librarian.launchpad.net/6874567/_usr_bin_gnome-sound-recorder.-4xt61.crash -- gnome-sound-recorder crash with multiple windows https://launchpad.net/bugs/94111 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94111] Re: gnome-sound-recorder crash with multiple windows
This is in edgy, BTW. Here's the problem report that I didn't get prompted to attach just now for some reason .. ** Attachment added: problem report http://librarian.launchpad.net/6874566/_usr_bin_gnome-sound-recorder.wkgP_p.crash -- gnome-sound-recorder crash with multiple windows https://launchpad.net/bugs/94111 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94111] Re: gnome-sound-recorder crash with multiple windows
Here we go, found it lurking in /var/crash .. ** Attachment added: full crash report http://librarian.launchpad.net/6874932/_usr_bin_gnome-sound-recorder.1000.crash -- gnome-sound-recorder crash with multiple windows https://launchpad.net/bugs/94111 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
