[Bug 1666676] Re: Enable tracker by default for Unity too
What about zeitgeist. Other things integrated with zeitgeist. So we run tracker indexing service only to recursive search in nautilus? -- 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/176 Title: Enable tracker by default for Unity too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1648992] Re: [SRU] Update gnome-calculator to 3.22.2
I did some test too, I think it is no problem, click on expression, it will replace and click on result it will append. It is designed as this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1648992 Title: [SRU] Update gnome-calculator to 3.22.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1648992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566513] Re: Complex numbers are exponentiated incorrectly
This will be fixed in this version for Ubuntu 16.10. I'm going to go ahead and close the 16.10 bug task now since it wasn't mentioned in the changelog. https://launchpad.net/ubuntu/+source/gnome- calculator/1:3.22.2-1ubuntu0.1 ** Changed in: gnome-calculator (Ubuntu Yakkety) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1566513 Title: Complex numbers are exponentiated incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1566513/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1633408] Re: [SRU] 3.22.0 wont allow cut in history pane
I verified the test cases on yakkety-proposed. By the way, this update also fixes bug 1566513. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1633408 Title: [SRU] 3.22.0 wont allow cut in history pane To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1633408/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1648992] Re: [SRU] Update gnome-calculator to 3.22.2
I verified the test cases on yakkety-proposed. The first test case results are a bit unusual, but they fix the regression so it's ok for now. (If you're curious, see the discussion at https://bugzilla.gnome.org/766155 ) ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1648992 Title: [SRU] Update gnome-calculator to 3.22.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1648992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes
Oops, sorry, this is only a duplicate of bug 1511604 if it's using Xmir. It looks like the above apps will be native GTK instead. ** Package changed: unity8 (Ubuntu) => gtk+3.0 (Ubuntu) ** Tags added: gtk-mir -- 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/1666469 Title: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes
Sorry again, this is also not a GTK bug. The windows you mention correctly implement resize constraints and I can confirm this on Unity8 17.04. So I can't reproduce the bug... Is Xmir running on your system? ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Tags added: unity8-desktop ** Tags added: resizing -- 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/1666469 Title: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666469] [NEW] [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes
You have been subscribed to a public bug: unitu 17.04 unity8 deb session [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes open a random app, open a child window (help>about or whatever), resize the window as small as it's allowed. see attached screenshot ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes https://bugs.launchpad.net/bugs/1666469 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636666] Re: [MIR] pcre2
I added an Other Info section. ** Description changed: Availability Synced with Debian. Built for all supported architectures. Rationale = Required by gnome-terminal 3.22+ and vte2.91 0.46+ Security At least one open security issue, affecting Ubuntu 16.04 LTS https://people.canonical.com/~ubuntu-security/cve/pkg/pcre2.html https://security-tracker.debian.org/tracker/source-package/pcre2 https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pcre Quality assurance = - Please subscribe Ubuntu Desktop Bugs or Ubuntu Foundation Bugs (like pcre3) to this package. https://bugs.launchpad.net/ubuntu/+source/pcre2 https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pcre2 Upstream tests are run during the build but there is no autopkgtest Does not have 3.0 (quilt) set Dependencies Only build-dependencies are dpkg and debhelper. No other added dependencies. Standards compliance 3.9.6 Maintenance === - Actively developed upstream http://pcre.org/ Background information == As the package description states, the older version of this library is confusingly named pcre3 in Debian/Ubuntu. pcre3 is already in Ubuntu main. + + Other Info + == + In the original release of pcre2 in Jan 2015, the author says this is not just a drastic update to the original pcre but a "new project". He felt free to change names and options. + https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html + + pcre3 has gotten some bugfix releases since then (from 8.36 to 8.40 + released Jan 2017) + + Some discussion of how it's different: + http://www.regular-expressions.info/pcre2.html -- 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/163 Title: [MIR] pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
Unfortunately, upstream for gnome-terminal and vte doesn't care to provide NEWS files. I said that gnome-terminal and vte hadn't changed much in the 3.24 cycle but there were changes in the 3.22 (0.46) cycle - Add systemd user service - Add Detach Terminal action to tab context menu (this is important because the ability to drag a tab out of a window was dropped in a 3.20 bug fix update but because of string freeze, this wasn't added until 3.22) - Add "gnome-terminal --preferences" to allow changing preferences if you somehow managed to break something in settings so that you can't launch gnome-terminal normally - a crash fix in the gnome-shell search provider https://git.gnome.org/browse/gnome-terminal/commit/?id=777e66d - Various appstream metadata updates 3.24, vte 0.48 - async spawning https://git.gnome.org/browse/gnome-terminal/commit/?id=d4e25a57 - There's this GNOME initiative to use "fancy quotes", even for command line output so some strings were changed for that. Here's the new vte symbols for 0.46 and 0.48 https://developer.gnome.org/vte/unstable/api-index-0-46.html https://developer.gnome.org/vte/unstable/api-index-0-48.html vte_pty_spawn_async@Base 0.47.90 vte_pty_spawn_finish@Base 0.47.90 vte_regex_error_get_type@Base 0.45.90 vte_regex_error_quark@Base 0.45.90 vte_regex_get_type@Base 0.45.90 vte_regex_jit@Base 0.45.90 vte_regex_new_for_match@Base 0.45.90 vte_regex_new_for_search@Base 0.45.90 vte_regex_ref@Base 0.45.90 vte_regex_unref@Base 0.45.90 vte_terminal_event_check_regex_simple@Base 0.45.90 vte_terminal_match_add_regex@Base 0.45.90 vte_terminal_search_get_regex@Base 0.45.90 vte_terminal_search_set_regex@Base 0.45.90 -- 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/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1665140] Re: Emoji that should be wide, according to Unicode 9, display incorrectly in the terminal
> I believe it's the distro's responsibility to ship glib, glibc and vim so that all use the same Unicode version. Sounds right, and it's good to hear that there's progress on this front. I was afraid the situation was stagnant and it would be up to applications to fix it. > Or even better, but it takes more time and a heavy refactoring: There should be a single core Unicode library that glibc, glib, vim etc. all depend on. Unfortunately I find it unlikely to get implemented. Working a lot with Unicode myself, the thing is that the number of things a Unicode library could do is enormous and no application needs all of them. Many developers consider linking to, for example, ICU to be unacceptable bloat, and I don't blame them. > Also note that in gnome-terminals' Profile Preferences, under the Compatibility tab you can choose whether you want ambiguous width characters to be narrow or wide. I wouldn't want to set *all* ambiguous characters to be wide, like a Japanese OS -- that would break many more things. It's only the emoji that changed. Thanks for the responses. -- 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/1665140 Title: Emoji that should be wide, according to Unicode 9, display incorrectly in the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1665140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666681] Re: Drop interactive_search.patch (type-ahead search)
Hey all, As Jeremy mentioned, I think it's the best idea to drop this patch and use the default search utility of Nautilus. For users - One of my main interests in the last 4 releases was to improve this situation, whether search doesn't replace the use cases of type ahead. We iterated on it and made several improvements: - Searches on the current folder are done with priority - Performance have been improved in several ways - Result of the current folder are clearly differentiated by not displaying the "Original Location" - We switch by default to list view when searching, so the locations or the file are clearly shown - We added a preference for permanently search recursively or only in the current folder. - The view used while searching can be changed independently of the default view when not searching. - Using tracker, search in most common folders is immediate. I believe all except one use case is covered in the current search, taking into account lag and performance too. The use case that is not covered is when the user wants to navigate to a folder that it's close to a name. For instance user wants "Pictures" folder and user searches for "Osomething", so most probably the next folder by alphabetical order is "Pictures". However I believe this is easily replaced by just searching for "Pictures" or "Osomething" and then right click -> open item location which opens the folder (it can be the current one) and selects the file, effectively replacing type ahead (again if tracker is enabled so lag is not an issue). We are still interested in evolving this more, and we are open to feedback and making the effort on improving the situation as long as it can fit, and doesn't clash, with our vision for search. For developers of Ubuntu The code on nautilus-window-slot and nautilus views is extremely delicate. You really need to understand all the interactions that happens under it to be able to modify the code expecting any reliability. Needless to say the patch that is currently used is missing this reliability, receiving crashes both in Ubuntu and upstream where we don't even know why this happen. Also this code has been refactored several times in the past, because it needed to, and it will be more refactored in the future. You will need to update the patch every release without exception, which I don't think is the best investment for Ubuntu if they are going to replace everything with Unity 8. So current situation is a lose-lose, trying to be as impartial as possible, I think using directly what upstream is using is the best solution for both parties, and even more in this part of the code. One thing to clarify, as Jeremy mentioned, this doesn't make sense without tracker, and if the decision is to not adopt tracker, I would recommend to keep the downstream patch. -- 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/181 Title: Drop interactive_search.patch (type-ahead search) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666681] Re: Drop interactive_search.patch (type-ahead search)
** Description changed: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type-ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. - Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. + + The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with + this patch now disabled. + + https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty -- 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/181 Title: Drop interactive_search.patch (type-ahead search) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666676] Re: Enable tracker by default for Unity too
** Description changed: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted - the removal of that feature by Nautilus years ago. + the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch -- 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/176 Title: Enable tracker by default for Unity too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666681] [NEW] Drop interactive_search.patch (type-ahead search)
Public bug reported: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type-ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Description changed: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type-ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. + + + Other Items + === + - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) + + - There is an option in Preferences for users to disable searching in + subfolders. I don't think we want to do that by default but maybe it can + help some people. -- 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/181 Title: Drop interactive_search.patch (type-ahead search) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666676] [NEW] Enable tracker by default for Unity too
Public bug reported: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666635] Re: gvfsd-smb-browse crashed with SIGABRT in _talloc_free()
*** This bug is a duplicate of bug 1546463 *** https://bugs.launchpad.net/bugs/1546463 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1546463, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/135/+attachment/4823570/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/135/+attachment/4823572/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/135/+attachment/4823574/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/135/+attachment/4823575/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/135/+attachment/4823576/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/135/+attachment/4823577/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/135/+attachment/4823578/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1546463 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/135 Title: gvfsd-smb-browse crashed with SIGABRT in _talloc_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1661371] Re: [zesty] doesn't offer a window to install missing gstreamer codecs
** Also affects: sessioninstaller Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1661371 Title: [zesty] doesn't offer a window to install missing gstreamer codecs To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1661371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
I'm not seeing a compelling reason to switch to 3.24 and the newer vte other than the version bump. If your argument is that after this revert, both gnome-terminal and vte are effectively identical feature-wise as what we have in the archive right now, then you're not introducing or removing features, in which case you don't need a Feature Freeze Exception in the first place. If this change does introduce/remove features to gnome-terminal and vte, please list them in a readable format (not an upstream git log/diff). I think the pcre2 MIR could do with an API diff between pcre3 and pcre2. Your massive patch suggests that the two APIs are very much different and that it's not something we can do as a typical transition, making the need for both of them to live in main together much clearer. -- 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/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666563] [NEW] /lib/systemd/systemd-journald:6:__GI__IO_default_xsputn:_IO_vfprintf_internal:__GI___vasprintf_chk:__asprintf_chk:asprintf
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 231-9ubuntu1, the problem page at https://errors.ubuntu.com/problem/c5bcb149ef4918afa612583d48612867d6b6ea6f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: vivid xenial yakkety -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1666563 Title: /lib/systemd/systemd- journald:6:__GI__IO_default_xsputn:_IO_vfprintf_internal:__GI___vasprintf_chk:__asprintf_chk:asprintf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1666563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1664529] Re: Please merge gedit 3.22.0-1ubuntu2 (main) from Debian unstable (main)
** Attachment added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1664529/+attachment/4823495/+files/debdiff -- 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/1664529 Title: Please merge gedit 3.22.0-1ubuntu2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1664529/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1655779] Re: udev deletes and recreates partition devices when the disk is opened r/w
** Package changed: udev (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1655779 Title: udev deletes and recreates partition devices when the disk is opened r/w To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1655779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1665602] Re: nautilus no thumbnails for .jpg and .png
Also thumbnails for .pdf are ok and for video .webm e .mp4 -- 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/1665602 Title: nautilus no thumbnails for .jpg and .png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1665602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
On Tue, Feb 21, 2017 at 01:00:02PM -, Jeremy Bicha wrote: > I don't like the revert idea either. > > But like I pointed out almost 4 months ago, there are just 3 options, right? > 1. Accept PCRE2 in main > 2. Keep gnome-terminal at 3.20 and vte at 0.44 indefinitely > 3. Revert the PCRE2 changes, which allows postponing a choice between the > first two. > > I don't think #2 is better for maintainability than #3 really (We've > done that with other packages before and it means that Ubuntu will only > get a handful of bugfixes. Long term, it means we'll have created a > mostly dead fork and I'm not convinced we had a good enough reason to do > that. #3 is a fork too but it won't be as dead as quickly.) > > I really think #1 is the right answer here but if we go with #3, we can > keep ignoring the MIR for several more months. I'm sure there will be some point at which there will be a compelling reason to upgrade. I just don't think we're there yet, and I think we'll be able to maintain 3.20 for another (9 month) release without getting into a potentially difficult situation with a complicated revert. There will also definitely be a point at which some other upstream switches off the dead branch of PCRE, and we get to have this fight with two programs on one side rather than one. That is, if you revert, then the patches will have to be removed. If we're on 3.20 then we'll have to upgrade. Either way, the situation we will have in Zesty will not be around forever. So I think I'm out of arguments. Sorry for not being convinced. If any other release team member is reading this and wants to weigh in, feel free. BTW I think we (Ubuntu as a whole) should push more on the PCRE transition in the next cycle in any event. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1662101] Re: Please merge pygtk 2.24.0-5.1 (main) from Debian unstable (main)
** Attachment added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1662101/+attachment/4823494/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1662101 Title: Please merge pygtk 2.24.0-5.1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1662101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1655779] [NEW] udev deletes and recreates partition devices when the disk is opened r/w
You have been subscribed to a public bug: Description:Ubuntu 16.04.1 LTS Release:16.04 parted: 3.2-15 gparted: 0.25.0-1 Applications that utilized parted/libparted to probe for block device information disable the read only status during the probe. Example: Set a block device read only using either hdparm -r1 /dev/sdc* or blockdev --setro /dev/sdc*: # hdparm -r1 /dev/sdc* /dev/sdc: readonly = 1 (on) /dev/sdc1: readonly = 1 (on) Run gparted Check the readonly status with hdparm: # hdparm -r /dev/sdc* /dev/sdc: readonly = 0 (off) /dev/sdc1: readonly = 0 (off) The read only status has changed to off. This can be replicated using partprobe: Set a block device read only using either hdparm -r1 /dev/sdc*: # hdparm -r1 /dev/sdc* /dev/sdc: readonly = 1 (on) /dev/sdc1: readonly = 1 (on) Probe the devices using partprobe -s: # partprobe -s /dev/sda: msdos partitions 1 2 3 /dev/sdb: gpt partitions 1 2 3 5 4 /dev/sdc: msdos partitions 1 Recheck the read only status: # hdparm -r /dev/sdc* /dev/sdc: readonly = 0 (off) /dev/sdc1: readonly = 0 (off) As before the read only status has been switched off. Again, this can be replicated using parted: Set a block device read only using either hdparm -r1 /dev/sdc*: # hdparm -r1 /dev/sdc* /dev/sdc: readonly = 1 (on) /dev/sdc1: readonly = 1 (on) List the partition layout using parted -l: # parted -l . . Model: WDC WD10 EFRX-68JCSN0 (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End SizeType File system Flags 1 1049kB 1000GB 1000GB primary ntfs Recheck the read only status: # hdparm -r /dev/sdc* /dev/sdc: readonly = 0 (off) /dev/sdc1: readonly = 0 (off) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- udev deletes and recreates partition devices when the disk is opened r/w https://bugs.launchpad.net/bugs/1655779 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1272461] Re: djvu search doesn't list results
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- 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/1272461 Title: djvu search doesn't list results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1272461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666545] [NEW] package libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: unsure of what is the issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Feb 21 08:22:24 2017 DuplicateSignature: package:libpam-gnome-keyring:amd64:3.18.3-0ubuntu2 Setting up libpaper1:amd64 (1.1.24+nmu4ubuntu1) ... dpkg: error processing package libpaper1:amd64 (--configure): subprocess installed post-installation script was killed by signal (Broken pipe) ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-02-17 (4 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: gnome-keyring Title: package libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1666545 Title: package libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1666545/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666545] Re: package libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1666545 Title: package libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1666545/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1589585] Re: Ubuntu Software tab Installed refreshing endlessly every 2 seconds
** Changed in: gnome-software (Ubuntu) Status: Triaged => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1589585 Title: Ubuntu Software tab Installed refreshing endlessly every 2 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1589585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1665140] Re: Emoji that should be wide, according to Unicode 9, display incorrectly in the terminal
Just for the record: glibc has just upgraded to Unicode 9.0 in git (forthcoming 2.26 release): https://sourceware.org/bugzilla/show_bug.cgi?id=20313 ** Bug watch added: Sourceware.org Bugzilla #20313 https://sourceware.org/bugzilla/show_bug.cgi?id=20313 -- 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/1665140 Title: Emoji that should be wide, according to Unicode 9, display incorrectly in the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1665140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1641629] Re: Autocomplete popups are misplaced
Ok, that's probably two separate bugs. I have a 100% reproducible scenario in Firefox, even with a single monitor, on an up to date, freshly booted 17.04: 1. Go to https://yoast.com/research/autocompletetype.php 2. Don't input anything and press Submit your name. An extended form appears, with fields for name, email, and more 3. Start typing your name in the name field. The autocomplete menu pops up and shows several alternatives (assuming you have some autocomplete values registered). Do not select anything, but instead keep typing random letters until there is no autocomplete match and the autocomplete menu disappears. 4. Go to the email field, and type the first letter of your email (assuming your email is registered as an autocomplete value) Result: the autocomplete menu appears, but it is anchored to the name field, not the email field. Moreover, it is out of sync with the mouse position (it behaves as it it was at the correct position, therefore the highlighted item does not match the mouse position). If in step 3 you choose an autocomplete entry instead of typing random stuff and having the menu disappear, the problem does not occur. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1641629 Title: Autocomplete popups are misplaced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1641629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
I don't like the revert idea either. But like I pointed out almost 4 months ago, there are just 3 options, right? 1. Accept PCRE2 in main 2. Keep gnome-terminal at 3.20 and vte at 0.44 indefinitely 3. Revert the PCRE2 changes, which allows postponing a choice between the first two. I don't think #2 is better for maintainability than #3 really (We've done that with other packages before and it means that Ubuntu will only get a handful of bugfixes. Long term, it means we'll have created a mostly dead fork and I'm not convinced we had a good enough reason to do that. #3 is a fork too but it won't be as dead as quickly.) I really think #1 is the right answer here but if we go with #3, we can keep ignoring the MIR for several more months. -- 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/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
** Tags removed: verification-needed ** Tags added: verification-done -- 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/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
Oh come on, there's no hive mind conspiracy against you here, you know that. It's individual developers answering questions that are asked of them and giving you their own judgement. If you'd have asked me before starting this work then I would have given the same answer ("do it only if the other changes make it worthwhile [and maybe consider cherry- picking those first if possible]"). The concern is this - Big revert patch - Can never drop it as long as we don't move to PCRE 2 - Gets harder to maintain over time - No clear path to moving to PCRE 2 - Given that, does having the new releases bring features and/or fixes that mean we should take on these difficulties or is this just taking on an unknown amount of work indefinitely just to have a larger number in the version string? That is a *question*, not an accusation. Or are you saying that I shouldn't be allowing these considerations to weigh into Feature Freeze requests, since the net change of *this* upload will be small? Maybe that's fair and if that's the case then it means I'm answering as a fellow desktop team member, not as someone in the release team. In that case, your two ways to get this upload (three if you count 'ignore me and upload anyway' as one) are - Provide an explanation that this upload is worth the above future difficulties - Show that the net change is small and convince another member of the release team to +1 this request -- 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/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636514] Re: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()
Same problem moving file in an owncloud folder -- 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/1636514 Title: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1636514/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
Isn't that the opposite of how Feature Freeze Exception requests go, that it should be more likely to be accepted if there are *not* many changes? Yesterday, it was reported that Ubuntu will have GNOME 3.24. And the first thing a GNOME packager for another distro said was well it isn't really GNOME 3.24 if you don't have *all* of it. Now my first choice is that the MIR for PCRE2 be approved and I've been disappointed in how bug 163 has been handled so far. I got the impression I was being told to try to revert the PCRE2 stuff in vte/gnome-terminal (since trying to port everything in main to PCRE2 is an unreasonable request). So it would be frustrating after I do the work if the answer is both No to the MIR and No to doing the update with the reverts. I believe the reverts are safe for zesty; my maintainability concerns are more about maybe a year from now when the code has drifted more. -- 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/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
On Mon, Feb 20, 2017 at 06:15:21PM -, Jeremy Bicha wrote: > ** Changed in: vte2.91 (Ubuntu) >Importance: Undecided => Low > > ** Description changed: > > gnome-terminal and vte are still at their 3.20 (and 0.44) versions > because they now hard-depend on pcre2, but the pcre2 MIR (LP: #163) > has stalled because there is already one version of pcre in main and it > would be a major task to convert all of main to use pcre2. > > So I reverted 3 commits for gnome-terminal and 5 for vte to make that > MIR less urgent. I am concerned about the long-term maintainability of > this approach - the vte patch is over 1600 lines. > > gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3 Staging > PPA for yakkety and zesty for months. I am not aware of any issues from > that. This is slightly different since I haven't tested those versions > without pcre2 until this weekend. > > The development cycle for gnome-terminal and vte has been fairly quiet > so I believe it's safe to go ahead and update gnome-terminal to 3.23.90 > and vte to 0.47.90. If there aren't many changes (other than porting to PCRE2), what's the proposed upside of getting onto the new versions? It seems risky and annoying to maintain such a patch going forward - it's only going to become harder to keep it working as time goes on, until we get to drop it. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637638] Re: Gnome Software causes heavy prolonged disk on start-up
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1637638 Title: Gnome Software causes heavy prolonged disk on start-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1637638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637638] Re: Gnome Software causes heavy prolonged disk on start-up
Hi ! Exact same issue on Ubuntu 16.10 On every start, I must wait about 1 minute before being able to open a single xterm. iotop gives exact same result : gnome-software --gapplication-service is having heavy disk access. Once finished, the system gets back to normal reactivity. Really annoying on harddrive laptop. Is there a known workaround to stop this ? Thanks ! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1637638 Title: Gnome Software causes heavy prolonged disk on start-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1637638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 792085] Re: Automatic remount of safely removed USB 3.0 drive
I can also confirm fix after upgrading from something older to 4.4.0-63-generic. Thanks to everybody who was involved bringing the solution! Best wishes, Martin. -- 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/792085 Title: Automatic remount of safely removed USB 3.0 drive To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/792085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1661568] Re: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property
This bug was fixed in the package systemd - 232-18ubuntu1 --- systemd (232-18ubuntu1) zesty; urgency=medium [ Martin Pitt ] * debian/README.source: Update patch and changelog handling to current reality. We've used gbp dch for a fair while now, let's document it as official policy. Update documentation about patch handling: using quilt directly is not really "welcome" any more as it creates a lot of noise in pq, so only document pq now. Also document the usage of topic branches, and our shiny debian/git-cherry-pick tool. [ Dimitri John Ledkov ] * Fix resolved failing to follow CNAMES for DNS stub replies (LP: #1647031) * Fix emitting change signals with a sessions property in logind. (LP: #1661568) systemd (232-18) unstable; urgency=medium * udev autopkgtest: Adjust to script-based test /sys creation. PR #5250 changes from the static sys.tar.xz to creating the test /sys directory with a script. Get along with both cases until 233 gets released and packaged. * systemd-resolved.service.d/resolvconf.conf: Don't fail if resolvconf is not installed. ReadWritePaths= fails by default if the referenced directory does not exist. This happens if resolvconf is not installed, so use '-' to ignore the absence. (Closes: #854814) * Fix two more seccomp issues. * Permit seeing process list of units whose unit files are missing. * Fix systemctl --user enable/disable without $XDG_RUNTIME_DIR being set. (Closes: #855050) -- Dimitri John LedkovThu, 16 Feb 2017 22:33:24 + ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1661568 Title: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661568/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666435] Re: GTK apps have wrong font/thickness/hinting under Unity8
** Changed in: unity8 (Ubuntu) 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/1666435 Title: GTK apps have wrong font/thickness/hinting under Unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666435] [NEW] GTK apps have wrong font/thickness/hinting under Unity8
Public bug reported: GTK apps have wrong font/thickness/hinting under Unity8 (compared to Unity7 where they look much better). ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Affects: unity8-desktop-session (Ubuntu) Importance: Undecided Status: New ** Tags: gtk-mir unity8-desktop visual-quality ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8-desktop-session (Ubuntu) Importance: Undecided Status: New -- 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/1666435 Title: GTK apps have wrong font/thickness/hinting under Unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs