[Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff
The bug has reappeared, I see it on each login again. The patch was added in 3.22.5-1ubuntu2, but then apparently removed again in 3.22.6-1ubuntu1. No mention in the changelog. Have there been regressions? ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1572331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1572331] [NEW] GtkPlug scaled to half the expected size on HiDPI screens
Public bug reported: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "layout-failure.jpg" https://bugs.launchpad.net/bugs/1572331/+attachment/4640239/+files/layout-failure.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882825] Re: Does not save the configuration file under ~/.config/
** Changed in: onboard (Ubuntu) Status: New = Fix Released -- 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/882825 Title: Does not save the configuration file under ~/.config/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/882825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1227173] Re: On every startup Onboard asks for enabling accessibility
You might see the dialog one more time after turning the plugin off. Does it still show after repeated logins? -- 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/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1227173] Re: On every startup Onboard asks for enabling accessibility
I can't reproduce the login problems here, no good idea why that happens for you. I must be missing something, but the plugin really doesn't seem to do a lot. Is there anything in the other log files? sudo grep -r at-spi2-registryd /var/log/* -- 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/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1227173] Re: On every startup Onboard asks for enabling accessibility
OK, thank you, it is indeed g-s-d then. I've opened an upstream bug report here: https://bugzilla.gnome.org/show_bug.cgi?id=708506 I'll mark the Onboard task as incomplete until we know more about the prospect for g-s-d changes. Feel free to change this. ** Bug watch added: GNOME Bug Tracker #708506 https://bugzilla.gnome.org/show_bug.cgi?id=708506 ** Changed in: gnome-control-center (Ubuntu) Status: New = Invalid ** Changed in: onboard (Ubuntu) Status: New = Incomplete ** Changed in: gnome-settings-daemon (Ubuntu) Status: New = Confirmed -- 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/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1227173] Re: On every startup Onboard asks for enabling accessibility
Hi Till, how do you start Onboard? Is it auto-started by the Universal Access setting in gnome-control-center? gsettings get org.gnome.desktop.a11y.applications screen-keyboard-enabled Apparently if neither screen-keyboard nor screen-reader are enabled, gnome-settings-daemon may turn a11y off right after login: (gnome-settings-daemon_:2229): a11y-settings-plugin-DEBUG: screen reader or OSK enablement changed (gnome-settings-daemon_:2229): a11y-settings-plugin-DEBUG: Disabling toolkit-accessibility, screen reader and OSK disabled This isn't good for a manually started Onboard, since we need a11y for both auto-show and word suggestions. Hence the dialog asking to turn toolkit-accessibility back on. -- 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/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1227173] Re: On every startup Onboard asks for enabling accessibility
We could set 'toolkit-accessibility' silently in Onboard's startup, but that should be the last option. I'd prefer not to fight with gnome- settings-daemon over that key. It would still be an incomplete solution, since 'screen-keyboard-enabled' can be reset any time afterwards, taking down a11y for new processes with it. Setting 'screen-keyboard-enabled'=true in your script when entering tablet mode would get rid of the dialog, but some processes started before tablet mode might still be invisible to Onboard, firefox in particular. You'd have to restart them after switching to get auto-show and word suggestions working. The only real solution I see is keeping 'toolkit-accessibility' enabled at all times, i.e. not letting g-s-d turn it off. Either by patching gsd-a11y-settings-manager.c, or by deactivating the a11y-settings plugin. Try this: gsettings set org.gnome.settings-daemon.plugins.a11y-settings active false You have to do this only once, and looking through the source, there seems little harm for your custom setup in disabling the plugin. -- 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/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1088495] Re: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen
So no, Onboard isn't the cause. The unlock dialog's buttons still lock up when Onboard isn't embedded into the screensaver. The ultimate cause most likely lies within gnome-screensaver itself, there is a lot of pointer grabbing going on during normal operation. However, the trigger seems to be the way indicator-session locks the screen. I can reproduce the lockups pretty reliably, on desktop and Nexus 7, with: dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock; dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity They seem to disappear with adding a one second delay between those calls: dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock; sleep 1; dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity I'll link them both for now, gnome-screensaver and indicator-session. They'll be better able to sort this out. ** Also affects: indicator-session Importance: Undecided Status: New ** Also affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Changed in: onboard Status: New = Invalid ** Changed in: Ubuntu Raring Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1088495 Title: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1088495/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1088495] Re: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen
** Bug watch added: GNOME Bug Tracker #690244 https://bugzilla.gnome.org/show_bug.cgi?id=690244 ** Also affects: gnome-screensaver via https://bugzilla.gnome.org/show_bug.cgi?id=690244 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1088495 Title: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1088495/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
Apparently bug #1055698 can reproduce _XAllocID asserts reliably. Onboard in unity-greeter is not exactly a minimal test case, but perhaps this is still of some help. -- 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/905686 Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/905686/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035273] Re: [Precise] Accessible for rename text entry isn't marked editable
Confirming that this bug affects Onboard in Ubuntu 12.04 too. When auto- show is enabled, Onboard doesn't pop up when renaming files in nautilus. This seems fixed in Ubuntu 12.10 with nautilus 1:3.5.4-0ubuntu3, though, at least for Onboard. -- 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/1035273 Title: [Precise] Accessible for rename text entry isn't marked editable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1035273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 807473] Re: gtk_plug_get_id not introspectable
I have retested this with in gir1.2-gtk-3.0, 3.1.90-0ubuntu1 and found it to be fixed. ** Changed in: gtk+3.0 (Ubuntu) Status: Triaged = Fix Committed ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: onboard Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/807473 Title: gtk_plug_get_id not introspectable To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/807473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 662876] Re: [gcalctool] scientific notation not working
This is not fixed in Oneirics version 6.0.2-0ubuntu1. The linked bugzilla report seems to have stalled too. As this bug report states, it is impossible to exchange data with programs using E-notation (i.e. all programs I care for). Also In it's current form entering numbers in scientific notation is inefficient and error prone due to the need for parenthesis: e.g. 8E9/30E6 becomes 8x109/(30x106). Is there a way to to have it not pulled in by ubuntu-desktop anymore? This would allow for easier replacement with alternatives. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gcalctool in Ubuntu. https://bugs.launchpad.net/bugs/662876 Title: [gcalctool] scientific notation not working To manage notifications about this bug go to: https://bugs.launchpad.net/gcalctool/+bug/662876/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 324848] Re: autohide panel disappears after restart
Still happens in Natty. I can live with it though. My workaround is having a launcher in another panel that does sh -c gconftool-2 -s -t bool /apps/panel/toplevels/top_panel_screen0/auto_hide false; gconftool-2 -s -t bool /apps/panel/toplevels/top_panel_screen0/auto_hide true. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/324848 Title: autohide panel disappears after restart -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 519372] Re: Regression: keyboard layout indicator cannot be hidden
I've tried it and it does work in principle. I did gconftool-2 -s /desktop/gnome/peripherals/keyboard/general/disable_indicator -t bool true then logged out and back in and the layout indicator was gone. However there is no schema for the key, it has to be created manually and cannot be discovered by searching initially. Furthermore apparently g-s-d doesn't listen to the gconf notification, so there is no immediate effect when toggling the key. It seems to require a log-out/restart. -- Regression: keyboard layout indicator cannot be hidden https://bugs.launchpad.net/bugs/519372 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 549654] Re: no keyboard indicator applet
which displays automatically when you configure multiple keyboard layouts Why is it bad? I have multiple keyboard layouts setup all the time but I'm only occasionally switching between them for example. There is no reason for me to have the layout switcher cluttering up precious panel space. I've been desperate enough to track down and look through the source code in gnome-settings-daemon for a toggle, but the logic seems pretty hard-coded. There really needs to be a way to hide the layout switcher, at least with a gconf key. -- no keyboard indicator applet https://bugs.launchpad.net/bugs/549654 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 509509] Re: non-default color theme corrupted after gnome-settings-daemon restart
Similar things happen here with gnome-terminal 2.29.1-0ubuntu3 when switching themes. Only the the terminals background color seems affected though. Switching from Human to DarkRoom gives a DarkRoom-brown background color #4C4039, switching back to Human makes it an unreadable (white text on) light-grey #E6DDD5. Apparently gnome-terminal applies the themes window color for the background despite being told not to, i.e. having Use colors from system theme unchecked. -- non-default color theme corrupted after gnome-settings-daemon restart https://bugs.launchpad.net/bugs/509509 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343219] Re: Adding Fast User Switcher applet causes shut down options to disappear from System menu
I hate to have to decide between shutdown entries in the system menu and using the FUSA. It just had to be be done again as I installed Jaunty for a friend. She expected to be able to shutdown by menu and couldn't figure out how to do it on her own. She does switch accounts for the family occasionally but values shutting down by keyboard more. In the end we deleted FUSA. Why on earth does one have to choose one or the other? Design decision or not, IMO this fits exactly the above description of a paper cut. -- Adding Fast User Switcher applet causes shut down options to disappear from System menu https://bugs.launchpad.net/bugs/343219 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 385635] [NEW] (copy) inserted at wrong position when cloning files
Public bug reported: Binary package hint: nautilus When I use copypaste to clone a file with multiple dots in its name, nautilus adds (copy) at unexpected positions. It seems to add it right before the first dot, when it should insert it just before the last dot. Examples: test.a.b -- test (copy).a.b strace_liferea-1.4.26.txt -- strace_liferea-1 (copy).4.26.txt Howto: right click on file with multiple dots and select copy right click on empty space and select past ProblemType: Bug Architecture: amd64 Date: Wed Jun 10 18:49:59 2009 DistroRelease: Ubuntu 9.10 Package: nautilus 1:2.27.1-0ubuntu1 ProcEnviron: PATH=(custom, User Name) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-8.9-generic SourcePackage: nautilus Uname: Linux 2.6.30-8-generic x86_64 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- (copy) inserted at wrong position when cloning files https://bugs.launchpad.net/bugs/385635 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 385635] Re: (copy) inserted at wrong position when cloning files
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27748114/Dependencies.txt -- (copy) inserted at wrong position when cloning files https://bugs.launchpad.net/bugs/385635 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 290714] Re: weird looking gksu window for password dialogs as normal windows
This is still an issue in current Jaunty Beta, gksu 2.0.2-1ubuntu2, Compiz only. There is still an out-of-place looking transparent frame between window border and content. In other words, the window is too large for its content. ** Changed in: gksu (Ubuntu) Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) -- weird looking gksu window for password dialogs as normal windows https://bugs.launchpad.net/bugs/290714 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 328378] Re: gnome-panel doesn't respond
Gnome-panel locks up here too and I had added a backtrace at https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/203527/comments/79. I probably should have added it here, but I missed this bug before, sorry. -- gnome-panel doesn't respond https://bugs.launchpad.net/bugs/328378 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 324925] Re: nautilus crashed with SIGSEGV when turning off show_desktop
Being ready to throw gdb, valgrind and ltrace at the crash again, I found that it doesn't happen anymore :). Todays updates must have fixed it. Nautilus is still spawning though, faster even than before, but I guess this is now https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/328341 Correct me if I'm wrong, but I understand my attempts to get a good backtrace have been futile anyway because the whole trace looks invalid. None of its addresses even lie in executable memory. I guess no amount of debug symbols could have fixed that. -- nautilus crashed with SIGSEGV when turning off show_desktop https://bugs.launchpad.net/bugs/324925 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 203527] Re: Clicking on clock applet hangs gnome-panel
** Attachment added: gdb-evolution-data-server-2.26.txt http://launchpadlibrarian.net/22613156/gdb-evolution-data-server-2.26.txt ** Attachment removed: gdb-evolution-data-server-2.26.txt http://launchpadlibrarian.net/22613156/gdb-evolution-data- server-2.26.txt -- Clicking on clock applet hangs gnome-panel https://bugs.launchpad.net/bugs/203527 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 203527] Re: Clicking on clock applet hangs gnome-panel
** Attachment added: gdb-evolution-data-server-2.26.txt http://launchpadlibrarian.net/22613251/gdb-evolution-data-server-2.26.txt -- Clicking on clock applet hangs gnome-panel https://bugs.launchpad.net/bugs/203527 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 203527] Re: Clicking on clock applet hangs gnome-panel
I can see this happening on current Jaunty 9.04 too, but it started only some days ago. The panel just locks up when clicking the clock. 'evolution --force-shutdown' doesn't help here either and I'm not using google accounts. What helps is starting evolution to the calendar page, ie evolution --component=calendar. I can open the clock just fine then. However evolution --component=contacts locks the panel and shows an error Evolution Error, The Evolution address book has quit unexpectedly. and evolution-data-server-2.26 is gone. I'll attach a trace of evolution-data-server too, looks like it failed an assertion. ** Attachment added: gdb-gnome-panel.txt http://launchpadlibrarian.net/22613127/gdb-gnome-panel.txt -- Clicking on clock applet hangs gnome-panel https://bugs.launchpad.net/bugs/203527 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 324925] Re: nautilus crashed with SIGSEGV when turning off show_desktop
I'm trying to get something useful. It's kind of hard to track down because I can't reproduce the crash interactively. So far I got some automated backtraces, but all without symbols for the relevant parts. Fwiw, the one workaround I found was that I can stop gnome-session from respawning nautilus by setting X-GNOME-AutoRestart=false in /usr/share/applications/nautilus.desktop. -- nautilus crashed with SIGSEGV when turning off show_desktop https://bugs.launchpad.net/bugs/324925 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 324925] Re: nautilus crashed with SIGSEGV when turning off show_desktop
I have run apport-retrace locally now with the crash file of this report. With all dependent *.dgbsym packages installed the backtrace still looked as useless as the one I reported first. The system was always freshly updated from the main repos too, so it seems unlikely that any new report from apport would improve the situation. I'll change the state back to new to get this bug out of stealth mode. Feel free to invalidate again if there is something wrong with that. ** Changed in: nautilus (Ubuntu) Status: Invalid = New -- nautilus crashed with SIGSEGV when turning off show_desktop https://bugs.launchpad.net/bugs/324925 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 324848] [NEW] autohide panel disappears after restart
Public bug reported: Binary package hint: gnome-panel Hi, second try. I hope you can reproduce it this time. I have a panel set to autohide with animation turned off. This worked well for a while, but recently, after restarts that panel stays hidden. It basically disappears and moving the mouse at its edge has no effect. The only way to get it back is to change its gconf settings, for example toggling autohide in gconf-editor. The window-manager doesn't affect the outcome this time, it happens with visual effects set to none or to normal. Not running xinerama or dual displays either and the orientation of the panel doesn't matter as I've tried left and top. I took care that I could really, really reproduce it this time. So this is what I did on today's daily live cd (Jaunty): 1. Create new panel, an empty panel all setting at default 2. gconftool-2 -s -t bool /apps/panel/toplevels/panel_0/auto_hide true 3. gconftool-2 -s -t bool /apps/panel/toplevels/panel_0/enable_animations false 4. killall gnome-panel # or restart X -- panel is gone and to get it back: 5. gconftool-2 -s -t bool /apps/panel/toplevels/panel_0/auto_hide false 6. gconftool-2 -s -t bool /apps/panel/toplevels/panel_0/auto_hide true -- panel is back Description:Ubuntu jaunty (development branch) Release:9.04 gnome-panel: Installed: 1:2.25.5.1-0ubuntu1 Candidate: 1:2.25.5.1-0ubuntu1 Version table: *** 1:2.25.5.1-0ubuntu1 0 500 http://archive.ubuntu.com jaunty/main Packages The old bug report is here, moved to compiz: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/321698 ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- autohide panel disappears after restart https://bugs.launchpad.net/bugs/324848 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 324925] Re: nautilus crashed with SIGSEGV when turning off show_desktop
** Visibility changed to: Public -- nautilus crashed with SIGSEGV when turning off show_desktop https://bugs.launchpad.net/bugs/324925 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 321698] Re: Vertical panels set to 'autohide' fail to unhide
Assigning to compiz because it happens only when the cube plugin is active. ** Changed in: compiz (Ubuntu) Sourcepackagename: gnome-panel = compiz Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned) Status: Incomplete = New -- Vertical panels set to 'autohide' fail to unhide https://bugs.launchpad.net/bugs/321698 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 321698] Re: Vertical panels set to 'autohide' fail to unhide
Thanks for replying and no, not using xinerama. I did have a closer look and there seem to be two issues involved. You were right, what I described here is most likely a compiz issue and needs the Rotate Cube plugin enabled and Rotate Flip Left/Right set to the left/right screen edge (default). Then compiz always steals the left and right screen edges from gnome-panel, even when Edge Flip Pointer is disabled (default). This must have changed recently. Some two weeks ago compiz enabled these hot screen edges only when needed, e.g. moving a window to another desktop. The other issue is with (non-expanded?) autohide panels which only contain launchers, no applets like the clock. They don't unhide at all, compiz or not, until I reset and set their autohide-property in gconf- editor. So, my plan would be to move this report to compiz and open a new one for the second thing. Does that sound right? -- Vertical panels set to 'autohide' fail to unhide https://bugs.launchpad.net/bugs/321698 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 321698] [NEW] Vertical panels set to 'autohide' fail to unhide
Public bug reported: Binary package hint: gnome-panel Since the recent update of gnome-panel to 1:2.25.5.1-0ubuntu1 left and right panels set to 'Autohide' either don't appear at all or only after repeated tries. TEST CASE - Create a new panel. - Open its properties and set it to right, expand, autohide and close the property window. - Let the mouse pointer touch the right screen border a few times. -- The panel appears only after multiple tries. - Open gconf-editor. - Set /apps/panel/toplevels/the-panel/auto_hide_size = 2. -- The panel never unhides no matter how often I try. Ubuntu jaunty (development branch) Release:9.04 gnome-panel: Installed: 1:2.25.5.1-0ubuntu1 compiz: Installed: 1:0.7.8-0ubuntu7 ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- Vertical panels set to 'autohide' fail to unhide https://bugs.launchpad.net/bugs/321698 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 127798] Re: file roller can't recognize second of duplicate files
This still happens in Intrepid RC with file-roller 2.24.1-0ubuntu2. It works the first time and then fails for all subsequent downloads of the same file. I have to manually delete the files in /tmp to make file-roller open the archive correctly. -- file roller can't recognize second of duplicate files https://bugs.launchpad.net/bugs/127798 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
