[Bug 1722286] Re: Same action is forced for lid-close on AC and lid-close on battery
** Bug watch added: GNOME Bug Tracker #790607 https://bugzilla.gnome.org/show_bug.cgi?id=790607 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=790607 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/1722286 Title: Same action is forced for lid-close on AC and lid-close on battery To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1722286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722286] Re: Same action is forced for lid-close on AC and lid-close on battery
I'm attaching a proof of concept python script that restores the behaviour (in case it's useful to others). The script should be launched as: systemd-inhibit --who=me --why=because --mode=block --what=handle-lid-switch /path/to/custom_suspend.py from the session startup (gnome-session-properties) This is public domain and only lightly tested. It relies on existing gnome/systemd commands to perform the underlying action ** Attachment added: "custom_suspend.py" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1722286/+attachment/4970889/+files/custom_suspend.py -- 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/1722286 Title: Same action is forced for lid-close on AC and lid-close on battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1722286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722286] [NEW] Same action is forced for lid-close on AC and lid-close on battery
Public bug reported: Note: I'm flagging this as a bug in gnome-settings-daemon, but the program itself is not buggy. It's rather the usage of this program instead of unity-settings-daemon in ubuntu 17.10 that causes a system regression. --- Up to and including Ubuntu 17.04, unity-settings-daemon was used to managed suspend policy in the default graphic session (Unity). Unity-settings-daemon is a fork of (an old version of) gnome-settings-daemon. Now that gnome-shell is the default environment, session management is handled by gnome-settings-daemon. In particular, the action to perform when the lid is closed is handled by the gsd-power plugin of gnome-settings-daemon (as it was by unity-settings-daemon). With unity-settings-daemon, two dconf keys where honored (lid-close-ac- action and lid-close-battery-action, under org/gnome/settings- daemon/power ) to specify what action are performed when the user closes the laptop lid, depending on whether the laptop is plugged or on battery. In Ubuntu 17.10, gnome-settings-daemon ignore those settings (unless their value is 'ignore') and delegate actions to systemd-logind. The latter has no knowledge on whether the laptop is plugged or not and apply the same action regardless. This is a regression in a useful (and I believe popular) functionality. It is common to want the laptop to suspend when unplugged but expecting it to remain running when plugged (I believe this is the default on MacOS and windows and both system can be configured to distinguish between on-AC and on-Battery). The functionality can be restored with a bit of sweat with either hooks for acpid (or maybe a session script using the gnome framework to detect events and apply the correct policy, acpid-scripts run as root), but this is clearly not something the average user should have to tinker with. At the *very least* release note should advertise this regression (as a new feature ?) but ideally provide a compatibility layer to restore this functionality. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 16:15:54 2017 InstallationDate: Installed on 2015-06-03 (859 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to artful on 2017-03-16 (207 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 artful gnome-shell suspend systemd-logind -- 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/1722286 Title: Same action is forced for lid-close on AC and lid-close on battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1722286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 990228] Re: sidebar minimum width too large
Hi, I've posted a patch yesterday in gnome bugzilla. I'll *try* to upload packages to my ppa so that it gets better testing. For those who want to test the patch I rather suggest using the second patch at: https://bugzilla.gnome.org/show_bug.cgi?id=657632 Which also fixes a nasty bug where you cannot shrink down the side pane once you have enlarged it. ** Bug watch added: GNOME Bug Tracker #671691 https://bugzilla.gnome.org/show_bug.cgi?id=671691 ** Also affects: evince via https://bugzilla.gnome.org/show_bug.cgi?id=671691 Importance: Unknown Status: Unknown ** Bug watch added: GNOME Bug Tracker #657632 https://bugzilla.gnome.org/show_bug.cgi?id=657632 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/990228 Title: sidebar minimum width too large To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/990228/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 746291] Re: set a sane minimum width for the side pane
*** This bug is a duplicate of bug 990228 *** https://bugs.launchpad.net/bugs/990228 ** This bug has been marked a duplicate of bug 990228 sidebar minimum width too large -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/746291 Title: set a sane minimum width for the side pane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/746291/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1021153] [NEW] Thumbnails sidepane cannot be shrunk once it has been enlarged
Public bug reported: When one elarges the thumbnail sidepane horizontally, (s)he cannot shrink it down to a smaller size: steps to reproduce: - open a pdf in evince with sufficiently many pages (say 3). - Make the Thumbnail sidepane visible. Originally it should display one column with the three pages - Hold the pane separator and drag to the right. When the pane is sufficiently wide, the content might (it does not always do it...) reflow to show two columns and then three columns. If the thumbnails are not reflowed, just hit ctrl-r to force a redraw. - Try to shrink the sidepane to its original size. This cannot be done anymore (and if gvfs is installed, then the state of evince UI is kept as metadata for the *file* and you need command line hackery to reset it, see the upstream bugreport). What should happen instead: I should be able to freely resize the side pane until it reaches its minimal width of 1 column. Additional informations: evince version: 3.4.0-0ubuntu1.1 ubuntu release: precise (12.04) uname -a: Linux tartufo 3.2.0-26-generic #41-Ubuntu SMP Thu Jun 14 17:49:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1021153 Title: Thumbnails sidepane cannot be shrunk once it has been enlarged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1021153/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1021154] [NEW] Thumbnails sidepane cannot be shrunk once it has been enlarged
*** This bug is a duplicate of bug 704232 *** https://bugs.launchpad.net/bugs/704232 Public bug reported: When one elarges the thumbnail sidepane horizontally, (s)he cannot shrink it down to a smaller size: steps to reproduce: - open a pdf in evince with sufficiently many pages (say 3). - Make the Thumbnail sidepane visible. Originally it should display one column with the three pages - Hold the pane separator and drag to the right. When the pane is sufficiently wide, the content might (it does not always do it...) reflow to show two columns and then three columns. If the thumbnails are not reflowed, just hit ctrl-r to force a redraw. - Try to shrink the sidepane to its original size. This cannot be done anymore (and if gvfs is installed, then the state of evince UI is kept as metadata for the *file* and you need command line hackery to reset it, see the upstream bugreport). What should happen instead: I should be able to freely resize the side pane until it reaches its minimal width of 1 column. Additional informations: evince version: 3.4.0-0ubuntu1.1 ubuntu release: precise (12.04) uname -a: Linux tartufo 3.2.0-26-generic #41-Ubuntu SMP Thu Jun 14 17:49:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux ** Affects: evince Importance: Unknown Status: Unknown ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #657632 https://bugzilla.gnome.org/show_bug.cgi?id=657632 ** Also affects: evince via https://bugzilla.gnome.org/show_bug.cgi?id=657632 Importance: Unknown Status: Unknown ** This bug has been marked a duplicate of bug 704232 can´t resize ¨side pane¨ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1021154 Title: Thumbnails sidepane cannot be shrunk once it has been enlarged To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1021154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 704232] Re: can´t resize ¨side pane¨
Indeed, the bug was re-introduced. Here is what I *think* happened. Bug shows in 2.32. Evince folks make the sidepane horizontally scrollable (GtkScrolledWindow with hscrollpolicy to ALWAYS or AUTOMATIC), which in turns allows the GtkIconView to be resized accordingly. Later people complain about this unsightly horizontal scrollbar that is always present (all the more visible thanks to bug: #990228, which puts too much padding space around the thumbnails). hscrollbar policy is set to NEVER but this has the side effect that when resizing the sidepane down, the GtkIconView used to display the thumbnails sets the minimal width and prevent its container from being sized down. Public outrage ensues. I've attached two patches to the original bug-report. The first one only fixes this issue. The second one also fixes #990228 (upstream:671691) at the same time. Please test and report your findings in the upstream bug report. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/704232 Title: can´t resize ¨side pane¨ To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/704232/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 990228] Re: sidebar minimum width too large
Hi. Pacakges for precise including the fix are available in my ppa. Please do test. https://launchpad.net/~kim.nguyen/+archive/ppa -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/990228 Title: sidebar minimum width too large To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/990228/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 704232] Re: can´t resize ¨side pane¨
Hi. Pacakges for precise including the fix are available in my ppa. Please do test. https://launchpad.net/~kim.nguyen/+archive/ppa -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/704232 Title: can´t resize ¨side pane¨ To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/704232/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 924759] Re: Unity Greeter to support logging in on any display in a multi-monitor setup
With latest version (0.2.6-0ubuntu1) there are several shortcommings. Configuration is the following: - front monitor DELL 16:9 1680x1050 hard-coded to Primary in xorg.conf - left monitor is DELL 4:3 1280x1024 rotated counterclockwise (property set in xorg.conf) - Intel core i5 clarkdale integrated chipset, fully accelerated (compiz/unity/webgl etc... run flawlessly) Problems: - although intially my mouse cursor is centered on the primary monitor, the greeter defaults to the left one. moving the cursor fixes the problem (the login dialog jumps on the correct monitor) but: - even though my machine as decent specs (core i5 4 core, 4GB ram, graphic card described above) the switch of the login dialog is *very* slow and laggy. With the previous issue, the following happens: (1) cursor and login window are on different screen. so I move my mouse left to give focus to the correct screen (2) dialog starts to be redrawn (i guess) on the right screen but the process is very slow. (3) cursor arrives on the left screen. I start going to the keyboard to log in. (4) dialog jumps to the right screen, loosing focus, while mouse is still is on left screen. (5) step 1 to 4 are repeated until I can catch-up with the login screen (by moving fast enough or waiting long enough for the dialog to jump back and forth which it does not always do) -- 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/924759 Title: Unity Greeter to support logging in on any display in a multi-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/924759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 742544] Re: Launcher is shown on the wrong screen in some multi-monitor setups
@Andrea: It seems that unity ignores the primary monitor setting in some situations. Unity version: 4.20.0-0ubuntu2 Set-up: right monitor, 22 Dell monitor no rotation, primary left monitor, 19 Dell monitor, left rotation, not primary Unity launcher still shows up on the left monitor (which I use only to display documentations and stuff in a portrait-wise orientation). I believe this setup to be quite common. I'm attaching a screenshot wich summarizes all the infos: in .config/monitor.xml the primary monitor is set-up correctly in the display panel, the black title bar is set on the right monitor on the desktop, the launcher shows up on the leftmost one. Note that Primary is also set-up correctly in Xorg.conf and lightdm shows-up correctly on the right monitor. ** Attachment added: Screenshot showing wrong placement of launcher https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/742544/+attachment/2486875/+files/unity_primary.png -- 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/742544 Title: Launcher is shown on the wrong screen in some multi-monitor setups To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/742544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 742544] Re: Launcher is shown on the wrong screen in some multi-monitor setups
@Andrea: ok. Although I understand this can be a sane default, just ignoring X primary monitor seems too much. There are several reasonable configurations where the primary should get the panel, no matter where it is. E.g configuration used when you need to copy/read from a secondary monitor placed on the left (like my case), configurations where you put your laptop on the left of your big monitor (because there is no space on your desk on the right for instance etc...). I understand that if the panel is not on the left-most monitor it makes it difficult to just fling your mouse on the top-left corner and display the application menu but still. A much better solution would be to make the top-left corner of the primary monitor (with the panel) block the mouse pointer or put some kind of slight edge resistance... The semantics of primary monitor is, the monitor which is just in front of me, where I want stuff to be displayed. Ignoring that won't cut it in many situations. Plus that makes the black bar in the Display property completely useless and confusing. Anyway I've patched it locally (see rev. http://bazaar.launchpad.net /~unity-team/unity/trunk/revision/1609 for those interested) to suit my needs but I'm just curious to see how this design issue will be solved. Best. -- 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/742544 Title: Launcher is shown on the wrong screen in some multi-monitor setups To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/742544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 391398] Re: Applications segfault with gtk+ version 2.17.2 when selecting listbox values
The packages are built, I have been running all day with the patched gtk lib and no segfaults. Feel free to try them out. -- Applications segfault with gtk+ version 2.17.2 when selecting listbox values https://bugs.launchpad.net/bugs/391398 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 391398] Re: Applications segfault with gtk+ version 2.17.2 when selecting listbox values
That's very strange I haven't had a single segfault since the upgrade. Would you mind posting a backtrace of synaptic ? -- Applications segfault with gtk+ version 2.17.2 when selecting listbox values https://bugs.launchpad.net/bugs/391398 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 391398] Re: Applications segfault with gtk+ version 2.17.2 when selecting listbox values
HAaaa the typo is actually upstream it seems: http://git.gnome.org/cgit/gtk+/commit/?id=3bf1c7adadb1fda69e63fc6fe0f3698d937a1b80 towards the end. It's only in libgail. Could you try disabling assistive technologies and see if it still segfaults ? System/Preferences/Assistive Technologies and untick enable assistive tech. I'll upload a new version of the package to fix it and report upstream to. -- Applications segfault with gtk+ version 2.17.2 when selecting listbox values https://bugs.launchpad.net/bugs/391398 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 391398] Re: Applications segfault with gtk+ version 2.17.2 when selecting listbox values
As a matter of fact, this typo as well as a few others were fixed by commit: http://git.gnome.org/cgit/gtk+/commit/?id=1a385c50f041cdcc8ee88b27af85094901c2b05d I'll add it to the package. -- Applications segfault with gtk+ version 2.17.2 when selecting listbox values https://bugs.launchpad.net/bugs/391398 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 391398] Re: Applications segfault with gtk+ version 2.17.2 when selecting listbox values
It's not broken, it's gone. You have: +#ifndef GTK_DISABLE_DEPRECATED GList *gtk_cell_view_get_cell_renderers (GtkCellView *cell_view); +#endif in gtkcellview.h (and of course GTK_DISABLE_DEPREATED is enabled during compilation). The code is still there so the there is no linking error but now every use of the function as a return type of int. (the default type for functions in C) instead of GList*. I guess the segfaults only occur on amd64 since on this arch sizeof(void*) is 8 and sizeof(int) is 4, so the higher 4 bytes of the pointer gets truncated. This would explain why the segfaults do not occur 100% of the time (when the old function returns an address which fits on 4 bytes then everything is fine). Anyway, these functions are not used upstream anymore by gtk itself but other libs might still use them (and thus compile without GTK_DISABLE_DEPRECATED) so there really isn't anything to report upstream. -- Applications segfault with gtk+ version 2.17.2 when selecting listbox values https://bugs.launchpad.net/bugs/391398 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 391398] Re: Applications segfault with gtk+ version 2.17.2 when selecting listbox values
Are the deprecated functions really used by nm-applet and pidgin or is it only gtk which is segfaulting ? A quick grep in the pidgin source code shows that at least pidgin is not using gtk_cell_view_get_cell_renderers. With gtk currently compiled as it is in Karmic, *any* program which uses a drop down list might segfault on amd64. -- Applications segfault with gtk+ version 2.17.2 when selecting listbox values https://bugs.launchpad.net/bugs/391398 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 391398] Re: Applications segfault with gtk+ version 2.17.2 when selecting listbox values
What? removing deprecated code is a major goal toward gtk 3.0 so this has to be done. Note that *none* of the applications are broken because of the deprecation, you don't need a compatibility library and they don't need to be updated (at least not as far as this bug is concerned). All the applications are broken because there is a *bug* in gtk 2.17.2 namely it uses internally a deprecated api which in turn cause the problem of pointer cast I mentioned above. This has already been fixed upstream. Glitches like this are bound too happen, 2.17.x *is* a developpement release. -- Applications segfault with gtk+ version 2.17.2 when selecting listbox values https://bugs.launchpad.net/bugs/391398 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 391398] Re: Applications segfault with gtk+ version 2.17.2 when selecting listbox values
Kim: Deprecated API is only removed when 3.0 is released, not in releases leading up to 3. This is an *development* release leading to 3.0. From my understanding deprecation is done in two steps. 1) Deprecate only the header, not the code. This way new programs don't use the old function and old programs can still be compiled without GTK_DISABLE_DEPRECATED. Incidentally, gtk itself is compiled (always for an development branch) with GTK_DISABLE_DEPRECATED in order to spot deprecated code paths and not use them internally. This is what is done in 2.17.x I believe. 2) Removal of deprecated code. Old program using the deprecated function won't compile anymore. This will happen in the unstable leading to 3.0 (perhaps 2.19.x ?). So to sum up. GTK *internally* was still using a depreacted function in 2.17.2 despite compiling with GTK_DISABLE_DEPRECATED, hence the segfaults. Bummer, developpment releases are precisely done for this puropose, testing new features and bug reporting. No one should complain about this. The bug was fixed upstream even before this bugreport was filled. The package is lagging a bit behind but considering the huge change that 2.17.3 is (integration of the client-side-window branch in particular, which breaks the directfb port and still has a few rendering glitches), one can hardly blame the debian/ubuntu package maintainers for not uploading this version yet. I have tested the three patches against the current 2.17.2 in karmic. I have uploaded the patched packages in a ppa I just opened, they are queued for building and should be ready sometime today. If it is the latter the GTK+ maintainers are smoking crack and someone probably needs to hit them with a cluebat. This is a bugtracker, not a forum, please refrain from doing such comments, it only add to the noise. Everyone is welcome to try the new packages when they are built: https://launchpad.net/~kim.nguyen/+archive/ppa -- Applications segfault with gtk+ version 2.17.2 when selecting listbox values https://bugs.launchpad.net/bugs/391398 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 391398] Re: Applications segfault with gtk+ version 2.17.2 when selecting listbox values
Hi guys, the problem is the use of the deprecated function get_cell_renderers. Instances of the bugs are in - gtk file chooser in the location bar, the drop down tooltip for completion segfaults, - evince, the drop down list widget to change the zoom makes the app segfault - epiphany, the url bar would somtime segfaults when showing possible completions - .. much more. cherry picking the following commits from upstream fixes all these issues: http://git.gnome.org/cgit/gtk+/commit/?id=d51132e5846d93d15a9a35e4b2cbade1008078fb http://git.gnome.org/cgit/gtk+/commit/?id=c12a8388f6f88477c0fcf52d66287d744d40929d http://git.gnome.org/cgit/gtk+/commit/?id=3bf1c7adadb1fda69e63fc6fe0f3698d937a1b80 Since the issues are already fixed upstream I don't think a bug report is necessary. Best, -- Applications segfault with gtk+ version 2.17.2 when selecting listbox values https://bugs.launchpad.net/bugs/391398 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 71076] Preset file name is lost when using ctrl-l to change location in GtkFileChooser
Public bug reported: Binary package hint: libgtk2.0-0 Starting with gtk 2.10, the location pop up previously available via ctrl-l in a GtkFileChooser has been merged with the location bar in the main GtkFileChooser window. The problem is that it overrides the presets file name when one try to changes the location. For exemple, while one is using galeon and downloads the file super-long-file-name-that-is-painfull-to-type.txt, the save-as dialog will put : super-long-file-name-that-is-painfull-to-type.txt, highlighted in the location bar. If one types ctrl-l, then the location bar takes the focus. One can then change the current path, but once the path is set, the filename is lost and the only solution here is to type foo.txt (because the filename is long). If one does'nt want to overwrite the filename, then (s)he can starts prepending the right path to the filename but then looses the path completion via [tab]. This is a rather anoying usability issue and seems to be a regression from gtk 2.8. I reported this bug upstream but it has not been reviewed yet. ** Affects: gtk (upstream) Importance: Unknown Status: Unknown ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: Unconfirmed ** Bug watch added: GNOME Bug Tracker #357956 http://bugzilla.gnome.org/show_bug.cgi?id=357956 ** Also affects: gtk (upstream) via http://bugzilla.gnome.org/show_bug.cgi?id=357956 Importance: Unknown Status: Unknown ** Description changed: Binary package hint: libgtk2.0-0 Starting with gtk 2.10, the location pop up previously available via ctrl-l in a GtkFileChooser has been merged with the location bar in the main GtkFileChooser window. The problem is that it overrides the presets file name when one try to changes the location. For exemple, while one is using galeon and downloads the file super-long-file-name-that-is-painfull-to-type.txt, the save-as dialog will put : super-long-file-name-that-is-painfull-to-type.txt, highlighted in the location bar. If one types ctrl-l, then the location bar takes the focus. One can then change the current path, but once the path is set, the filename is lost and the only solution here is to type foo.txt (because the filename is long). If one does'nt want to overwrite the filename, then (s)he can starts prepending the right path to the filename but then looses the path completion via [tab]. This is a rather anoying usability issue and seems to be a regression from gtk 2.8. + + I reported this bug upstream but it has not been reviewed yet. -- Preset file name is lost when using ctrl-l to change location in GtkFileChooser https://launchpad.net/bugs/71076 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 70724] gedit should be able to spellcheck latex documents
Public bug reported: Binary package hint: gedit It seems that gedit spellcheker does'nt know how to skip latex commands while the underlying tools (ispell, aspell) can. This is rather annoying as gedit is the default (and suposedly unique) editor used by a new user. It should provide that feature. This could also be valuable for html or xml documents in general where tags could be skipped by the typecheker. ** Affects: gedit (upstream) Importance: Unknown Status: Unknown ** Affects: gedit (Ubuntu) Importance: Undecided Status: Unconfirmed ** Bug watch added: GNOME Bug Tracker #147160 http://bugzilla.gnome.org/show_bug.cgi?id=147160 ** Also affects: gedit (upstream) via http://bugzilla.gnome.org/show_bug.cgi?id=147160 Importance: Unknown Status: Unknown ** Description changed: Binary package hint: gedit It seems that gedit spellcheker does'nt know how to skip latex commands while the underlying tools (ispell, aspell) can. - This is rather annoying as gedit is the default (and suposedly unique) editor used by a new user. It should provide that feature. + This is rather annoying as gedit is the default (and suposedly unique) editor used by a new user. It should provide that feature. This could also be valuable for html or xml documents in general where tags could be skipped by the typecheker. -- gedit should be able to spellcheck latex documents https://launchpad.net/bugs/70724 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 69759] Re: Patch for compositing disable hibernate and suspend from logout dialog
** Tags added: aiglx hibernate suspend -- Patch for compositing disable hibernate and suspend from logout dialog https://launchpad.net/bugs/69759 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
