[Desktop-packages] [Bug 1650395] Re: Large grey border around gnome-terminal shadows when transparency is enabled (wayland)
Great news! Glad to hear it! I was surprised to see this issue still around. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1650395 Title: Large grey border around gnome-terminal shadows when transparency is enabled (wayland) Status in Ubuntu GNOME: Triaged Status in gnome-terminal package in Ubuntu: Fix Released Status in gnome-terminal source package in Zesty: Triaged Status in gnome-terminal source package in Bionic: Fix Released Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22, that there is a large strange grey border around the window: - Fullscreen_gnome-terminal_in_AO_no_strange_border.png - Fullscreen_gnome-terminal_window.png - gnome-terminal_in_AO_strange_border.png - gnome-terminal_window_strange_border.png But this only occurs when the window is not fullscreen, and when transparency is enabled. Turning transparency off immediately fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 15 21:29:17 2016 InstallationDate: Installed on 2016-05-15 (214 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-19 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495479] Re: Strange dimming effect when setting sRGB image as desktop background image and activating desktop icons
Well, on Arch the issue, (as I said before) doesn't seem to be present. However can't you just check yourself? It should be quite easy to reproduce if it's still a bug. If it is, then as it says "Fix released" for the upstream bug, then surely you can fix it downstream as well. And if not, then we can close the bug! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1495479 Title: Strange dimming effect when setting sRGB image as desktop background image and activating desktop icons Status in GNOME Shell: Fix Released Status in One Hundred Papercuts: Incomplete Status in Ubuntu GNOME: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have recently noticed that when setting sRGB images as the desktop image, and having the desktop icons active (gsettings set org.gnome.desktop.background show-desktop-icons true) that there is a strange dimming effect, so I turn my machine on, log on, and then I see my image normally for a few seconds, then suddenly it is dimmed and stays like that, there are only a few seconds on login that I can then see it normally for. But I find that if I set desktop icons to inactive (gsettings set org.gnome.desktop.background show-desktop-icons false) that the problem goes away until I reactivate them, in which case the immediate moment that I turn them back on in the settings the desktop image dims. However this does not occur with just normal RGB or PNG images. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gdm 3.16.1.1-0ubuntu1~vivid2 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 14 12:34:32 2015 InstallationDate: Installed on 2015-07-29 (47 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1495479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650395] Re: Large grey border around gnome-terminal shadows when transparency is enabled (wayland)
@Robie, I run Arch now, so it would be best if someone else tested this, otherwise if nobody is around other than me to test it then I will happily do so in my QEMU VM. Just let me know if nobody gets back to you about this in a while. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1650395 Title: Large grey border around gnome-terminal shadows when transparency is enabled (wayland) Status in Ubuntu GNOME: Triaged Status in gnome-terminal package in Ubuntu: Fix Released Status in gnome-terminal source package in Zesty: Triaged Status in gnome-terminal source package in Bionic: Fix Committed Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22, that there is a large strange grey border around the window: - Fullscreen_gnome-terminal_in_AO_no_strange_border.png - Fullscreen_gnome-terminal_window.png - gnome-terminal_in_AO_strange_border.png - gnome-terminal_window_strange_border.png But this only occurs when the window is not fullscreen, and when transparency is enabled. Turning transparency off immediately fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 15 21:29:17 2016 InstallationDate: Installed on 2016-05-15 (214 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-19 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1614925] Re: Allow one to set the week to start on Sunday in built-in calendar
The upstream bug reports have been moved to: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/160, https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/75 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1614925 Title: Allow one to set the week to start on Sunday in built-in calendar Status in GNOME Calendar: Expired Status in GNOME Tweaks: Expired Status in Ubuntu GNOME: Confirmed Status in gnome-calendar package in Ubuntu: Confirmed Status in gnome-tweaks package in Ubuntu: Triaged Bug description: Some religious as well as regional calendars (e.g.: the Japanese calendar) start the week with Sunday as opposed to Monday. I think that there should be an option in the gnome-tweak-tool to make it so that the weeks are displayed as starting on Sunday in the built-in calendar accessible from the top-bar. This can already be done manually, but an option in the GUI would be nice. Upstream: https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/75 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1614925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686044] Re: Allow the enable of two-finger-scrolling and edge-scrolling at the same time
** Bug watch added: GNOME Bug Tracker #761461 https://bugzilla.gnome.org/show_bug.cgi?id=761461 ** Changed in: gnome-control-center Importance: Wishlist => Unknown ** Changed in: gnome-control-center Status: Invalid => Unknown ** Changed in: gnome-control-center Remote watch: GNOME Bug Tracker #781699 => GNOME Bug Tracker #761461 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1686044 Title: Allow the enable of two-finger-scrolling and edge-scrolling at the same time Status in gnome-control-center: Fix Released Status in Ubuntu GNOME: New Status in gnome-control-center package in Ubuntu: New Bug description: I find both two-finger-scrolling and edge-scrolling quite useful in different circumstances, so I think it would be quite nice if I could have both enabled at the same time through the gnome-control-center. Currently selecting one in the Mouse & Touchpad settings deselects the other. As can be seen here there is some demand for a feature like this: https://askubuntu.com/questions/248290/enable-both-edge-scrolling-and- two-finger-scrolling-for-touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1686044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1539289] Re: Divisory line at the top partly disappears in certain cases
I no longer use Ubuntu, I'm on Arch so I don't know for sure. But it's not happening over here with GNOME 3.26.3 so I assume that the issue has probably gone. ** Changed in: ubuntu-gnome Status: New => Invalid ** Changed in: gnome-system-monitor (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1539289 Title: Divisory line at the top partly disappears in certain cases Status in Ubuntu GNOME: Invalid Status in gnome-system-monitor package in Ubuntu: Invalid Bug description: I have recently noticed that for instance if I open the System Monitor and have it so that it takes up half of my screen on one of the sides the top divisory line looks normal like this: System_Monitor_Screenshot1.png However if I then switch to the "Processes" tab this happens: System_Monitor_Screenshot2.png Then if I drag the window to the top of the screen and make it go fullscreen that way then the line disappears entirely: System_Monitor_Screenshot3.png And then if I go to the "Resources" tab the line becomes only in the centre and in a strange pattern off to the right in some cases: System_Monitor_Screenshot4.png Finally, if I I drag it away anywhere it becomes normal again. I am using the pre-installed Numix theme. --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily Flavour: GNOME GNOME Version: 3.18 Package Information: gnome-system-monitor: Installed: 3.18.2-1~wily1 Candidate: 3.18.2-1~wily1 Version table: *** 3.18.2-1~wily1 0 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 3.16.0-2 0 500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1539289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569857] Re: Show installation and uninstallation history
** Description changed: I much prefer GNOME Software to the Ubuntu Software Center, however I believe that there is one thing lacking in GS which is present in USC, the installation and uninstallation history. That is, the history of all packaged which have been installed and uninstalled, I believe that this is a very important feature for any software center like application to have and GS users would benefit from it. + + Upstream: https://gitlab.gnome.org/GNOME/gnome-software/issues/51 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1569857 Title: Show installation and uninstallation history Status in GNOME Software: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-software package in Ubuntu: Triaged Bug description: I much prefer GNOME Software to the Ubuntu Software Center, however I believe that there is one thing lacking in GS which is present in USC, the installation and uninstallation history. That is, the history of all packaged which have been installed and uninstalled, I believe that this is a very important feature for any software center like application to have and GS users would benefit from it. Upstream: https://gitlab.gnome.org/GNOME/gnome-software/issues/51 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1569857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652272] Re: Firefox suddenly loses internet connection
If anybody else still experiences this issue I would recommend that they file a new bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1652272 Title: Firefox suddenly loses internet connection Status in Mozilla Firefox: Invalid Status in Ubuntu GNOME: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Since earlier today I have found that after about 10 minutes or less of using Firefox that suddenly for no apparent reason pages will refuse to load any contents, and although Firefox does not take me to the page which says it can't reach the site, it doesn't manage to load anything as though its internet connection has suddenly been lost. It won't even let me check for updates for plugins and gives an error for that. I have tested with other applications such as ping and the internet connection is fine, it's just Firefox which loses it. I have noticed that when I run firefox from Terminal that this is the output to begin with: 1482487989643 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest. 1482487989708 addons.webextension.fire...@ghostery.comWARN Please specify whether you want browser_style or not in your browser_action options. Promise resolved after context unloaded Then when the problem starts to occur, I find that the only way to resolve it, if even for a short period, is to restart the browser, so I tell Firefox to quit, however although the window does close, the process carries on and this is the output: tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. console.error: Message: Error: SessionFile is closed Stack: SessionFileInternal.write@resource://app/modules/sessionstore/SessionFile.jsm:315:29 this.SessionFile.write@resource://app/modules/sessionstore/SessionFile.jsm:76:12 SessionSaverInternal._writeState@resource://app/modules/sessionstore/SessionSaver.jsm:259:12 SessionSaverInternal._saveState@resource://app/modules/sessionstore/SessionSaver.jsm:230:12 SessionSaverInternal._saveStateAsync@resource://app/modules/sessionstore/SessionSaver.jsm:243:5 SessionSaverInternal.runDelayed/this._timeoutID<@resource://app/modules/sessionstore/SessionSaver.jsm:147:40 setTimeout_timer@resource://gre/modules/Timer.jsm:30:5 ExceptionHandler::GenerateDump cloned child 12324 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... I am then told that Firefox crashed and asked if I would like to submit a report, so far I have told it to submit a report three times as the crash has occurred that number of times. For that entire period of time this is the output from Firefox in syslog: Dec 23 10:00:42 firefox.desktop[11349]: 1482487242751#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242778#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error
[Desktop-packages] [Bug 1652272] Re: Firefox suddenly loses internet connection
This bug was somehow fixed a long time ago with one of the new versions of Firefox. ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ubuntu-gnome Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1652272 Title: Firefox suddenly loses internet connection Status in Mozilla Firefox: Invalid Status in Ubuntu GNOME: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Since earlier today I have found that after about 10 minutes or less of using Firefox that suddenly for no apparent reason pages will refuse to load any contents, and although Firefox does not take me to the page which says it can't reach the site, it doesn't manage to load anything as though its internet connection has suddenly been lost. It won't even let me check for updates for plugins and gives an error for that. I have tested with other applications such as ping and the internet connection is fine, it's just Firefox which loses it. I have noticed that when I run firefox from Terminal that this is the output to begin with: 1482487989643 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest. 1482487989708 addons.webextension.fire...@ghostery.comWARN Please specify whether you want browser_style or not in your browser_action options. Promise resolved after context unloaded Then when the problem starts to occur, I find that the only way to resolve it, if even for a short period, is to restart the browser, so I tell Firefox to quit, however although the window does close, the process carries on and this is the output: tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. console.error: Message: Error: SessionFile is closed Stack: SessionFileInternal.write@resource://app/modules/sessionstore/SessionFile.jsm:315:29 this.SessionFile.write@resource://app/modules/sessionstore/SessionFile.jsm:76:12 SessionSaverInternal._writeState@resource://app/modules/sessionstore/SessionSaver.jsm:259:12 SessionSaverInternal._saveState@resource://app/modules/sessionstore/SessionSaver.jsm:230:12 SessionSaverInternal._saveStateAsync@resource://app/modules/sessionstore/SessionSaver.jsm:243:5 SessionSaverInternal.runDelayed/this._timeoutID<@resource://app/modules/sessionstore/SessionSaver.jsm:147:40 setTimeout_timer@resource://gre/modules/Timer.jsm:30:5 ExceptionHandler::GenerateDump cloned child 12324 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... I am then told that Firefox crashed and asked if I would like to submit a report, so far I have told it to submit a report three times as the crash has occurred that number of times. For that entire period of time this is the output from Firefox in syslog: Dec 23 10:00:42 firefox.desktop[11349]: 1482487242751#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242778#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]:
[Desktop-packages] [Bug 1614925] Re: Allow one to set the week to start on Sunday in built-in calendar
** Description changed: Some religious as well as regional calendars (e.g.: the Japanese calendar) start the week with Sunday as opposed to Monday. I think that there should be an option in the gnome-tweak-tool to make it so that the weeks are displayed as starting on Sunday in the built-in calendar accessible from the top-bar. This can already be done manually, but an option in the GUI would be nice. + + Upstream: https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/75 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1614925 Title: Allow one to set the week to start on Sunday in built-in calendar Status in GNOME Calendar: Expired Status in gnome-tweak-tool: Expired Status in Ubuntu GNOME: Confirmed Status in gnome-calendar package in Ubuntu: Confirmed Status in gnome-tweak-tool package in Ubuntu: Triaged Bug description: Some religious as well as regional calendars (e.g.: the Japanese calendar) start the week with Sunday as opposed to Monday. I think that there should be an option in the gnome-tweak-tool to make it so that the weeks are displayed as starting on Sunday in the built-in calendar accessible from the top-bar. This can already be done manually, but an option in the GUI would be nice. Upstream: https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/75 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1614925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
I hadn't noticed this bug in a while. And then suddenly yesterday (on Arch Linux) it appeared! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: In Progress Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Committed Status in gnome-shell package in Debian: Confirmed Status in gnome-shell package in Fedora: In Progress Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744465] Re: After emptying the search box with "Clear Search History" pressing Esc restores search box contents
This bug has been verified upstream. ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-gnome Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1744465 Title: After emptying the search box with "Clear Search History" pressing Esc restores search box contents Status in Mozilla Firefox: New Status in Ubuntu GNOME: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: In the search box (not the URL bar) I have noticed that if I enter some text, for instance if I put the word "sausage" in there, and then I right-click on the box and click "Clear Search History" that it also clears the text in the search box. If I click off the search box it stays blank. However if I (without clicking off it) press the Esc key, then the word "sausage" (or whatever was there) is restored. I think if you're going to clear the text box of its contents when somebody clicks the clear history button, that you should allow pressing Esc to just restore it. It's strange and inconsistent. I am running an up-to-date installation of Ubuntu 17.10 and Firefox version 57.0.4. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1744465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744465] [NEW] After emptying the search box with "Clear Search History" pressing Esc restores search box contents
Public bug reported: In the search box (not the URL bar) I have noticed that if I enter some text, for instance if I put the word "sausage" in there, and then I right-click on the box and click "Clear Search History" that it also clears the text in the search box. If I click off the search box it stays blank. However if I (without clicking off it) press the Esc key, then the word "sausage" (or whatever was there) is restored. I think if you're going to clear the text box of its contents when somebody clicks the clear history button, that you should allow pressing Esc to just restore it. It's strange and inconsistent. I am running an up-to-date installation of Ubuntu 17.10 and Firefox version 57.0.4. ** Affects: firefox Importance: Unknown Status: Unknown ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Mozilla Bugzilla #1431923 https://bugzilla.mozilla.org/show_bug.cgi?id=1431923 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1431923 Importance: Unknown Status: Unknown ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1744465 Title: After emptying the search box with "Clear Search History" pressing Esc restores search box contents Status in Mozilla Firefox: Unknown Status in Ubuntu GNOME: New Status in firefox package in Ubuntu: New Bug description: In the search box (not the URL bar) I have noticed that if I enter some text, for instance if I put the word "sausage" in there, and then I right-click on the box and click "Clear Search History" that it also clears the text in the search box. If I click off the search box it stays blank. However if I (without clicking off it) press the Esc key, then the word "sausage" (or whatever was there) is restored. I think if you're going to clear the text box of its contents when somebody clicks the clear history button, that you should allow pressing Esc to just restore it. It's strange and inconsistent. I am running an up-to-date installation of Ubuntu 17.10 and Firefox version 57.0.4. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1744465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1528915] Re: Allow changing of the top panel's colour and transparency levels without need to install extension - feature request
@Dave, Yes, I know, that's the one I'm referring to in my bug description (in fact it's quite obvious from the title of the bug). I meant that I was requesting for this functionality to be built-in rather than having to install the extension. Anyway, this bug is almost 2 -years-old, and I'm on Arch now so you Ubuntu can do what you want with it. But it should be noted that there has been a little upstream activity on the bug so maybe this will get implemented in at least a similar way to the way I requested. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1528915 Title: Allow changing of the top panel's colour and transparency levels without need to install extension - feature request Status in gnome-control-center: Won't Fix Status in Ubuntu GNOME: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Currently if one wants to change the colour or transparency levels of the top panel they have to install an extension, I think that this functionality should be built-in so that one can just change these settings in the gnome-control-center rather than having to install some third-party extension. I am running Ubuntu GNOME 15.10 with GNOME 3.18. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1528915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609009] Re: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead)
@Marius, This could still be done as a downstream patch and they haven't rejected that yet so there's no reason to close it as just "Opinion", in fact it would make more sense for them to close this as "Won't fix" because really "Opinion" refers to something completely different. I must admit that after looking at the description given for this option it does look like it's at least very close, but I've always been told that this is not what the option is for when others use it on my bugs. ** Changed in: ubuntu-gnome Status: Opinion => Confirmed ** Changed in: gnome-terminal (Ubuntu) Status: Opinion => Confirmed ** Changed in: vte2.91 (Ubuntu) Status: Opinion => Confirmed ** Changed in: ubuntu-gnome Status: Confirmed => New ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => New ** Changed in: vte2.91 (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1609009 Title: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead) Status in Ubuntu GNOME: New Status in Gnome Virtual Terminal Emulator: Won't Fix Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: I would find it rather useful, especially with certain types of outputs, if gnome-terminal would allow me to disable text wrapping, that is so that there would be a horizontal scroll bar that would allow me to see the rest of the text. I don't know if this should/would include the commands you type it, but maybe there could be a separate option for the wrapping of that. There are other Terminals which support this, and I think it would be really nice if gnome-terminal would too so that one doesn't have to put all of the output into another program like 'less' or similar in order to disable the wrapping. I am running Ubuntu GNOME 16.04 with GNOME 3.20 and would find this a very useful feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1609009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1528915] Re: Allow changing of the top panel's colour and transparency levels without need to install extension - feature request
@James, No, you misunderstand what I mean, I just mean the black, not all the icons and everything: ** Attachment added: "Screenshot from 2017-11-06 11-15-57.png" https://bugs.launchpad.net/ubuntu-gnome/+bug/1528915/+attachment/5004604/+files/Screenshot%20from%202017-11-06%2011-15-57.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1528915 Title: Allow changing of the top panel's colour and transparency levels without need to install extension - feature request Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Currently if one wants to change the colour or transparency levels of the top panel they have to install an extension, I think that this functionality should be built-in so that one can just change these settings in the gnome-control-center rather than having to install some third-party extension. I am running Ubuntu GNOME 15.10 with GNOME 3.18. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1528915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with non-English/non-Latin input source
It should be noted that I'm on Arch though so I may not be able to be so helpful with this bug report any more. However we do have Anthy here and the same issue. But I do remember experiencing on Ubuntu what the other bug you link is describing. ** Changed in: ubuntu-gnome Status: Incomplete => Confirmed ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Tags added: artful ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1566357 Title: Unable to type passwords with non-English/non-Latin input source Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I recently found that I am unable to type using the "Japanese (Anthy)" input source in password fields in gnome-shell. That is I am unable to type using it (I just get English) on the login screen in the password field (though I haven't tried the username field), I am unable to type using it in the graphical prompts for authentication, and I am unable to type using it when setting a new password through the gnome- control-center. I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well as with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1566357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with non-English/non-Latin input source
@Daniel, It looks the same to me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1566357 Title: Unable to type passwords with non-English/non-Latin input source Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I recently found that I am unable to type using the "Japanese (Anthy)" input source in password fields in gnome-shell. That is I am unable to type using it (I just get English) on the login screen in the password field (though I haven't tried the username field), I am unable to type using it in the graphical prompts for authentication, and I am unable to type using it when setting a new password through the gnome- control-center. I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well as with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1566357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1614925] Re: Allow one to set the week to start on Sunday in built-in calendar
** Bug watch added: GNOME Bug Tracker #783792 https://bugzilla.gnome.org/show_bug.cgi?id=783792 ** Also affects: gnome-calendar via https://bugzilla.gnome.org/show_bug.cgi?id=783792 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1614925 Title: Allow one to set the week to start on Sunday in built-in calendar Status in GNOME Calendar: Confirmed Status in gnome-tweak-tool: Incomplete Status in Ubuntu GNOME: Confirmed Status in gnome-calendar package in Ubuntu: Confirmed Status in gnome-tweak-tool package in Ubuntu: Triaged Bug description: Some religious as well as regional calendars (e.g.: the Japanese calendar) start the week with Sunday as opposed to Monday. I think that there should be an option in the gnome-tweak-tool to make it so that the weeks are displayed as starting on Sunday in the built-in calendar accessible from the top-bar. This can already be done manually, but an option in the GUI would be nice. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1614925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1614925] Re: Allow one to set the week to start on Sunday in built-in calendar
** Changed in: ubuntu-gnome Status: New => Confirmed ** Also affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-calendar (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1614925 Title: Allow one to set the week to start on Sunday in built-in calendar Status in GNOME Calendar: Unknown Status in gnome-tweak-tool: Incomplete Status in Ubuntu GNOME: Confirmed Status in gnome-calendar package in Ubuntu: Confirmed Status in gnome-tweak-tool package in Ubuntu: Triaged Bug description: Some religious as well as regional calendars (e.g.: the Japanese calendar) start the week with Sunday as opposed to Monday. I think that there should be an option in the gnome-tweak-tool to make it so that the weeks are displayed as starting on Sunday in the built-in calendar accessible from the top-bar. This can already be done manually, but an option in the GUI would be nice. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1614925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652272] Re: Firefox suddenly loses internet connection
** Changed in: ubuntu-gnome Status: New => Confirmed ** Tags added: zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1652272 Title: Firefox suddenly loses internet connection Status in Mozilla Firefox: New Status in Ubuntu GNOME: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Since earlier today I have found that after about 10 minutes or less of using Firefox that suddenly for no apparent reason pages will refuse to load any contents, and although Firefox does not take me to the page which says it can't reach the site, it doesn't manage to load anything as though its internet connection has suddenly been lost. It won't even let me check for updates for plugins and gives an error for that. I have tested with other applications such as ping and the internet connection is fine, it's just Firefox which loses it. I have noticed that when I run firefox from Terminal that this is the output to begin with: 1482487989643 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest. 1482487989708 addons.webextension.fire...@ghostery.comWARN Please specify whether you want browser_style or not in your browser_action options. Promise resolved after context unloaded Then when the problem starts to occur, I find that the only way to resolve it, if even for a short period, is to restart the browser, so I tell Firefox to quit, however although the window does close, the process carries on and this is the output: tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. console.error: Message: Error: SessionFile is closed Stack: SessionFileInternal.write@resource://app/modules/sessionstore/SessionFile.jsm:315:29 this.SessionFile.write@resource://app/modules/sessionstore/SessionFile.jsm:76:12 SessionSaverInternal._writeState@resource://app/modules/sessionstore/SessionSaver.jsm:259:12 SessionSaverInternal._saveState@resource://app/modules/sessionstore/SessionSaver.jsm:230:12 SessionSaverInternal._saveStateAsync@resource://app/modules/sessionstore/SessionSaver.jsm:243:5 SessionSaverInternal.runDelayed/this._timeoutID<@resource://app/modules/sessionstore/SessionSaver.jsm:147:40 setTimeout_timer@resource://gre/modules/Timer.jsm:30:5 ExceptionHandler::GenerateDump cloned child 12324 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... I am then told that Firefox crashed and asked if I would like to submit a report, so far I have told it to submit a report three times as the crash has occurred that number of times. For that entire period of time this is the output from Firefox in syslog: Dec 23 10:00:42 firefox.desktop[11349]: 1482487242751#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242778#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An
[Desktop-packages] [Bug 1695917] [NEW] 0.26.2 has been released
Public bug reported: A new maintenance release for Shotwell which is 0.26.2 is now available for download. Please upgrade the version the the repositories. The changelog is: Shotwell 0.26.2 - 1 Jun 2017 * Fix issue when minimizing publishing UI on Unity * Fix browsing on GVFS-mounted file systems * Fix missing linebreaks in comments when writing back meta-data * Fix crash when no import plugin is selected * Translation updates ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1695917 Title: 0.26.2 has been released Status in shotwell package in Ubuntu: New Bug description: A new maintenance release for Shotwell which is 0.26.2 is now available for download. Please upgrade the version the the repositories. The changelog is: Shotwell 0.26.2 - 1 Jun 2017 * Fix issue when minimizing publishing UI on Unity * Fix browsing on GVFS-mounted file systems * Fix missing linebreaks in comments when writing back meta-data * Fix crash when no import plugin is selected * Translation updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1695917/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650395] Re: Strange large grey border around gnome-terminal when transparency is enabled (shadow is opaque)
I also experienced this issue with: Adwaita, Numix, and Arc all from the official Ubuntu repositories. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1650395 Title: Strange large grey border around gnome-terminal when transparency is enabled (shadow is opaque) Status in Ubuntu GNOME: Triaged Status in gnome-terminal package in Ubuntu: Triaged Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22, that there is a large strange grey border around the window: - Fullscreen_gnome-terminal_in_AO_no_strange_border.png - Fullscreen_gnome-terminal_window.png - gnome-terminal_in_AO_strange_border.png - gnome-terminal_window_strange_border.png But this only occurs when the window is not fullscreen, and when transparency is enabled. Turning transparency off immediately fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 15 21:29:17 2016 InstallationDate: Installed on 2016-05-15 (214 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-19 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1692233] Re: Unable to install language packs
*** This bug is a duplicate of bug 1631750 *** https://bugs.launchpad.net/bugs/1631750 Oh, sorry, I just forgot and couldn't find a similar bug report for some reason I filled a new one... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1692233 Title: Unable to install language packs Status in Ubuntu GNOME: New Status in gnome-control-center package in Ubuntu: New Bug description: I have found that on my Ubuntu GNOME 17.04 installation with GNOME 3.24.1 that if I open the "Region & Language" section of the gnome- control-center that even though in Terminal it is indicated that there are Enlish (UK) packages to install, it doesn't do anything in the GUI. And if I attempt to install a new language the whole window just really quickly flashes once but nothing else happens. Here is the output from Terminal: ** (gnome-control-center:9685): WARNING **: Ignoring launcher gufw (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher language-selector (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher system-config-printer (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) (gnome-control-center:9685): common-cc-panel-WARNING **: Language en_GB.UTF-8 not installed, trying to install it (gnome-control-center:9685): common-cc-panel-WARNING **: Language ja_JP not installed, trying to install it I know other people who are experiencing this issue and the only way for them to install new languages is to install the gnome-language- selector from Unity. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-control-center 1:3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 20 16:20:05 2017 InstallationDate: Installed on 2017-05-18 (1 days ago) InstallationMedia: SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1692233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1692233] [NEW] Unable to install language packs
Public bug reported: I have found that on my Ubuntu GNOME 17.04 installation with GNOME 3.24.1 that if I open the "Region & Language" section of the gnome- control-center that even though in Terminal it is indicated that there are Enlish (UK) packages to install, it doesn't do anything in the GUI. And if I attempt to install a new language the whole window just really quickly flashes once but nothing else happens. Here is the output from Terminal: ** (gnome-control-center:9685): WARNING **: Ignoring launcher gufw (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher language-selector (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher system-config-printer (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) (gnome-control-center:9685): common-cc-panel-WARNING **: Language en_GB.UTF-8 not installed, trying to install it (gnome-control-center:9685): common-cc-panel-WARNING **: Language ja_JP not installed, trying to install it I know other people who are experiencing this issue and the only way for them to install new languages is to install the gnome-language-selector from Unity. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-control-center 1:3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 20 16:20:05 2017 InstallationDate: Installed on 2017-05-18 (1 days ago) InstallationMedia: SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1692233 Title: Unable to install language packs Status in Ubuntu GNOME: New Status in gnome-control-center package in Ubuntu: New Bug description: I have found that on my Ubuntu GNOME 17.04 installation with GNOME 3.24.1 that if I open the "Region & Language" section of the gnome- control-center that even though in Terminal it is indicated that there are Enlish (UK) packages to install, it doesn't do anything in the GUI. And if I attempt to install a new language the whole window just really quickly flashes once but nothing else happens. Here is the output from Terminal: ** (gnome-control-center:9685): WARNING **: Ignoring launcher gufw (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher language-selector (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher system-config-printer (missing desktop file) ** (gnome-control-center:9685): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) (gnome-control-center:9685): common-cc-panel-WARNING **: Language en_GB.UTF-8 not installed, trying to install it (gnome-control-center:9685): common-cc-panel-WARNING **: Language ja_JP not installed, trying to install it I know other people who are experiencing this issue and the only way for them to install new languages is to install the gnome-language- selector from Unity. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-control-center 1:3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 20 16:20:05 2017 InstallationDate: Installed on 2017-05-18 (1 days ago) InstallationMedia: SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1692233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650684] Re: Position of gnome-system-monitor is not remembered on screen when under Wayland
Apparently this is not actually possible under Wayland. ** Changed in: ubuntu-gnome Status: New => Invalid ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1650684 Title: Position of gnome-system-monitor is not remembered on screen when under Wayland Status in GNOME Shell: Invalid Status in Ubuntu GNOME: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in gnome-system-monitor package in Ubuntu: Invalid Bug description: I am running Ubuntu GNOME 16.10 with GNOME 3.22 and since switching from Xorg to Wayland via the login screen I have noticed that with the gnome-system-monitor that it always starts off on the left hand side of the screen, and I like to have it on the right hand side, so that is where I always put it. However, if I restart it, it always goes back to the left side rather than remembering where it was before like it does if I close it when it is fullscreen. So far it seems that this issue only affects the gnome-system-monitor, all other applications behave as expected in regards to this matter. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 16 22:26:09 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (215 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1650684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685878] Re: Gedit bottom scroll bar goes on top of final line
I have also found this issue in gnome-builder so I believe it to be a GTK+ issue. ** Project changed: gedit => gtk ** No longer affects: gedit (Ubuntu) ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1685878 Title: Gedit bottom scroll bar goes on top of final line Status in GTK+: New Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: New Bug description: I am on Ubuntu GNOME 17.04 with GNOME 3.24, though obviously still Gedit 3.22, and I have found something slightly annoying with it, and that is that when mousing over the last line to try to copy and paste it for instance, the bottom scroll bar goes on top of it and obscures it. I have attached two screenshots of what I mean. This also affects me on Arch so I have filled an upstream report on this. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1685878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652282] Re: GParted does not work in GNOME on Wayland
@Phillip, Wayland actually does accommodate it, I have an Arch system where it works perfectly fine with running GParted as root. The reason it doesn't work on Ubuntu is not completely because of Wayland, but rather because of how Wayland has been set up by the Ubuntu GNOME team. Which is intentional for security. I don't know, but you might be able to disable this since it's probably somewhere in the configuration. I don't know, I just know that on Arch there is no issue with this with the standard Wayland. ** Summary changed: - Wayland default policy prohibits root applications + GParted does not work in GNOME on Wayland ** No longer affects: wayland (Ubuntu) ** Also affects: gparted (Ubuntu) Importance: Undecided Status: New ** Changed in: gparted (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1652282 Title: GParted does not work in GNOME on Wayland Status in GParted: Confirmed Status in Ubuntu GNOME: Triaged Status in gparted package in Ubuntu: Confirmed Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 that GParted does not run when I try to run it as root. That is when I click the icon and enter my password nothing happens. I have found that when running what is run when the icon is clicked that the output in Terminal is (gparted-pkexec): Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/boot.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/boot.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/tmp.mount. So I am now unable to launch and use GParted as root which is really the only way I can run it in order to make changes. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gparted 0.25.0-1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 23 11:13:13 2016 InstallationDate: Installed on 2016-05-15 (221 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gparted UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1652282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685878] [NEW] Gedit bottom scroll bar goes on top of final line
Public bug reported: I am on Ubuntu GNOME 17.04 with GNOME 3.24, though obviously still Gedit 3.22, and I have found something slightly annoying with it, and that is that when mousing over the last line to try to copy and paste it for instance, the bottom scroll bar goes on top of it and obscures it. I have attached two screenshots of what I mean. This also affects me on Arch so I have filled an upstream report on this. ** Affects: gedit Importance: Unknown Status: Unknown ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Also affects: gedit (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #781669 https://bugzilla.gnome.org/show_bug.cgi?id=781669 ** Also affects: gedit via https://bugzilla.gnome.org/show_bug.cgi?id=781669 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1685878 Title: Gedit bottom scroll bar goes on top of final line Status in gedit: Unknown Status in Ubuntu GNOME: New Status in gedit package in Ubuntu: New Bug description: I am on Ubuntu GNOME 17.04 with GNOME 3.24, though obviously still Gedit 3.22, and I have found something slightly annoying with it, and that is that when mousing over the last line to try to copy and paste it for instance, the bottom scroll bar goes on top of it and obscures it. I have attached two screenshots of what I mean. This also affects me on Arch so I have filled an upstream report on this. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672161] [NEW] Have better archive handling
Public bug reported: I have a system running Ubuntu GNOME 16.10 with GNOME 3.22 and I have found that in this version of GNOME if one right-clicks on a file or folder or a group of them and goes to "Compress..." that they are provided with 3 different formats to compress into, however the options which allow splitting of large archives into smaller ones as well as the ability to encrypt them with a password are gone. This can obviously still be done through the CLIs of the various tools, however it would be useful to have such features accessible as they used to be through the GUI. Perhaps this is a side-effect of making all Nautilus activities central to the Nautilus GUI? Because I think I remember it possibly opening another program in the past which had these options. Regardless of what it and how it did it in the past, these are vital options which are missing and I think should be added back for ease of use. I am fine with using the CLI, but many users are not. ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #773366 https://bugzilla.gnome.org/show_bug.cgi?id=773366 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=773366 Importance: Unknown Status: Unknown ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1672161 Title: Have better archive handling Status in Nautilus: Unknown Status in Ubuntu GNOME: New Status in nautilus package in Ubuntu: New Bug description: I have a system running Ubuntu GNOME 16.10 with GNOME 3.22 and I have found that in this version of GNOME if one right-clicks on a file or folder or a group of them and goes to "Compress..." that they are provided with 3 different formats to compress into, however the options which allow splitting of large archives into smaller ones as well as the ability to encrypt them with a password are gone. This can obviously still be done through the CLIs of the various tools, however it would be useful to have such features accessible as they used to be through the GUI. Perhaps this is a side-effect of making all Nautilus activities central to the Nautilus GUI? Because I think I remember it possibly opening another program in the past which had these options. Regardless of what it and how it did it in the past, these are vital options which are missing and I think should be added back for ease of use. I am fine with using the CLI, but many users are not. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1672161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1590204] Re: [SRU] Update to bug fix release 3.8.4 in Trusty
** Changed in: gnome-contacts (Ubuntu Trusty) Assignee: Nikita Yerenkov-Scott (yerenkov-scott) => (unassigned) ** Changed in: gnome-contacts (Ubuntu) Assignee: Nikita Yerenkov-Scott (yerenkov-scott) => (unassigned) ** Changed in: ubuntu-gnome Assignee: Nikita Yerenkov-Scott (yerenkov-scott) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-contacts in Ubuntu. https://bugs.launchpad.net/bugs/1590204 Title: [SRU] Update to bug fix release 3.8.4 in Trusty Status in Ubuntu GNOME: Triaged Status in gnome-contacts package in Ubuntu: Fix Released Status in gnome-contacts source package in Trusty: Triaged Bug description: Impact --- Missing text input box for Address field (LP: #1249947) https://git.gnome.org/browse/gnome-contacts/tree/NEWS?h=gnome-3-8 * Fixed New Contact dialog address field issue Test case -- 1. Install gnome-contact from trusty-proposed 2. Add a New Contact 3. See the text input box for the Address field Regression potential Low, as the fix is small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1590204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652282] Re: Wayland default policy prohibits root applications
@Phillip, This is an intended policy and it is there for security reasons so rather than decreasing security standards, I think it would be best for GParted to simply meet them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1652282 Title: Wayland default policy prohibits root applications Status in GParted: Confirmed Status in Ubuntu GNOME: New Status in wayland package in Ubuntu: New Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 that GParted does not run when I try to run it as root. That is when I click the icon and enter my password nothing happens. I have found that when running what is run when the icon is clicked that the output in Terminal is (gparted-pkexec): Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/boot.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/boot.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/tmp.mount. So I am now unable to launch and use GParted as root which is really the only way I can run it in order to make changes. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gparted 0.25.0-1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 23 11:13:13 2016 InstallationDate: Installed on 2016-05-15 (221 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gparted UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1652282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654834] [NEW] gnome-terminal launches new windows rather than focusing on already open ones under Wayland
Public bug reported: For some strange reason after switching from Xorg to Wayland under Ubuntu GNOME 16.10 with GNOME 3.22, when I click on the docked gnome- terminal icon in the dock I find that if a Terminal window is already open, or even multiple already, instead of just going to one of the existing ones as one would expect it to do, it opens a new Terminal window and acts as if none were open already. If one is to carry on clicking it it will open many many more Terminal windows, it may then randomly stop this strange behaviour and just focus on one of the already open ones. Though when it decides to go back to normal appears to be completely random. I have not found this issue with any other of my applications, just gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 8 11:13:00 2017 InstallationDate: Installed on 2016-05-15 (237 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-19 (80 days ago) ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa gnome3-staging third-party-packages wayland-session yakkety ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1654834 Title: gnome-terminal launches new windows rather than focusing on already open ones under Wayland Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: For some strange reason after switching from Xorg to Wayland under Ubuntu GNOME 16.10 with GNOME 3.22, when I click on the docked gnome- terminal icon in the dock I find that if a Terminal window is already open, or even multiple already, instead of just going to one of the existing ones as one would expect it to do, it opens a new Terminal window and acts as if none were open already. If one is to carry on clicking it it will open many many more Terminal windows, it may then randomly stop this strange behaviour and just focus on one of the already open ones. Though when it decides to go back to normal appears to be completely random. I have not found this issue with any other of my applications, just gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 8 11:13:00 2017 InstallationDate: Installed on 2016-05-15 (237 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-19 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1654834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653352] Re: Allow one to mark as "Junk" from right-click menu
It turns out that this feature is already present, just it is in the Mark sub-menu. ** Changed in: ubuntu-gnome Status: New => Invalid ** Changed in: thunderbird (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1653352 Title: Allow one to mark as "Junk" from right-click menu Status in Mozilla Thunderbird: Invalid Status in Ubuntu GNOME: Invalid Status in thunderbird package in Ubuntu: Invalid Bug description: I don't want to have to open junk mail which could potentially have malicious content in order to mark it as junk. So it would be very useful if there were a mark as "Junk" option in the right-click menu for emails, as well as the "Delete" option. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351] Re: Have option to not automatically open next email
** Bug watch added: Mozilla Bugzilla #395151 https://bugzilla.mozilla.org/show_bug.cgi?id=395151 ** Changed in: thunderbird Remote watch: Mozilla Bugzilla #1326536 => Mozilla Bugzilla #395151 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Unknown Status in Ubuntu GNOME: New Status in thunderbird package in Ubuntu: New Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653352] [NEW] Allow one to mark as "Junk" from right-click menu
Public bug reported: I don't want to have to open junk mail which could potentially have malicious content in order to mark it as junk. So it would be very useful if there were a mark as "Junk" option in the right-click menu for emails, as well as the "Delete" option. ** Affects: thunderbird Importance: Unknown Status: Unknown ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Mozilla Bugzilla #1326537 https://bugzilla.mozilla.org/show_bug.cgi?id=1326537 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=1326537 Importance: Unknown Status: Unknown ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1653352 Title: Allow one to mark as "Junk" from right-click menu Status in Mozilla Thunderbird: Unknown Status in Ubuntu GNOME: New Status in thunderbird package in Ubuntu: New Bug description: I don't want to have to open junk mail which could potentially have malicious content in order to mark it as junk. So it would be very useful if there were a mark as "Junk" option in the right-click menu for emails, as well as the "Delete" option. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351] [NEW] Have option to not automatically open next email
Public bug reported: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. ** Affects: thunderbird Importance: Unknown Status: Unknown ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Mozilla Bugzilla #1326536 https://bugzilla.mozilla.org/show_bug.cgi?id=1326536 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=1326536 Importance: Unknown Status: Unknown ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Unknown Status in Ubuntu GNOME: New Status in thunderbird package in Ubuntu: New Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652463] Re: gnome-terminal-server crashed with SIGSEGV in XSync() when launched from desktop under Wayland
** Project changed: gnome-terminal => gtk ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-terminal (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1652463 Title: gnome-terminal-server crashed with SIGSEGV in XSync() when launched from desktop under Wayland Status in GTK+: Confirmed Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: New Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that when I use the right-click menu to open Terminal from the desktop that a window looking like this shows up on the screen for about a second or less: Terminal_Opened_From_Desktop.png And then when it closes all the other Terminal sessions go with it instantly killing anything I've got running from any of the gnome- terminal windows which is really quite annoying and luckily I didn't have anything vital running from one at the time. But this could seriously cause something quite bad for another unsuspecting person. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 24 19:59:50 2016 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2016-05-15 (223 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-terminal StacktraceTop: ?? () XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 gdk_window_process_all_updates () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libvte-2.91.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-terminal-server crashed with SIGSEGV in XSync() UpgradeStatus: Upgraded to yakkety on 2016-10-19 (66 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1652463/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652463] Re: gnome-terminal-server crashed with SIGSEGV in XSync() when launched from desktop under Wayland
** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/gnome-terminal/+bug/1652463/+attachment/4796160/+files/JournalErrors.txt ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1652463 Title: gnome-terminal-server crashed with SIGSEGV in XSync() when launched from desktop under Wayland Status in GNOME Terminal: Incomplete Status in Ubuntu GNOME: New Status in gnome-terminal package in Ubuntu: Invalid Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that when I use the right-click menu to open Terminal from the desktop that a window looking like this shows up on the screen for about a second or less: Terminal_Opened_From_Desktop.png And then when it closes all the other Terminal sessions go with it instantly killing anything I've got running from any of the gnome- terminal windows which is really quite annoying and luckily I didn't have anything vital running from one at the time. But this could seriously cause something quite bad for another unsuspecting person. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 24 19:59:50 2016 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2016-05-15 (223 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-terminal StacktraceTop: ?? () XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 gdk_window_process_all_updates () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libvte-2.91.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-terminal-server crashed with SIGSEGV in XSync() UpgradeStatus: Upgraded to yakkety on 2016-10-19 (66 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1652463/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652461] Re: Launching Terminal from desktop kills all gnome-terminal sessions under Wayland
*** This bug is a duplicate of bug 1652463 *** https://bugs.launchpad.net/bugs/1652463 ** This bug has been marked a duplicate of private bug 1652463 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1652461 Title: Launching Terminal from desktop kills all gnome-terminal sessions under Wayland Status in GNOME Terminal: Unknown Status in Ubuntu GNOME: New Status in gnome-terminal package in Ubuntu: New Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that when I use the right-click menu to open Terminal from the desktop that a window looking like this shows up on the screen for about a second or less: Terminal_Opened_From_Desktop.png And then when it closes all the other Terminal sessions go with it instantly killing anything I've got running from any of the gnome- terminal windows which is really quite annoying and luckily I didn't have anything vital running from one at the time. But this could seriously cause something quite bad for another unsuspecting person. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.22.2-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 24 20:14:41 2016 InstallationDate: Installed on 2016-05-15 (223 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-19 (65 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1652461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652461] Re: Launching Terminal from desktop kills all gnome-terminal sessions under Wayland
** Bug watch added: GNOME Bug Tracker #776472 https://bugzilla.gnome.org/show_bug.cgi?id=776472 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=776472 Importance: Unknown Status: Unknown ** Project changed: nautilus => gnome-terminal ** No longer affects: nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1652461 Title: Launching Terminal from desktop kills all gnome-terminal sessions under Wayland Status in GNOME Terminal: Unknown Status in Ubuntu GNOME: New Status in gnome-terminal package in Ubuntu: New Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that when I use the right-click menu to open Terminal from the desktop that a window looking like this shows up on the screen for about a second or less: Terminal_Opened_From_Desktop.png And then when it closes all the other Terminal sessions go with it instantly killing anything I've got running from any of the gnome- terminal windows which is really quite annoying and luckily I didn't have anything vital running from one at the time. But this could seriously cause something quite bad for another unsuspecting person. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.22.2-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 24 20:14:41 2016 InstallationDate: Installed on 2016-05-15 (223 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-19 (65 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1652461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652461] [NEW] Launching Terminal from desktop kills all gnome-terminal sessions under Wayland
Public bug reported: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that when I use the right-click menu to open Terminal from the desktop that a window looking like this shows up on the screen for about a second or less: Terminal_Opened_From_Desktop.png And then when it closes all the other Terminal sessions go with it instantly killing anything I've got running from any of the gnome- terminal windows which is really quite annoying and luckily I didn't have anything vital running from one at the time. But this could seriously cause something quite bad for another unsuspecting person. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.22.2-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 24 20:14:41 2016 InstallationDate: Installed on 2016-05-15 (223 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-19 (65 days ago) usr_lib_nautilus: dropbox 2015.10.28 ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa gnome3-staging third-party-packages wayland-session yakkety ** Attachment added: "Terminal_Opened_From_Desktop.png" https://bugs.launchpad.net/bugs/1652461/+attachment/4796149/+files/Terminal_Opened_From_Desktop.png ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Launching Terminal from desktop kills all gnome-terminal sessions + Launching Terminal from desktop kills all gnome-terminal sessions under Wayland ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1652461 Title: Launching Terminal from desktop kills all gnome-terminal sessions under Wayland Status in Ubuntu GNOME: New Status in gnome-terminal package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that when I use the right-click menu to open Terminal from the desktop that a window looking like this shows up on the screen for about a second or less: Terminal_Opened_From_Desktop.png And then when it closes all the other Terminal sessions go with it instantly killing anything I've got running from any of the gnome- terminal windows which is really quite annoying and luckily I didn't have anything vital running from one at the time. But this could seriously cause something quite bad for another unsuspecting person. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.22.2-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 24 20:14:41 2016 InstallationDate: Installed on 2016-05-15 (223 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-19 (65 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1652461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652299] Re: Menus jump around under Wayland
** Bug watch added: GNOME Bug Tracker #776439 https://bugzilla.gnome.org/show_bug.cgi?id=776439 ** Also affects: gimp via https://bugzilla.gnome.org/show_bug.cgi?id=776439 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1652299 Title: Menus jump around under Wayland Status in The Gimp: Unknown Status in Ubuntu GNOME: New Status in gimp package in Ubuntu: New Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 that when I for instance will go to the Filters menu and go down to Artistic and then when I move my mouse to where its pull-down menu is, I find that suddenly it jumps to the File menu being open, or another one. This is not always the case, but it happens a lot, so much that it disrupts my work. This happens with quite a few of the pull-down menus, though mostly with the longer ones. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gimp 2.8.18-1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 23 12:41:28 2016 InstallationDate: Installed on 2016-05-15 (221 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gimp UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/1652299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652299] [NEW] Menus jump around under Wayland
Public bug reported: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 that when I for instance will go to the Filters menu and go down to Artistic and then when I move my mouse to where its pull-down menu is, I find that suddenly it jumps to the File menu being open, or another one. This is not always the case, but it happens a lot, so much that it disrupts my work. This happens with quite a few of the pull-down menus, though mostly with the longer ones. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gimp 2.8.18-1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 23 12:41:28 2016 InstallationDate: Installed on 2016-05-15 (221 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gimp UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago) ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages wayland-session yakkety ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1652299 Title: Menus jump around under Wayland Status in Ubuntu GNOME: New Status in gimp package in Ubuntu: New Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 that when I for instance will go to the Filters menu and go down to Artistic and then when I move my mouse to where its pull-down menu is, I find that suddenly it jumps to the File menu being open, or another one. This is not always the case, but it happens a lot, so much that it disrupts my work. This happens with quite a few of the pull-down menus, though mostly with the longer ones. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gimp 2.8.18-1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 23 12:41:28 2016 InstallationDate: Installed on 2016-05-15 (221 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gimp UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1652299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652272] [NEW] Firefox suddenly loses internet connection
Public bug reported: Since earlier today I have found that after about 10 minutes or less of using Firefox that suddenly for no apparent reason pages will refuse to load any contents, and although Firefox does not take me to the page which says it can't reach the site, it doesn't manage to load anything as though its internet connection has suddenly been lost. It won't even let me check for updates for plugins and gives an error for that. I have tested with other applications such as ping and the internet connection is fine, it's just Firefox which loses it. I have noticed that when I run firefox from Terminal that this is the output to begin with: 1482487989643 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest. 1482487989708 addons.webextension.fire...@ghostery.comWARN Please specify whether you want browser_style or not in your browser_action options. Promise resolved after context unloaded Then when the problem starts to occur, I find that the only way to resolve it, if even for a short period, is to restart the browser, so I tell Firefox to quit, however although the window does close, the process carries on and this is the output: tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. console.error: Message: Error: SessionFile is closed Stack: SessionFileInternal.write@resource://app/modules/sessionstore/SessionFile.jsm:315:29 this.SessionFile.write@resource://app/modules/sessionstore/SessionFile.jsm:76:12 SessionSaverInternal._writeState@resource://app/modules/sessionstore/SessionSaver.jsm:259:12 SessionSaverInternal._saveState@resource://app/modules/sessionstore/SessionSaver.jsm:230:12 SessionSaverInternal._saveStateAsync@resource://app/modules/sessionstore/SessionSaver.jsm:243:5 SessionSaverInternal.runDelayed/this._timeoutID<@resource://app/modules/sessionstore/SessionSaver.jsm:147:40 setTimeout_timer@resource://gre/modules/Timer.jsm:30:5 ExceptionHandler::GenerateDump cloned child 12324 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... I am then told that Firefox crashed and asked if I would like to submit a report, so far I have told it to submit a report three times as the crash has occurred that number of times. For that entire period of time this is the output from Firefox in syslog: Dec 23 10:00:42 firefox.desktop[11349]: 1482487242751#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242778#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242821#011addons.webextension.fire...@ghostery.com#011WARN#011Please specify whether you want browser_style or not in your browser_action options. Dec 23 10:01:00 firefox.desktop[11349]: Promise resolved after context unloaded Dec 23 10:10:37 firefox.desktop[11349]: Promise resolved after context unloaded Dec 23 10:11:25 firefox.desktop[11349]: console.error: Dec 23
[Desktop-packages] [Bug 1644320] Re: [SRU] New upstream release 2.50.1
This update fixes the issues for me and there are currently no noticeable regressions on my Ubuntu GNOME 16.10 GNOME 3.22 64-bit system. ** Tags removed: verification-needed ** Tags added: verification-done ** Tags added: yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1644320 Title: [SRU] New upstream release 2.50.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: [ Description ] Upstream have released a new bugfix release. [ Changes ] From NEWS: Overview of changes in GLib 2.50.2 == * Bugs fixed: 767882 Bit shift overflow (-Wshift-overflow) warning in gparam.h 769135 External control for g_test_add/g_test_run 769630 gfile: G_FILE_MONITOR_WATCH_MOVES was actually introduced in 2.46 772054 Patch for glib/gspawn-win32-helper.c: unexpected behavior re CommandLineToArgvW() 773303 GApplication leaks option_strings 773344 glib-compile-resources: Fix creating depfile with other targets * Translation updates: French Galician German Lithuanian Norwegian bokmål Occitan Serbian Slovak Overview of changes in GLib 2.50.1 == * Update Unicode support to Unicode 9.0.0 * Bugs fixed: 662946 gunixmounts monitoring doesn't work correctly with libmount 771591 Update to Unicode 9.0.0 772054 glib/gspawn-win32-helper.c: unexpected behavior re CommandLineToArgvW() 772255 gresolver: Mark GResolver as an abstract class 772269 Add --version options to glib-compile-resources and glib-compile-schemas 772297 completion: Complete gsettings describe 772511 g_log_default_handler crashes windows apps with "Unspecified fatal err... * Translation updates: Brazilian Portuguese Catalan Croatian Czech Danish Hungarian Italian Latvian Polish Swedish [ QA, testing, regression potential ] Under the GNOME MRE, you can believe all bugs upstream says are fixed are really fixed. Just test the system and make sure there are no regressions (e.g. look at errors.ubuntu.com). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1644320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650684] Re: Position of gnome-system-monitor is not remembered on screen when under Wayland
** Bug watch added: GNOME Bug Tracker #776321 https://bugzilla.gnome.org/show_bug.cgi?id=776321 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=776321 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1650684 Title: Position of gnome-system-monitor is not remembered on screen when under Wayland Status in gnome-shell: Unknown Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: New Status in gnome-system-monitor package in Ubuntu: New Bug description: I am running Ubuntu GNOME 16.10 with GNOME 3.22 and since switching from Xorg to Wayland via the login screen I have noticed that with the gnome-system-monitor that it always starts off on the left hand side of the screen, and I like to have it on the right hand side, so that is where I always put it. However, if I restart it, it always goes back to the left side rather than remembering where it was before like it does if I close it when it is fullscreen. So far it seems that this issue only affects the gnome-system-monitor, all other applications behave as expected in regards to this matter. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 16 22:26:09 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (215 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1650684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
I tested this in an Ubuntu GNOME 16.10 GNOME 3.20 64-bit VM and found that with the new update the issue goes away and the problem here is fixed. Although it should be noted that after updating to the new version it shows any mounted partitions with a long gobbledygook name in the sidebar when running Nautilus as root. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: Confirmed Status in glib2.0 source package in Yakkety: Fix Committed Bug description: [ Description ] Can't trash files if the directory they are in is a symlink to another device [ QA ] Steps: 1. Install system and partition disk into root and data partitions 2. create ~/Data folder, and mount data partition on it 3. create symlinks for ~/whatever/ to ~/Data/something/ 4. delete files directly inside ~/whatever/ What happen: Then Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". What should happen: The files moved into Trash. [ Regression potential ] The proposed fix uses g_stat instead of g_stat to follow symlinks, so we know where to place the trash (you can't rename() across filesystems). If that is wrong, then it could regress trashing other kinds of files. [ Original ] I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
** Attachment added: "Gobbledygook name in Nautilus sidebar" https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+attachment/4794160/+files/Screenshot%20from%202016-12-19%2021-14-42.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: Confirmed Status in glib2.0 source package in Yakkety: Fix Committed Bug description: [ Description ] Can't trash files if the directory they are in is a symlink to another device [ QA ] Steps: 1. Install system and partition disk into root and data partitions 2. create ~/Data folder, and mount data partition on it 3. create symlinks for ~/whatever/ to ~/Data/something/ 4. delete files directly inside ~/whatever/ What happen: Then Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". What should happen: The files moved into Trash. [ Regression potential ] The proposed fix uses g_stat instead of g_stat to follow symlinks, so we know where to place the trash (you can't rename() across filesystems). If that is wrong, then it could regress trashing other kinds of files. [ Original ] I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: Confirmed Status in glib2.0 source package in Yakkety: Fix Committed Bug description: [ Description ] Can't trash files if the directory they are in is a symlink to another device [ QA ] Steps: 1. Install system and partition disk into root and data partitions 2. create ~/Data folder, and mount data partition on it 3. create symlinks for ~/whatever/ to ~/Data/something/ 4. delete files directly inside ~/whatever/ What happen: Then Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". What should happen: The files moved into Trash. [ Regression potential ] The proposed fix uses g_stat instead of g_stat to follow symlinks, so we know where to place the trash (you can't rename() across filesystems). If that is wrong, then it could regress trashing other kinds of files. [ Original ] I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
** Changed in: glib2.0 (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: Confirmed Status in glib2.0 source package in Yakkety: Fix Committed Bug description: [ Description ] Can't trash files if the directory they are in is a symlink to another device [ QA ] Steps: 1. Install system and partition disk into root and data partitions 2. create ~/Data folder, and mount data partition on it 3. create symlinks for ~/whatever/ to ~/Data/something/ 4. delete files directly inside ~/whatever/ What happen: Then Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". What should happen: The files moved into Trash. [ Regression potential ] The proposed fix uses g_stat instead of g_stat to follow symlinks, so we know where to place the trash (you can't rename() across filesystems). If that is wrong, then it could regress trashing other kinds of files. [ Original ] I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1633824] Re: nautilus ignores trash on external drives
** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in GLib: Fix Released Status in Ubuntu GNOME: New Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1633824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1651086] Re: Nautilus doesn't see items in local USB Trash
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #776262 https://bugzilla.gnome.org/show_bug.cgi?id=776262 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=776262 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1651086 Title: Nautilus doesn't see items in local USB Trash Status in Nautilus: Unknown Status in Ubuntu GNOME: New Status in nautilus package in Ubuntu: New Bug description: I have found that after upgrading from Ubuntu GNOME 16.04.1 with GNOME 3.20 to Ubuntu GNOME 16.10 with GNOME 3.22 that if I go into a USB and click the Nautilus button to "Move to Wastebasket" that it doesn't actually appear in my Wastebasket. If I then click the Undo button that comes up with the notification of the action in Nautilus, nothing happens. This is a before and after from the tree -a command: Before: /media/// ├── 123 │ ├── IMAG4613.jpg │ └── IMAG4617.jpg └── .Trash-1000 ├── files └── info 4 directories, 2 files After: /media/// └── .Trash-1000 ├── files │ └── 123 │ ├── IMAG4613.jpg │ └── IMAG4617.jpg └── info └── 123.trashinfo 4 directories, 3 files This is the case with all my USBs, but what is interesting is that I tried using Dolphin instead of Nautilus to bin the files and it worked using Dolphin, but I believe only because it moved it to the Trash of the actual system, rather than using the Trash system local to the USB. But this has become rather annoying to me as I can no longer delete files on USBs unless I enable the immediate permanent removal button or cut and copy them over to my system to deal with them there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.22.2-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 19 10:25:17 2016 InstallationDate: Installed on 2016-05-15 (217 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-19 (60 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1651086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650395] Re: Strange large grey border around gnome-terminal when transparency is enabled
I have tested this on Fedora 25 and it works fine. No strange border or anything. So it's probably our patch then or its handling. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1650395 Title: Strange large grey border around gnome-terminal when transparency is enabled Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22, that there is a large strange grey border around the window: - Fullscreen_gnome-terminal_in_AO_no_strange_border.png - Fullscreen_gnome-terminal_window.png - gnome-terminal_in_AO_strange_border.png - gnome-terminal_window_strange_border.png But this only occurs when the window is not fullscreen, and when transparency is enabled. Turning transparency off immediately fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 15 21:29:17 2016 InstallationDate: Installed on 2016-05-15 (214 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-19 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650684] [NEW] Position of gnome-system-monitor is not remembered on screen when under Wayland
Public bug reported: I am running Ubuntu GNOME 16.10 with GNOME 3.22 and since switching from Xorg to Wayland via the login screen I have noticed that with the gnome- system-monitor that it always starts off on the left hand side of the screen, and I like to have it on the right hand side, so that is where I always put it. However, if I restart it, it always goes back to the left side rather than remembering where it was before like it does if I close it when it is fullscreen. So far it seems that this issue only affects the gnome-system-monitor, all other applications behave as expected in regards to this matter. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 16 22:26:09 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (215 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (58 days ago) ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa gnome3-staging third-party-packages wayland-session yakkety ** Also affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1650684 Title: Position of gnome-system-monitor is not remembered on screen when under Wayland Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: New Status in gnome-system-monitor package in Ubuntu: New Bug description: I am running Ubuntu GNOME 16.10 with GNOME 3.22 and since switching from Xorg to Wayland via the login screen I have noticed that with the gnome-system-monitor that it always starts off on the left hand side of the screen, and I like to have it on the right hand side, so that is where I always put it. However, if I restart it, it always goes back to the left side rather than remembering where it was before like it does if I close it when it is fullscreen. So far it seems that this issue only affects the gnome-system-monitor, all other applications behave as expected in regards to this matter. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 16 22:26:09 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (215 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1650684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650395] Re: Strange large grey border around gnome-terminal when transparency is enabled
Yes, I know, I was thinking about that... So could it be an issue with the way it was patched in? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1650395 Title: Strange large grey border around gnome-terminal when transparency is enabled Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22, that there is a large strange grey border around the window: - Fullscreen_gnome-terminal_in_AO_no_strange_border.png - Fullscreen_gnome-terminal_window.png - gnome-terminal_in_AO_strange_border.png - gnome-terminal_window_strange_border.png But this only occurs when the window is not fullscreen, and when transparency is enabled. Turning transparency off immediately fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 15 21:29:17 2016 InstallationDate: Installed on 2016-05-15 (214 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-19 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650395] Re: Strange large grey border around gnome-terminal when transparency is enabled
** Attachment added: "gnome-terminal_window_strange_border.png" https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+attachment/4792210/+files/gnome-terminal_window_strange_border.png ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1650395 Title: Strange large grey border around gnome-terminal when transparency is enabled Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22, that there is a large strange grey border around the window: - Fullscreen_gnome-terminal_in_AO_no_strange_border.png - Fullscreen_gnome-terminal_window.png - gnome-terminal_in_AO_strange_border.png - gnome-terminal_window_strange_border.png But this only occurs when the window is not fullscreen, and when transparency is enabled. Turning transparency off immediately fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 15 21:29:17 2016 InstallationDate: Installed on 2016-05-15 (214 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-19 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1558156] Re: System Monitor numbers change but not graphs when viewing it through the Activities Overview (this happens often but not all the time)
This was under Xorg, now that I am running Wayland however the issue is much worse. Now not even the numbers, nothing does, even though it's running, it looks like just a still image of it in one state from the AO. So is this still likely to be a GNOME issue or could it perhaps be with Xorg and Wayland or something else? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1558156 Title: System Monitor numbers change but not graphs when viewing it through the Activities Overview (this happens often but not all the time) Status in gnome-shell: Confirmed Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: New Status in gnome-system-monitor package in Ubuntu: New Bug description: Although I have noticed this issue only with the System Monitor I do not know if it is isolated to it, but for some reason sometimes (about half the time) when viewing the System Monitor through the Activities Overview I get this strange effect where the numbers are clearly changing but the graphs are not: System_Monitor_Activities_Overview_Only_Numbers_Changing.mp4 And when I click on the application the graphs often then show something very different and carry as they were, so I'm going to say that I don't think that this is just an accurate display of the System Monitor going wrong, but rather something meaning that it is not displayed properly. I can also close and reopen the Activities Overview and the System Monitor will only snap out of it when I actually go to it (though I will have to test if it only corrects the problem when I go to it through the Activities Overview, but I think that that is the case). I am running Ubuntu GNOME 15.10 with GNOME 3.18, but I am sure that this issue was also present under Ubuntu GNOME 15.04 with GNOME 3.16. I only really do fresh installs so it's not going to just be faulty installation thing as I do them a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1558156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1648756] Re: Option to quit and save state
** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1648756 Title: Option to quit and save state Status in firefox package in Ubuntu: Invalid Bug description: When Firefox crashes and is force quitted or just closes because of the crash, it will normally remember the pages and cookies etc of the time it was open before the crash so that one can resume one's previous activities when starting it up again without having to reopen and relogin to everything etc. But sometimes I need to, say, restart my machine, or just temporarily close the browser so that I have enough RAM for another big process. So it would be very useful if there were an option somewhere, which like with the close with the crash, would save the current state of the browser so that one may return to that state when launching the browser again. This option could maybe be slightly out of the way in a menu, but not too hard to find. So that it's not the default, but one may use it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1648756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1648756] [NEW] Option to quit and save state
Public bug reported: When Firefox crashes and is force quitted or just closes because of the crash, it will normally remember the pages and cookies etc of the time it was open before the crash so that one can resume one's previous activities when starting it up again without having to reopen and relogin to everything etc. But sometimes I need to, say, restart my machine, or just temporarily close the browser so that I have enough RAM for another big process. So it would be very useful if there were an option somewhere, which like with the close with the crash, would save the current state of the browser so that one may return to that state when launching the browser again. This option could maybe be slightly out of the way in a menu, but not too hard to find. So that it's not the default, but one may use it. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1648756 Title: Option to quit and save state Status in firefox package in Ubuntu: New Bug description: When Firefox crashes and is force quitted or just closes because of the crash, it will normally remember the pages and cookies etc of the time it was open before the crash so that one can resume one's previous activities when starting it up again without having to reopen and relogin to everything etc. But sometimes I need to, say, restart my machine, or just temporarily close the browser so that I have enough RAM for another big process. So it would be very useful if there were an option somewhere, which like with the close with the crash, would save the current state of the browser so that one may return to that state when launching the browser again. This option could maybe be slightly out of the way in a menu, but not too hard to find. So that it's not the default, but one may use it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1648756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647198] [NEW] Suggestions dropdown menu often shown in wrong place
Public bug reported: Annoyingly so I have recently found that the suggestions dropdown menu below text boxes is showing in the wrong place. And even if I click where it is shown, or where the item should be, it may only highlight the relevant option, but close if you try to click it. As shown in this screencast: Firefox_suggestions_dropdown_menu_shown_in_wrong_place.mp4 And am able to reproduce the issue on many different sites so I don't think that it is site specific. I am running Ubuntu GNOME 16.10 with GNOME 3.22 and Firefox 50. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: firefox 50.0.2+build1-0ubuntu0.16.10.1 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: totoro 1705 F pulseaudio BuildID: 20161130094630 Channel: Unavailable CurrentDesktop: GNOME Date: Sun Dec 4 18:16:37 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-05-15 (203 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp3s0 proto static metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.3 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-3665f6f0-ae45-4976-ac4a-6c04f2160716 Plugins: GNOME Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) PrefErrors: 'utf-8' codec can't decode byte 0xa1 in position 2706: invalid start byte Profiles: Profile0 (Default) - LastVersion=50.0.2/20161130094630 (In use) RelatedPackageVersions: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-3665f6f0-ae45-4976-ac4a-6c04f2160716 bp-3fac0839-54f6-4471-9076-a99602160629 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to yakkety on 2016-10-19 (45 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO ** Affects: firefox Importance: Unknown Status: Unknown ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages xenial yakkety ** Attachment added: "Firefox_suggestions_dropdown_menu_shown_in_wrong_place.mp4" https://bugs.launchpad.net/bugs/1647198/+attachment/4787375/+files/Firefox_suggestions_dropdown_menu_shown_in_wrong_place.mp4 ** Description changed: Annoyingly so I have recently found that the suggestions dropdown menu below text boxes is showing in the wrong place. And even if I click where it is shown, or where the item should be, it may only highlight the relevant option, but close if you try to click it. As shown in this screencast: - Firefox_suggestions_dropdown_menu_shown_in_wrong_place.mp4 + Firefox_suggestions_dropdown_menu_shown_in_wrong_place.mp4 + + And am able to reproduce the issue on many different sites so I don't + think that it is site specific. I am running Ubuntu GNOME 16.10 with GNOME 3.22 and Firefox 50. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: firefox 50.0.2+build1-0ubuntu0.16.10.1 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: totoro 1705 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: totoro 1705 F pulseaudio BuildID: 20161130094630 Channel: Unavailable CurrentDesktop: GNOME Date: Sun Dec 4 18:16:37 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and
[Desktop-packages] [Bug 1640741] Re: ubuntu 17.04 gnome-software install button not working
Is this definitely a downstream issue or would it be worth reporting upstream as well? ** Also affects: ubuntu-gnome Importance: Undecided Status: New ** Changed in: ubuntu-gnome Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1640741 Title: ubuntu 17.04 gnome-software install button not working Status in Ubuntu GNOME: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: on ubuntu 17.04 gnome-software install button does nothing. try with different applications: UFRaw, Shutter, Entangle ... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.2+git20161108.0.a58dfc7-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 10 11:08:48 2016 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2016-11-06 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1640741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645102] Re: Allow bookmarks to launch multiple pages
** Bug watch added: Mozilla Bugzilla #1320547 https://bugzilla.mozilla.org/show_bug.cgi?id=1320547 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1320547 Importance: Unknown Status: Unknown ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1645102 Title: Allow bookmarks to launch multiple pages Status in Mozilla Firefox: Unknown Status in Ubuntu GNOME: New Status in firefox package in Ubuntu: New Bug description: I think it would be really useful if Firefox allowed you to have bookmarks which open multiple pages. So for instance, I have 3 news sites I read on a regular basis, however I don't want to have to open each one manually even if it's through 3 bookmarks, I also don't want to have them as startup pages. So what would be really useful for me would be just one bookmark titles something like "News" which upon being clicked would open 3 separate tabs in the specified order of the pages. I am sure that there would be many uses for this and that others would also find it useful. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1645102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645102] [NEW] Allow bookmarks to launch multiple pages
Public bug reported: I think it would be really useful if Firefox allowed you to have bookmarks which open multiple pages. So for instance, I have 3 news sites I read on a regular basis, however I don't want to have to open each one manually even if it's through 3 bookmarks, I also don't want to have them as startup pages. So what would be really useful for me would be just one bookmark titles something like "News" which upon being clicked would open 3 separate tabs in the specified order of the pages. I am sure that there would be many uses for this and that others would also find it useful. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1645102 Title: Allow bookmarks to launch multiple pages Status in firefox package in Ubuntu: New Bug description: I think it would be really useful if Firefox allowed you to have bookmarks which open multiple pages. So for instance, I have 3 news sites I read on a regular basis, however I don't want to have to open each one manually even if it's through 3 bookmarks, I also don't want to have them as startup pages. So what would be really useful for me would be just one bookmark titles something like "News" which upon being clicked would open 3 separate tabs in the specified order of the pages. I am sure that there would be many uses for this and that others would also find it useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1645102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"
If this bug affects you please also remember to mark it as "Yes, it
affects me" using the little pencil button next to the text under the
title which reads "This bug affects -- people. Does this bug affect
you?" ("--" replaced by the number of people). This adds 'heat' to the
bug meaning that its urgency will be seen as greater on the site.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1575248
Title:
"AppStream cache update completed, but some metadata was ignored due
to errors." on "sudo apt-get update"
Status in AppStream:
Invalid
Status in Ubuntu GNOME:
Confirmed
Status in appstream package in Ubuntu:
Invalid
Status in fwupd package in Ubuntu:
Fix Released
Status in fwupd source package in Xenial:
Fix Released
Status in fwupd package in Debian:
Fix Released
Bug description:
[Impact]
* Checks for apt updates using apt or apt-get also update the
appstream cache. Some of the appstream metadata installed locally
isn't strictly valid as it's missing two fields.
[Test Case]
* fwupdmgr refresh
* apt update
* check for errors about metadata being ignored
[Regression Potential]
* This is just changing the XML metadata locally, I don't see any
regression potential.
[Other Info]
* This fix has been applied upstream:
https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96
[Original report]
I have found that when there are new packages available which my
machine doesn't know about yet, if I run "sudo apt-get update" this is
the output:
Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2
kB]
Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386
Packages [28 B]
Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease
[82.2 kB]
Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386
Packages [28 B]
Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386
Packages [28 B]
Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64
Packages [28 B]
Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386
Packages [28 B]
Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse
Translation-en [28 B]
Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
[1,201 kB]
Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages
[1,196 kB]
Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB
[426 kB]
Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en
[568 kB]
Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11
Metadata [733 kB]
Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons
[409 kB]
Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64
Packages [8,344 B]
Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386
Packages [8,684 B]
Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted
Translation-en_GB [2,556 B]
Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted
Translation-en [2,908 B]
Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11
Metadata [186 B]
Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
[7,532 kB]
Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
[7,512 kB]
Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe
Translation-en_GB [3,040 kB]
Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en
[4,354 kB]
Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11
Metadata [3,410 kB]
Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64
Icons [7,448 kB]
Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64
Packages [144 kB]
Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386
Packages [140 kB]
Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse
Translation-en_GB [88.1 kB]
Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse
Translation-en [106 kB]
Get:32 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11
Metadata [63.8 kB]
Get:33 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64
Icons [230 kB]
Get:34 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages [28 B]
Get:35 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages [28 B]
Get:36 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main
Translation-en [28 B]
Get:37
[Desktop-packages] [Bug 1642718] Re: At least 3-5 minute gap between removing power cable and system notifying of event
After communicating with the upstream GNOME Shell project it has been found that this issue is more likely in UPower: https://bugzilla.gnome.org/show_bug.cgi?id=774717#c7 ** No longer affects: gnome-shell (Ubuntu) ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Bug watch added: freedesktop.org Bugzilla #98796 https://bugs.freedesktop.org/show_bug.cgi?id=98796 ** Also affects: upower via https://bugs.freedesktop.org/show_bug.cgi?id=98796 Importance: Unknown Status: Unknown ** No longer affects: gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1642718 Title: At least 3-5 minute gap between removing power cable and system notifying of event Status in Ubuntu GNOME: New Status in Upower: Unknown Status in upower package in Ubuntu: New Bug description: I have noticed something very strange after upgrading to Ubuntu GNOME 16.10 with GNOME 3.22, and that is that if: - My laptop is fully charged and I remove the power cable: 1. The indicator in the top right hand side of the screen changes from the icon indicating that it is fully charged to the icon indicating that it is charging, but not fully charged. 2. In about 3-5 minutes (longer if I suspend my machine mid way during this time span) I will hear the noise which signifies that my machine has disconnected from the power cable and the icon will change to the normal one which indicates that the machine does not have a power cable attached to it (the time indicator will also show how long until the battery runs out instead of how long until it is fully charged). - My laptop is not fully charged and I remove the power cable: 1. The same happens as for the previous bullet point, however step 1 is skipped as it is not fully charged yet. - Either or the above bullet points, however I attach the power cable instead of removing it: 1. All of the expected (the noise and the icon change) happen immediately. I have described this with the Adwaita icon theme, however it is icon theme independent. Related: Bug #1643190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1642718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 886415] Re: No GUI for disabling guest account access
** No longer affects: ubuntu-gnome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/886415 Title: No GUI for disabling guest account access Status in gnome-control-center package in Ubuntu: Invalid Status in unity-control-center package in Ubuntu: Triaged Bug description: Given the tendancy to clone the MacUI, it would appear Ubuntu is missing an equivalent option to disable guest access. In OS X 10.7, you'll find it in a "Security and Privacy" control panel. I'm reporting this against LightDM as the file I had to edit to remove it was /etc/lightdm/lightdm.conf by adding the line: allow-guest=false Not allowing the target audience (people who don't (want to) know how to use the linux command prompt) to turn off guest access doesn't feel right. As it's kind of treated as an account of sorts (albeit temporary), I'd suggest in Ubuntu that perhaps it should be added to the "User Accounts" control panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/886415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1405627] Re: Suspending while a program is fullscreen
This issue is no longer present on trusty. ** Tags removed: trusty ** Changed in: xorg (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-gnome Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1405627 Title: Suspending while a program is fullscreen Status in Ubuntu GNOME: Invalid Status in xorg package in Ubuntu: Invalid Bug description: I have found that my system initiates suspend and goes to sleep when the keyboard and mouse are inactive for the specified amount of time, and this is all very well. However it does it regardless of whether or not an application is fullscreen, and it would be preferable at least for me if this didn't happen. It doesn't happen on Xenial, but it does on Trusty (I originally reported here for Utopic). I haven't tested it on any other versions. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 25 13:17:17 2014 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (19 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-12-13 (11 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Dec 25 11:51:51 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1405627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history - patch
I have tested the packages from -proposed on both Trusty and Xenial and I can confirm that they both solve the problem with no currently noticeable regressions. The package versions I tested were: - Xenial: 0.6.40-2ubuntu11.3 - Trusty: 0.6.35-0ubuntu7.3 I tested the Xenial one in an Ubuntu GNOME 16.04.1 (GNOME 3.18) 64-bit VM, and I tested the Trusty one in an Ubuntu (Unity) 14.04.5 64-bit VM. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history - patch Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Trusty: Fix Committed Status in accountsservice source package in Xenial: Fix Committed Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. [bdmurray] - What could go wrong? What should a user testing this look for? -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
** Patch added: "FixLogoutTimesInLogin-HistoryTrusty.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/accountsservice/+bug/1443052/+attachment/4770694/+files/FixLogoutTimesInLogin-HistoryTrusty.debdiff ** Summary changed: - User accounts login history showing incorrect history + User accounts login history showing incorrect history - patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history - patch Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Xenial: In Progress Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
** No longer affects: unity-control-center (Ubuntu) ** No longer affects: gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Xenial: In Progress Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
You're welcome! It seems as though I accidentally gave it a .patch extension when I should have given it a .debdiff extension. Shall I change that or just leave it as it is? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: In Progress Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
** Description changed: + Impact + --- + + Logout times for users are correct if user logs off and then shutdown + from GDM, however logout times are wrong if user shutdowns directly + from the user session, because DEAD_PROCESS record is missing in that + case and BOOT_TIME record is used instead. + + Therefore the logout time will be shown in the login-history (in the + gnome-control-center) just before the next login time rather than when + the logout actually occurred. + + Test case + -- + + 1. Make sure that you have turned on and logged into the machine and + then turned off from the user session several times with enough distance + between them for you to tell that the timestamps are correct. + + 2. Check that after applying the patch that the timestamps show the + correct times for the logins and logouts and not what is described in + the Impact section above. + + Regression potential + + + I have not encountered any regressions while testing this patch. + + + -- + + Original description: + I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. ** Tags added: patch ** Patch added: "FixLogoutTimesInLogin-History.patch" https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1443052/+attachment/4767052/+files/FixLogoutTimesInLogin-History.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
** Changed in: ubuntu-gnome Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott) ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott) ** Changed in: accountsservice (Ubuntu Xenial) Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1590204] Re: [SRU] Update to bug fix release 3.8.4 in Trusty
** Changed in: ubuntu-gnome Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott) ** Changed in: gnome-contacts (Ubuntu) Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott) ** Changed in: gnome-contacts (Ubuntu Trusty) Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-contacts in Ubuntu. https://bugs.launchpad.net/bugs/1590204 Title: [SRU] Update to bug fix release 3.8.4 in Trusty Status in Ubuntu GNOME: Triaged Status in gnome-contacts package in Ubuntu: Fix Released Status in gnome-contacts source package in Trusty: Triaged Bug description: Impact --- Missing text input box for Address field (LP: #1249947) https://git.gnome.org/browse/gnome-contacts/tree/NEWS?h=gnome-3-8 * Fixed New Contact dialog address field issue Test case -- 1. Install gnome-contact from trusty-proposed 2. Add a New Contact 3. See the text input box for the Address field Regression potential Low, as the fix is small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1590204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1405627] Re: Suspending while a program is fullscreen
** Also affects: ubuntu-gnome Importance: Undecided Status: New ** Changed in: ubuntu-gnome Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1405627 Title: Suspending while a program is fullscreen Status in Ubuntu GNOME: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I have found that my system initiates suspend and goes to sleep when the keyboard and mouse are inactive for the specified amount of time, and this is all very well. However it does it regardless of whether or not an application is fullscreen, and it would be preferable at least for me if this didn't happen. It doesn't happen on Xenial, but it does on Trusty (I originally reported here for Utopic). I haven't tested it on any other versions. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 25 13:17:17 2014 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (19 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-12-13 (11 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Dec 25 11:51:51 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1405627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
So this update should be backported in to prior releases as I can confirm that it does now fix the problem, I think that it didn't work for me immediately because of a local issue on my system caused by something else earlier. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574810] Re: Highlighting and output showing issues on 16.04
I no longer experience this bug on Ubuntu GNOME 16.04, nor any later version. ** Changed in: ubuntu-gnome Status: New => Invalid ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1574810 Title: Highlighting and output showing issues on 16.04 Status in GNOME Terminal: Invalid Status in Ubuntu GNOME: Invalid Status in gnome-terminal package in Ubuntu: Invalid Bug description: I have noticed that on Ubuntu GNOME 16.04 with GNOME 3.20 that often when I execute a command although the cursor goes to the right place and still blinks as it should the output is not shown until I press Enter once more: gnome-terminal_16-04_Execute_Invisible_Output_Issue.png gnome-terminal_16-04_Execute_Shown_Output_Issue.png I have also noticed that often when clicking and dragging to select text though when I copy and paste it somewhere else I can see that all the text was really selected, it doesn't show all the text to be selected (it is normally much more extreme with many more lines missing the highlighting than shown here though): gnome-terminal_16-04_Highlighting_Issue1.png I have also noticed that if I select text but then move my mouse the other way some of the text doesn't get unselected as it should: gnome-terminal_16-04_Highlighting_Issue2.png Don't let the fact that the screenshots are from my Ubuntu (Unity) 16.04 VM confuse you though, the same happens on my GNOME one, I just had my Unity one open at the time when I wanted to take the sreenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1574810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1612343] Re: Unable to delete large folders in Trash
** Changed in: ubuntu-gnome Status: New => Confirmed ** Tags added: yakkety ** Project changed: nautilus => gvfs ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1612343 Title: Unable to delete large folders in Trash Status in gvfs: Confirmed Status in Ubuntu GNOME: Confirmed Status in gvfs package in Ubuntu: New Status in nautilus package in Ubuntu: Triaged Bug description: I have found that since the indicator of file operations was replaced with the notification coming from the right of the top bar rather than a popup window, that I am unable to delete large folders from Trash. Placing them in Trash sometimes means that other items (even really small ones) can't be deleted until the large folders have been moved from Trash to another location, though on other occasions all, or at least half, of the other files will be seemingly successfully deleted, though not the large folder(s). For instance I have a folder with many sub-folders, which each have many sub-sub-folders etc and lots of files... The folder's file size is about 1.7GB. I tried creating a tar of the file which was 1.8GB, I moved that into Trash and it was deleted within about a second with no trouble at all so it seems only to be folders. I looked at the properties for a large folder I placed in Trash by itself, and even though I had clicked the Empty Trash button many times now, it was staying at the same size. I find that the indicator which is meant to be indicating how it's doing to me is always just stuck at "Preparing", even when it actually deletes stuff it only ever really shows that so is not very useful. I am running Ubuntu GNOME 16.04 with GNOME 3.20, but I believe this was also present in 3.18, though not to such a bad degree (pressing the Empty Trash button many times in some cases eventually worked on 3.18, but on 3.20 I can't seem to do anything to delete the folder without first splitting it up). One thing to note though is that if I am to use the right-click option to permanently delete files and folders (which can be enabled in the Preferences) then it deletes them just fine apart from showing a huge and negative amount of files per seconds, but that is for another bug report. I have only tested this in Nautilus, I have not yet tested if it works better in a different file manager, I will comment when I have tested it with a different file manager. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1612343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1612380] Re: Huge unrealistic amount of hours to go shown after successfully moving file/folder
** Changed in: ubuntu-gnome Status: New => Confirmed ** Tags added: yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1612380 Title: Huge unrealistic amount of hours to go shown after successfully moving file/folder Status in Nautilus: Confirmed Status in Ubuntu GNOME: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: For instance I was moving a folder today using Nautilus which told me it would take 5 minutes to move, and it did, the time to completion was actually very accurate, until it finished, at which point it suddenly jumped to this even though it had already succeed in moving the folder in the time it had promised. I see this happen reasonably often. I am running Ubuntu GNOME 16.04 with GNOME 3.20. I have attached a screenshot of what I mean. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1612380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636144] Re: Nautilus needs to be restarted to record top level "item" changes not done through Nautilus
** Bug watch added: GNOME Bug Tracker #768455 https://bugzilla.gnome.org/show_bug.cgi?id=768455 ** Changed in: nautilus Importance: Medium => Unknown ** Changed in: nautilus Status: Confirmed => Unknown ** Changed in: nautilus Remote watch: GNOME Bug Tracker #773416 => GNOME Bug Tracker #768455 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1636144 Title: Nautilus needs to be restarted to record top level "item" changes not done through Nautilus Status in Nautilus: Unknown Status in Ubuntu GNOME: New Status in nautilus package in Ubuntu: New Bug description: I have recently found that after upgrading from Ubuntu GNOME 16.04.1 with GNOME 3.20 to Ubuntu GNOME 16.10 with GNOME 3.22 that in Nautilus the little indicator of how many "items" there are in the top level of the selected directory does not get updated when Nautilus is open if another program creates an item in the directory, though Nautilus will update the indicator if it makes the changes. For instance I launched Nautilus, then I created a directory which had no items currently in it so it was displayed as ""test" selected (containing 0 item)". Then I opened Terminal, cded into the right directory, and executed "touch t.txt". The indicator in Nautilus, no matter what I did, whether I went into the folder and saw that the item was there, or I clicked "Properties" in the right-click menu and got an accurate result, it didn't show the update in items count in the little indicator in the bottom-right-hand corner of Nautilus until I restarted Nautilus. This is the same for creating directories in the directory, not just files. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.22.1-1ubuntu0~yakkety2 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 24 11:56:11 2016 InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-19 (4 days ago) usr_lib_nautilus: dropbox2015.10.28 gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1636144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636144] Re: Nautilus needs to be restarted to record top level "item" changes not done through Nautilus
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #773416 https://bugzilla.gnome.org/show_bug.cgi?id=773416 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=773416 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1636144 Title: Nautilus needs to be restarted to record top level "item" changes not done through Nautilus Status in Nautilus: Unknown Status in Ubuntu GNOME: New Status in nautilus package in Ubuntu: New Bug description: I have recently found that after upgrading from Ubuntu GNOME 16.04.1 with GNOME 3.20 to Ubuntu GNOME 16.10 with GNOME 3.22 that in Nautilus the little indicator of how many "items" there are in the top level of the selected directory does not get updated when Nautilus is open if another program creates an item in the directory, though Nautilus will update the indicator if it makes the changes. For instance I launched Nautilus, then I created a directory which had no items currently in it so it was displayed as ""test" selected (containing 0 item)". Then I opened Terminal, cded into the right directory, and executed "touch t.txt". The indicator in Nautilus, no matter what I did, whether I went into the folder and saw that the item was there, or I clicked "Properties" in the right-click menu and got an accurate result, it didn't show the update in items count in the little indicator in the bottom-right-hand corner of Nautilus until I restarted Nautilus. This is the same for creating directories in the directory, not just files. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.22.1-1ubuntu0~yakkety2 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 24 11:56:11 2016 InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-19 (4 days ago) usr_lib_nautilus: dropbox2015.10.28 gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1636144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635833] [NEW] "No such key 'enable-interactive-search'" message when processing triggers
Public bug reported: Since upgrading from Ubuntu GNOME 16.04.1 with GNOME 3.20 to Ubuntu GNOME 16.10 with GNOME 3.22 I have found that whenever I am installing something which needs to: Processing triggers for libglib2.0-0:amd64 (2.50.0-1) ... That I get the following message immediately after that: No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/20_ubuntu-gnome-default- settings.gschema.override'; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libglib2.0-0 2.50.0-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 22 13:37:33 2016 InstallationDate: Installed on 2016-05-15 (159 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: glib2.0 UpgradeStatus: Upgraded to yakkety on 2016-10-19 (2 days ago) ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1635833 Title: "No such key 'enable-interactive-search'" message when processing triggers Status in Ubuntu GNOME: New Status in glib2.0 package in Ubuntu: New Bug description: Since upgrading from Ubuntu GNOME 16.04.1 with GNOME 3.20 to Ubuntu GNOME 16.10 with GNOME 3.22 I have found that whenever I am installing something which needs to: Processing triggers for libglib2.0-0:amd64 (2.50.0-1) ... That I get the following message immediately after that: No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/20_ubuntu-gnome-default- settings.gschema.override'; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libglib2.0-0 2.50.0-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 22 13:37:33 2016 InstallationDate: Installed on 2016-05-15 (159 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: glib2.0 UpgradeStatus: Upgraded to yakkety on 2016-10-19 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1635833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
Now this is very strange, I restarted my machine, it didn't work. But after restarting it the second time for some reason it started working as it should so I assume that the patch does work, just something odd happened somewhere, but it is all fine now. ** Changed in: accountsservice (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
** Changed in: gnome-control-center (Ubuntu) Status: Fix Released => Confirmed ** Changed in: accountsservice (Ubuntu) Status: Fix Released => Confirmed ** Tags added: yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
I tried it in my Ubuntu GNOME 16.10 with GNOME 3.20 VM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
This update still doesn't fix the issue for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1405627] Re: Suspending while a program is fullscreen
** Description changed: - It would be really useful if you could at least set it so that Ubuntu - does not suspend in a certain amount of time whilst an application is - fullscreen. As I have found this very annoying when streaming, because - even though the program is fullscreen and I am watching something, the - computer thinks that there is no activity and then goes to sleep. - - I understand that not all may want it so that it does not suspend and go to sleep when an application is fullscreen, but at least to have an option to make it register that an application is full screen and therefore not to go to sleep. - You could also be allowed to configure for which applications Ubuntu would not go to sleep for when they are fullscreen. + I have found that my system initiates suspend and goes to sleep when the + keyboard and mouse are inactive for the specified amount of time, and + this is all very well. However it does it regardless of whether or not + an application is fullscreen, and it would be preferable at least for me + if this didn't happen. It doesn't happen on Xenial, but it does on + Trusty (I originally reported here for Utopic). I haven't tested it on + any other versions. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 25 13:17:17 2014 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (19 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-12-13 (11 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Dec 25 11:51:51 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1405627 Title: Suspending while a program is fullscreen Status in xorg package in Ubuntu: Confirmed Bug description: I have found that my system initiates suspend and goes to sleep when the keyboard and mouse are inactive for the specified amount of time, and this is all very well. However it does it regardless of whether or not an application is fullscreen, and it would be preferable at least for me if this didn't happen. It doesn't happen on Xenial, but it does on Trusty (I originally reported here for Utopic). I haven't tested it on any other versions. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname:
[Desktop-packages] [Bug 1405627] Re: Suspending while a program is fullscreen
This issue is still present on Trusty. ** Summary changed: - Suspending while a program is full-screen + Suspending while a program is fullscreen ** Description changed: It would be really useful if you could at least set it so that Ubuntu does not suspend in a certain amount of time whilst an application is - full-screen. As I have found this very annoying when streaming, because - even though the program is full-screen and I am watching something, the + fullscreen. As I have found this very annoying when streaming, because + even though the program is fullscreen and I am watching something, the computer thinks that there is no activity and then goes to sleep. - I understand that not all may want it so that it does not suspend and go to sleep when an application is full-screen, but at least to have an option to make it register that an application is full screen and therefore not to go to sleep. - You could also be allowed to configure for which applications Ubuntu would not go to sleep for when they are full-screen. + I understand that not all may want it so that it does not suspend and go to sleep when an application is fullscreen, but at least to have an option to make it register that an application is full screen and therefore not to go to sleep. + You could also be allowed to configure for which applications Ubuntu would not go to sleep for when they are fullscreen. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 25 13:17:17 2014 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:5002] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (19 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-12-13 (11 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Dec 25 11:51:51 2014 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id 827 - vendor LGD + product id 827 + vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 ** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1405627 Title: Suspending while a program is fullscreen Status in xorg package in Ubuntu: Confirmed Bug description: It would be really useful if you could at least set it so that Ubuntu does not suspend
[Desktop-packages] [Bug 1619900] Re: Search box often appears briefly (though sometimes for longer periods) on New Tab 'blank' page
** Attachment added: "Firefox_Blank_Page_Search_Box.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1619900/+attachment/4733503/+files/Firefox_Blank_Page_Search_Box.png ** Tags added: xenial ** Description changed: I have set it to "Show blank page" on my New Tab however the search box from "Show your top sites" keeps briefly (for a split second) showing up. This happens rather regularly and in most cases. Though sometimes the search bar will last for up to 10 seconds as it did this time: + + Firefox_Blank_Page_Search_Box.png + + I am running Ubuntu GNOME 16.04.1 with GNOME 3.20 and Firefox 48. ** Bug watch added: Mozilla Bugzilla #1300299 https://bugzilla.mozilla.org/show_bug.cgi?id=1300299 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1300299 Importance: Unknown Status: Unknown ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1619900 Title: Search box often appears briefly (though sometimes for longer periods) on New Tab 'blank' page Status in Mozilla Firefox: Unknown Status in Ubuntu GNOME: New Status in firefox package in Ubuntu: New Bug description: I have set it to "Show blank page" on my New Tab however the search box from "Show your top sites" keeps briefly (for a split second) showing up. This happens rather regularly and in most cases. Though sometimes the search bar will last for up to 10 seconds as it did this time: Firefox_Blank_Page_Search_Box.png I am running Ubuntu GNOME 16.04.1 with GNOME 3.20 and Firefox 48. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1619900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619900] [NEW] Search box often appears briefly (though sometimes for longer periods) on New Tab 'blank' page
Public bug reported: I have set it to "Show blank page" on my New Tab however the search box from "Show your top sites" keeps briefly (for a split second) showing up. This happens rather regularly and in most cases. Though sometimes the search bar will last for up to 10 seconds as it did this time: Firefox_Blank_Page_Search_Box.png I am running Ubuntu GNOME 16.04.1 with GNOME 3.20 and Firefox 48. ** Affects: firefox Importance: Unknown Status: Unknown ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1619900 Title: Search box often appears briefly (though sometimes for longer periods) on New Tab 'blank' page Status in Mozilla Firefox: Unknown Status in Ubuntu GNOME: New Status in firefox package in Ubuntu: New Bug description: I have set it to "Show blank page" on my New Tab however the search box from "Show your top sites" keeps briefly (for a split second) showing up. This happens rather regularly and in most cases. Though sometimes the search bar will last for up to 10 seconds as it did this time: Firefox_Blank_Page_Search_Box.png I am running Ubuntu GNOME 16.04.1 with GNOME 3.20 and Firefox 48. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1619900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619814] Re: Can't paste contents from clipboard copied from LibreOffice once it is closed
** Summary changed: - Can't copy and paste from LibreOffice once it is closed + Can't paste contents from clipboard copied from LibreOffice once it is closed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1619814 Title: Can't paste contents from clipboard copied from LibreOffice once it is closed Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: New Bug description: I have found recently that if I copy some text for example from any of the LibreOffice programs, that if I then paste it into another program outside of that suite then it pastes it fine. But if I then close LibreOffice then trying to paste the text does nothing, so closing LibreOffice also gets rid of the contents in the clipboard from it which is not ideal. I am running Ubuntu GNOME 16.04.1 with GNOME 3.20 and LibreOffice version "5.1.4.2 10m0(Build:2)". To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1619814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619814] [NEW] Can't copy and paste from LibreOffice once it is closed
Public bug reported: I have found recently that if I copy some text for example from any of the LibreOffice programs, that if I then paste it into another program outside of that suite then it pastes it fine. But if I then close LibreOffice then trying to paste the text does nothing, so closing LibreOffice also gets rid of the contents in the clipboard from it which is not ideal. I am running Ubuntu GNOME 16.04.1 with GNOME 3.20 and LibreOffice version "5.1.4.2 10m0(Build:2)". ** Affects: df-libreoffice Importance: Unknown Status: Unknown ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Bug watch added: Document Foundation Bugzilla #101868 https://bugs.documentfoundation.org/show_bug.cgi?id=101868 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=101868 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1619814 Title: Can't copy and paste from LibreOffice once it is closed Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: New Bug description: I have found recently that if I copy some text for example from any of the LibreOffice programs, that if I then paste it into another program outside of that suite then it pastes it fine. But if I then close LibreOffice then trying to paste the text does nothing, so closing LibreOffice also gets rid of the contents in the clipboard from it which is not ideal. I am running Ubuntu GNOME 16.04.1 with GNOME 3.20 and LibreOffice version "5.1.4.2 10m0(Build:2)". To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1619814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616994] Re: Firefox should allow showing of built-in DE desktop notifications for certain events
** Description changed: I think it would be really nice if one could get built-in DE desktop notifications when certain events occur such as a download is finished. There could be a section in the Preferences which would allow the user to select which events they want to cause the desktop notification to be shown. - Currently an addon is required to be installed to get this + Currently an add-on is required to be installed to get this functionality, but I think it would be much better if such functionality were built-in. ** Summary changed: - Firefox should allow showing of built-in DE desktop notifications for certain events + Firefox should allow showing of a desktop notification when a download is complete ** Description changed: - I think it would be really nice if one could get built-in DE desktop - notifications when certain events occur such as a download is finished. + I think it would be really nice if like with other browsers Firefox + would show a desktop notification using the style of the DE/OS when a + download has been completed. - There could be a section in the Preferences which would allow the user - to select which events they want to cause the desktop notification to be - shown. - - Currently an add-on is required to be installed to get this - functionality, but I think it would be much better if such functionality - were built-in. + Currently one is required to install an add-on, but I think such basic + functionality should really be built-in. ** Bug watch added: Mozilla Bugzilla #1298077 https://bugzilla.mozilla.org/show_bug.cgi?id=1298077 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1298077 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1616994 Title: Firefox should allow showing of a desktop notification when a download is complete Status in Mozilla Firefox: Unknown Status in Ubuntu GNOME: New Status in firefox package in Ubuntu: New Bug description: I think it would be really nice if like with other browsers Firefox would show a desktop notification using the style of the DE/OS when a download has been completed. Currently one is required to install an add-on, but I think such basic functionality should really be built-in. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1616994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616994] [NEW] Firefox should allow showing of built-in DE desktop notifications for certain events
Public bug reported: I think it would be really nice if one could get built-in DE desktop notifications when certain events occur such as a download is finished. There could be a section in the Preferences which would allow the user to select which events they want to cause the desktop notification to be shown. Currently an add-on is required to be installed to get this functionality, but I think it would be much better if such functionality were built-in. ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1616994 Title: Firefox should allow showing of built-in DE desktop notifications for certain events Status in Ubuntu GNOME: New Status in firefox package in Ubuntu: New Bug description: I think it would be really nice if one could get built-in DE desktop notifications when certain events occur such as a download is finished. There could be a section in the Preferences which would allow the user to select which events they want to cause the desktop notification to be shown. Currently an add-on is required to be installed to get this functionality, but I think it would be much better if such functionality were built-in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1616994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1483276] Re: Unable to launch xdiagnose through the Activities Overview in the normal way
I know it's strange, but I'm almost certain that the version of Ubuntu where I first had the issue, it only came after doing a fresh install, previously it had worked on a fresh install as well. But this update definitely fixes it for me. Seems it doesn't affect all though, but if you can test that the updated version in -proposed doesn't break the functionality for you then I don't see a problem in releasing it if it fixes the problem for those who have it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1483276 Title: Unable to launch xdiagnose through the Activities Overview in the normal way Status in gnome-shell: Confirmed Status in Ubuntu GNOME: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in xdiagnose source package in Xenial: Fix Committed Bug description: Impact == Clicking the icon in GNOME Shell's Activities Overview for xdiagnose fails silently. Nothing happens. xdiagnose is a default app in Ubuntu GNOME so this is a major papercut. Another bug being fixed in this upload is that xdiagnose hard-coded its app icon location making it impossible for icon themes to override it. Test Case = 1. From Ubuntu GNOME 16.04, install the update. 2. Note that GNOME Shell caches app icons so the xdiagnose icon will probably disappear. You can fix this by logging out and logging back or by running Alt-F2 and entering the letter r in the popup. Wait a few moments for gnome-shell to reload. 3. Open the Activies Overview. Search for xdiagnose and click the app in the results. 4. Does xdiagnose run? Does its icon display ok? Regression Potential Low. The primary change basically just copies what Synaptic does with its synaptic-pkexec launcher. Except for the minor glitch with the icon disappearing until GNOME Shell is reloaded, the icon switch is simple. Original Bug Report === I am in need of doing some diagnostics work with "xdiagnose", however when searching for it in the Activities Overview, and then clicking on it, absolutely nothing happens, when in the past it would ask me for my password so that I could run it as root. I looked further into the issue and when trying to run it through Terminal: xdiagnose This was the output I got: Error: Must run as superuser But when running it in Terminal like so: pkexec xdiagnose It prompted for the password as it normally would and should (so pkexec is not the issue). There was also no output from the command: grep -r 'xdiagnose' ~/.local/share/applications And the output of this command "grep -r 'xdiagnose' /usr/share/applications" was: /usr/share/applications/xdiagnose.desktop:Name=xdiagnose /usr/share/applications/xdiagnose.desktop:Exec=pkexec xdiagnose /usr/share/applications/xdiagnose.desktop:Icon=/usr/share/xdiagnose/icons/microscope.svg /usr/share/applications/xdiagnose.desktop:X-Ubuntu-Gettext-Domain=xdiagnose The contents of the file is this: [Desktop Entry] Name=xdiagnose GenericName=Diagnose Graphics Issues Comment=X.org Diagnostic and Repair Utility Exec=pkexec xdiagnose Icon=/usr/share/xdiagnose/icons/microscope.svg Terminal=false Type=Application Categories=System;Settings; X-Ubuntu-Gettext-Domain=xdiagnose I have reinstalled it with "sudo apt-get install --reinstall xdiagnose", however this seems to have made no difference at all to anything. I have also attempted to launch another application via the Activities Overview that uses 'pkexec' to start, and it works fine as normal. I initially experienced this issue on Ubuntu GNOME 15.04 with GNOME 3.16, then on Ubuntu GNOME 15.10 with GNOME 3.18, and now on Ubuntu GNOME 16.04 with GNOME 3.20. Though I remember a time when this issue wasn't present (probably when I was running Ubuntu GNOME 15.04 with GNOME 3.14). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1483276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1483276] Re: Unable to launch xdiagnose through the Activities Overview in the normal way
It is even stranger that in all my GNOME VMs it doesn't work without the version in -proposed, but in my Unity VMs it works fine with the version we have currently and you say it works for you on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1483276 Title: Unable to launch xdiagnose through the Activities Overview in the normal way Status in gnome-shell: Confirmed Status in Ubuntu GNOME: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in xdiagnose source package in Xenial: Fix Committed Bug description: Impact == Clicking the icon in GNOME Shell's Activities Overview for xdiagnose fails silently. Nothing happens. xdiagnose is a default app in Ubuntu GNOME so this is a major papercut. Another bug being fixed in this upload is that xdiagnose hard-coded its app icon location making it impossible for icon themes to override it. Test Case = 1. From Ubuntu GNOME 16.04, install the update. 2. Note that GNOME Shell caches app icons so the xdiagnose icon will probably disappear. You can fix this by logging out and logging back or by running Alt-F2 and entering the letter r in the popup. Wait a few moments for gnome-shell to reload. 3. Open the Activies Overview. Search for xdiagnose and click the app in the results. 4. Does xdiagnose run? Does its icon display ok? Regression Potential Low. The primary change basically just copies what Synaptic does with its synaptic-pkexec launcher. Except for the minor glitch with the icon disappearing until GNOME Shell is reloaded, the icon switch is simple. Original Bug Report === I am in need of doing some diagnostics work with "xdiagnose", however when searching for it in the Activities Overview, and then clicking on it, absolutely nothing happens, when in the past it would ask me for my password so that I could run it as root. I looked further into the issue and when trying to run it through Terminal: xdiagnose This was the output I got: Error: Must run as superuser But when running it in Terminal like so: pkexec xdiagnose It prompted for the password as it normally would and should (so pkexec is not the issue). There was also no output from the command: grep -r 'xdiagnose' ~/.local/share/applications And the output of this command "grep -r 'xdiagnose' /usr/share/applications" was: /usr/share/applications/xdiagnose.desktop:Name=xdiagnose /usr/share/applications/xdiagnose.desktop:Exec=pkexec xdiagnose /usr/share/applications/xdiagnose.desktop:Icon=/usr/share/xdiagnose/icons/microscope.svg /usr/share/applications/xdiagnose.desktop:X-Ubuntu-Gettext-Domain=xdiagnose The contents of the file is this: [Desktop Entry] Name=xdiagnose GenericName=Diagnose Graphics Issues Comment=X.org Diagnostic and Repair Utility Exec=pkexec xdiagnose Icon=/usr/share/xdiagnose/icons/microscope.svg Terminal=false Type=Application Categories=System;Settings; X-Ubuntu-Gettext-Domain=xdiagnose I have reinstalled it with "sudo apt-get install --reinstall xdiagnose", however this seems to have made no difference at all to anything. I have also attempted to launch another application via the Activities Overview that uses 'pkexec' to start, and it works fine as normal. I initially experienced this issue on Ubuntu GNOME 15.04 with GNOME 3.16, then on Ubuntu GNOME 15.10 with GNOME 3.18, and now on Ubuntu GNOME 16.04 with GNOME 3.20. Though I remember a time when this issue wasn't present (probably when I was running Ubuntu GNOME 15.04 with GNOME 3.14). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1483276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1615706] Re: update-notifier has much larger icon in gnome-system-monitor than other processes and than it should
** Changed in: ubuntu-gnome Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1615706 Title: update-notifier has much larger icon in gnome-system-monitor than other processes and than it should Status in Ubuntu GNOME: Confirmed Status in gnome-system-monitor package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: I keep noticing that the update-notifier has a huge icon in the gnome- system-monitor: Big_Icon_gnome-system-monitor.png As you will see in the screenshot I have blacked out most of the processes (for privacy and security reasons) except for the update- notifier and firefox for comparison, all the other processes have an icon the size of firefox's, but seemingly the update-notifier almost always has an absolutely huge one. I am running Ubuntu GNOME 16.04 with GNOME 3.20. I am not sure where the bug is so I am filing this report under both the gnome-system- monitor and the update-notifier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1615706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1615706] Re: update-notifier has much larger icon in gnome-system-monitor than other processes and than it should
** Attachment added: "Big_Icon_gnome-system-monitor.png" https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1615706/+attachment/4725806/+files/Big_Icon_gnome-system-monitor.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1615706 Title: update-notifier has much larger icon in gnome-system-monitor than other processes and than it should Status in Ubuntu GNOME: New Status in gnome-system-monitor package in Ubuntu: New Status in update-notifier package in Ubuntu: New Bug description: I keep noticing that the update-notifier has a huge icon in the gnome- system-monitor: Big_Icon_gnome-system-monitor.png As you will see in the screenshot I have blacked out most of the processes (for privacy and security reasons) except for the update- notifier and firefox for comparison, all the other processes have an icon the size of firefox's, but seemingly the update-notifier almost always has an absolutely huge one. I am running Ubuntu GNOME 16.04 with GNOME 3.20. I am not sure where the bug is so I am filing this report under both the gnome-system- monitor and the update-notifier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1615706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1615706] [NEW] update-notifier has much larger icon in gnome-system-monitor than other processes and than it should
Public bug reported: I keep noticing that the update-notifier has a huge icon in the gnome- system-monitor: Big_Icon_gnome-system-monitor.png As you will see in the screenshot I have blacked out most of the processes (for privacy and security reasons) except for the update- notifier and firefox for comparison, all the other processes have an icon the size of firefox's, but seemingly the update-notifier almost always has an absolutely huge one. I am running Ubuntu GNOME 16.04 with GNOME 3.20. I am not sure where the bug is so I am filing this report under both the gnome-system-monitor and the update-notifier. ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Attachment added: "Big_Icon_gnome-system-monitor.png" https://bugs.launchpad.net/bugs/1615706/+attachment/4725805/+files/Big_Icon_gnome-system-monitor.png ** Also affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Also affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Attachment removed: "Big_Icon_gnome-system-monitor.png" https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1615706/+attachment/4725805/+files/Big_Icon_gnome-system-monitor.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1615706 Title: update-notifier has much larger icon in gnome-system-monitor than other processes and than it should Status in Ubuntu GNOME: New Status in gnome-system-monitor package in Ubuntu: New Status in update-notifier package in Ubuntu: New Bug description: I keep noticing that the update-notifier has a huge icon in the gnome- system-monitor: Big_Icon_gnome-system-monitor.png As you will see in the screenshot I have blacked out most of the processes (for privacy and security reasons) except for the update- notifier and firefox for comparison, all the other processes have an icon the size of firefox's, but seemingly the update-notifier almost always has an absolutely huge one. I am running Ubuntu GNOME 16.04 with GNOME 3.20. I am not sure where the bug is so I am filing this report under both the gnome-system- monitor and the update-notifier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1615706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
