[Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
I'm also affected by this bug on Ubuntu 18.04. This happens both with nvidia-driver-390 and nvidia-driver-396. My graphics card model is a Nvidia GM107GLM [Quadro M1200 Mobile] on a Dell Precision 5520 laptop -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1749007] Re: Snap mounts should be hidden from System Monitor
the patch looks fine but it's a bit weird to add the new argument to the function to the begin of the arguments and not the end, though the API is not public so it shouldn't really matter. It looks fine to me for a SRU so I'm going to sponsor it this week -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1749007 Title: Snap mounts should be hidden from System Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1749007/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Ubiquity also crashes inside a virtual machine (VirtualBox) running on a non-HiDPI host machine. I have observed corrupted graphics in the "main area" of Ubiquity when this bug occurs. By "main area", I am referring to the rendered rectangular area in Ubiquity below the title bar and above the "Copying files..." progress bar. The corruption looks like jagged diagonal lines or "snow". I have seen this on both actual hardware (HiDPI machine scaled at 200%) and in a virtual machine (non-HiDPI hardware scaled at 100%). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768543] [NEW] Difference between appearance in two similar cases
Public bug reported: Ubuntu 18.04 Gnome Shell with Communitheme, also checked with default theme. Steps to reproduce: 1. Open 2 windows of the same application (Terminal in my case) 2. Left click on the icon in the dock and notice how the previews of app's windows and the close button are positioned 3. Click somewhere to close the previews 4. Right click on the icon in the dock 5. Select "All windows" and notice the slight difference in the positions of previews and close button Screenshots attached ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Attachment added: "View of the difference side by side" https://bugs.launchpad.net/bugs/1768543/+attachment/5132083/+files/side_by_side.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1768543 Title: Difference between appearance in two similar cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1768543/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1768541 Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
For those who still see this issue in 18.04: Is the icon really giant (144x144) for you, as attached to this bug; or is it somewhat smaller (48x48), as attached to bug 1765704? Does installing/removing gnome-icon-theme, as per comment 8, do anything for you? If you execute xprop from gnome-terminal, then click on gnome-terminal's window, and scroll back, in what size(s) is/are the icon(s) shown there? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768541] [NEW] package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gn
Public bug reported: installation of this package failed, upgrading from 17.10. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 2 01:39:47 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1 Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb (--unpack): libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-keyring Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1768541 Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768532] [NEW] Popup behind the dock
Public bug reported: Ubuntu 18.04 with Gnome Shell Steps to reproduce: 1. Create a folder on the desktop 2. Press F2 to change the folder's name Expected result: The popup where you can write new name is not obstructed by the dock What happens instead: The popup where you can write new name is partially covered by the dock Screenshot attached ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "Zrzut ekranu z 2018-05-01 12-51-11.png" https://bugs.launchpad.net/bugs/1768532/+attachment/5132041/+files/Zrzut%20ekranu%20z%202018-05-01%2012-51-11.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1768532 Title: Popup behind the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1768532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
Issue remains for me as well 18.04 - 3.28.1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Davide Ads2000 means to hit cancel before retyping your password. Hit cancel, then re-select user, then retype password, all before hitting enter... and hence the purple screen. I believe it's the same problem. This workaround works for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Ads2 The cancel button is not visible (purple screen), your workaround is for another problem. I think it's better to remove it from the bug description. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713581] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
Yeah, I've noticed it... Mh, I'm a bit out of ideas at this point. I'll see if I can find a way to reproduce it. ** Changed in: nautilus (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1713581 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1713581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687864] Re: auto-login and "privacy -> auto screen lock -> disable" do not work
The problem persists on "bionic" as well. Keep trying... (-; -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1687864 Title: auto-login and "privacy -> auto screen lock -> disable" do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1687864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 704504] Re: Run time error in ntfs-config
*** This bug is a duplicate of bug 1768470 *** https://bugs.launchpad.net/bugs/1768470 ** This bug has been marked a duplicate of bug 1768470 Cannot disable device, please remove from archive -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/704504 Title: Run time error in ntfs-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/704504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767817] Re: Full text search does not work
Sorry, but the process seems a bit too complex for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768501] Re: File system problem snapd and others in ubuntu 18.04
*** This bug is a duplicate of bug 1749007 *** https://bugs.launchpad.net/bugs/1749007 ** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1749007 Snap mounts should be hidden from System Monitor -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1768501 Title: File system problem snapd and others in ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1768501/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768501] [NEW] File system problem snapd and others in ubuntu 18.04
Public bug reported: Hi, The monitor is showing more file then usually (16.04 and lower), and it very confusing to see snapd's file too. ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Selection_001.png" https://bugs.launchpad.net/bugs/1768501/+attachment/5131968/+files/Selection_001.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1768501 Title: File system problem snapd and others in ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1768501/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765686] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node()
** Also affects: glib (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Changed in: glib (Ubuntu) Status: New => In Progress ** Changed in: glib (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765686 Title: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib/+bug/1765686/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767953] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from g_hash_table_lookup_node()
*** This bug is a duplicate of bug 1765686 *** https://bugs.launchpad.net/bugs/1765686 ** This bug has been marked a duplicate of bug 1765686 gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1767953 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from g_hash_table_lookup_node() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1749975] Re: Flickering screen with ultra-wide monitor in Wayland mode
I do not experience this issue upon upgrade to 18.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1749975 Title: Flickering screen with ultra-wide monitor in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1749975/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756619] Re: nautilus-actions package missing in Ubuntu 18.04 beta
** Also affects: nautilus-actions (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1756619 Title: nautilus-actions package missing in Ubuntu 18.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1756619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1748611] Re: Desktop symbols disappear after changing symbol size in nautilus
I call the stuff I place on the desktop "symbols" - like files, folders etc. Pictures before and after the changing of the symbol size in nautilus attached. ** Attachment added: "pictures.zip" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1748611/+attachment/5131932/+files/pictures.zip -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1748611 Title: Desktop symbols disappear after changing symbol size in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1748611/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
OK, I can now reproduce the problem at scale=100%. The trick is to slow down the installer with GDK_SYNCHRONIZE=1. So this is just a race condition, usually triggered by slower rendering of scale 200%, but can be triggered other ways. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
So it sounds like a race between Xorg and the ubiquity perms dropping which then breaks Xorg's ability to authenticate XShmAttach used in cairo. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768448] Re: Don't use snaps for default system packages
I see. Well, then I will have to look for another distribution. I would strongly suggest that normal packages be managed system wide with a normal package manager. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768448 Title: Don't use snaps for default system packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768448/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768178] Re: color scheme Solarized Dark is incorrect
Submitted https://git.gnome.org/browse/gnome- terminal/commit/?id=e8ee9f786 to make it more obvious that we indeed define the Solarized palette correctly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1768178 Title: color scheme Solarized Dark is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1768178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Unfortunately I can't tell what in shm_access is failing exactly because
gdb skips straight from shm.c:314 back to the caller. So that suggests
this code path, but I can't verify it:
static int
shm_access(ClientPtr client, SHMPERM_TYPE * perm, int readonly)
{
int uid, gid;
mode_t mask;
int uidset = 0, gidset = 0;
LocalClientCredRec *lcc;
if (GetLocalClientCreds(client, ) != -1) { // FALSE
...
}
/* Otherwise, check everyone else */
mask = S_IROTH;
if (!readonly) {
mask |= S_IWOTH;
}
return (SHMPERM_MODE(perm) & mask) == mask ? 0 : -1;
}
So Xorg _should_ be returning an error, and it is. The problem seems to
be that the client (python3 gtk_ui process) has a real uid=0 and
effective uid=999. So that allows it to connect to Xorg (normally Xorg
rejects root clients), but doesn't allow Xorg to check the client shm
permissions. So Xorg rejects the client's attempt at XShmAttach.
How any of this relates to scale=200% and why it works at 100%, I'm not
sure. We might need to review comment #15 in more detail.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1748611] Re: Desktop symbols disappear after changing symbol size in nautilus
Thank you for your bug report, what do you call "symbol"? Could you take a screenshot showing the issue? ** Package changed: gnome-session (Ubuntu) => nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1748611 Title: Desktop symbols disappear after changing symbol size in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1748611/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Given that XShmAttach can fail (you can google the reasons), I think maybe we need to handle that in ubiquity/cairo and fall back to an alternative rendering method. I'm not so sure we should be treating XShmAttach failure as a bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767542] Re: Turning off WiFi enables Airplane mode
How is that an important issue? It's a best confusing but whether no wifi/bluetooth is showed as equivalent to be in airplane mode or not is just a visual clue being displayed one way or another -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1767542 Title: Turning off WiFi enables Airplane mode To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1767542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768448] Re: Don't use snaps for default system packages
Thank you for your bug report, that's not really a bug and not one in gnome-software. If you want to discuss the use of snaps for those applications https://community.ubuntu.com/ is a better place. Snaps have some issues as you pointed but those are being worked on and are going to be fixed and we believe that providing them as snaps increases the security and is going to make easier updating them to newer versions in the futur so it's not likely we revert that decision. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768448 Title: Don't use snaps for default system packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768448/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768448] Re: Don't use snaps for default system packages
** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768448 Title: Don't use snaps for default system packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768448/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716409] Re: Unable to install flatpakref on Ubuntu artful
This bug seems to have been re-introduced in Ubuntu 18.04 (GNOME Software 3.28.1-0ubuntu4), should I file a new bug or re-open this one? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1716409 Title: Unable to install flatpakref on Ubuntu artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716409/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765390] Re: printer settings: add switch for disable autodetect and add
Sorry for that. I only described the Problem with the Printer Concept/Workflow that is used in Ubuntu. In my opinion this is one Issue, I'm not able to get what is working in Background and what is working how in Background. I'm not familiar with the responsibility in the deep of your developing. In my opinion I don't have to. I barley able to manage to report in this strange and absolute not intuitive Web surface (see also [Bug 1765667] ). I like Ubuntu, but not that much that I would learn to develop some apps. So please do this for me. I'm wondering also that you allow accepting Bugs to this package but are not able to send it further to the correct address. Maybe there is a need of a Feature Request for a better Work-flow in this reporting tool . -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765390 Title: printer settings: add switch for disable autodetect and add To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
** Changed in: glib2.0 (Ubuntu) Status: Incomplete => Invalid ** Changed in: glib2.0 (Ubuntu Bionic) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Getting closer. It's this failing in the Xorg process:
/* The attach was performed with root privs. We must
* do manual checking of access rights for the credentials
* of the client */
if (shm_access(client, &(SHM_PERM(buf)), stuff->readOnly) == -1) {
shmdt(shmdesc->addr);
free(shmdesc);
return BadAccess;
}
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Possibly relevant to permissions: The uid of this process changed from 'root' in 17.10 (where it works), to 'ubuntu' in 18.04 (where it doesn't work). ubuntu4468 17.8 1.2 502716 97352 tty1 Sl+ 08:17 0:01 /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui In both cases the Xorg process is running as 'ubuntu'. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1670009] Re: Remove libunity9 package dependency for nautilus
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1670009 Title: Remove libunity9 package dependency for nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1670009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed
** Changed in: gnome-session (Ubuntu Bionic) Status: New => Triaged ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-session (Ubuntu Bionic) Assignee: (unassigned) => Didier Roche (didrocks) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1720310 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1720310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed
** Branch linked: lp:~ubuntu-desktop/gnome-session/ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1720310 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1720310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed
** Description changed: + [Impact] + + * People having this particular setup: +- removed ubuntu-desktop metapackage from their system +- upgrading from 16.04 to 18.04 (or previously to 17.10) by manually editing /etc/apt/sources.lists without using do-release-upgrade (which reinstalls ubuntu-desktop). + They end up with: + - no ubuntu-dock installed + - and consequentely, the settings migration script would trigger an apport dialog (crashing) due to lack of gsettings schema. + * Even if this is an unsupported case (people shouldn't cowboy sources.list and use our upgrader tools), we can easily prevent this crash, ignoring settings migration in such a case. + + [Test Case] + + 1. Install 16.04 + 2. Remove ubuntu-desktop metapackage + 3. Change your sources.list from "xenial" to "bionic" + 4. apt update && apt full-upgrade + 5. Reboot and log into a new session once upgrade is done. + -> you won't get the ubuntu-dock, but the session migration script shouldn't crash. + + [Regression Potential] + + * The script was crashing (even if there is no settings to migrate, so + it was a no-op). We prevents gsettings to segfault by guarding for + schema existence in the standard way. + + -- + Upgrade... ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 08:15:13 2017 ExecutablePath: /usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py InstallationDate: Installed on 2017-09-25 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py ProcEnviron: - LANGUAGE=ru - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=ru_RU.UTF-8 - SHELL=/bin/bash + LANGUAGE=ru + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 Signal: 5 SourcePackage: gnome-session StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 + ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Also affects: gnome-session (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1720310 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1720310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
This bug is closed due to no response from the original reporter, so please don't add further comments. Everyone else should: 1. If using a release older than 18.04 then apply the workaround from bug 994921 first. 2. Run: ubuntu-bug /var/crash/YOURFILE.crash ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
BTW, we have fixed many gnome-shell bugs with these symptoms recently in Ubuntu 18.04. So please try 18.04 and log a new bug if you have any problems. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768448] [NEW] Don't use snaps for default system packages
Public bug reported: In a fresh install, standard applications like gnome-calculator and gnome-system-monitor are installed as snaps. This results in a plethora of mounted loopback devices for basically nothing. Never mind the slow application startup times (seconds for gnome-system-monitor on a Ryzen 1700 with 32GB RAM and a Samsung EVO 960 on an M.2 interface). Removing the snaps and going back to deb packages, the performance issues go away. I can understand using snaps for third-party commercial software, but for the base system, the default debian package manager has served us well. I consider pushing snaps for default gnome applications a bug, and mismanagement of the system. This does not happen on an upgraded Ubuntu (from 16.04LTS). Snap is there, with no applications installed. That's how the default should be. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768448 Title: Don't use snaps for default system packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768448/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
Right, looks like I was missing ibus-gtk then - reinstalling ubuntu- desktop brought it back. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1760818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
It is nonsense to close an issue if it affects 70+ people. ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1767618] Re: system Brightness & Lock app ignores file permissions
Hi Seth, thanks for your mail. I'm agreed that this is the way the system permissions work. But, did you see the comment I added to the bug report? Further investigation shows that file ownership is also ignored If I change the ownership and permissions of the file, then they are ignored by the Brightness & Lock app eve@steve-laptop:~$ ls -l ~/.config/dconf/user -rw-r--r-- 1 steve eve 15965 Apr 28 10:37 /home/eve/.config/dconf/user ==> Alter lock settings using "Brightness & Lock" app eve@steve-laptop:~$ ls -l ~/.config/dconf/user -rw-rw-r-- 1 eve eve 15965 Apr 28 11:13 /home/eve/.config/dconf/user Eve is no longer the file owner, but is in the group (and she is not in the sudo group), so I don't believe that any process she is running should be able to change the file permissions and ownership. So I am guessing that the screen locking process is either not run by the user, or it is running with elevated privileges, which enable it to overwrite the file with a different privilege set. I understand that the setup that I am looking to configure may not be in the design spec - and there may be better ways to achieve it, but I don't think that it is that uncommon (for example, on my work (Windows 10) laptop, the screen locking settings are all configured by Group IT and are locked, so mere mortals cannot change them. However, I am not convinced that the existing behaviour is desirable - because the screen locking process appears not to check the file permissions and ownership, and uses it's elevated privilege status to overwrite them. All the best, Steve PS. FWIW Eve is thankfully not interested in Unix system hacking. Social engineering on her parents seems a better way to get increased access to funny cat videos :-) Steve Gooberman-Hill Skype: steve.gooberman.hill On 1 May 2018 at 03:35, Seth Arnold <1767...@bugs.launchpad.net> wrote: > This is the way Unix discretionary access controls work. So long as the > files are in Eve's home directory, and she retains ownership of her home > directory, she will be able to rename the ~/.config/ directory and > continue on as she wishes. > > Furthermore, the screen locking is handled by a process that runs as her > user account in her user session. She could simply attach a debugger to > it and lock it solid. Or she could write a little program to keep the > X11 session 'active' and thus keep the screen from locking. Or she could > click on a menu entry every time she walks away from the computer to > keep the screen from locking. Or she could write her own screen locking > program that would act as she wishes. > > You could try using the shadow 'lock account' tools; note that this is > trivial to bypass if she can sit at the computer during bootup, unless > you also take steps to lock the hard drive, lock the bios, and lock the > grub configuration. But it cannot help you enforce screen locking when > you wish. Not much short of forcibly killing her processes or rebooting > the machine will help. > > Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1767618 > > Title: > system Brightness & Lock app ignores file permissions > > Status in gnome-screensaver package in Ubuntu: > Won't Fix > > Bug description: > The "Brightness & Lock" app in "System Settings" is ignoring file > permissions. > > As a sudoo group user, I wish to restrict another user's ability to > change their user settings (particularly the screen lock settings), so > they can't switch the lock off > > (I want to restrict my daughter's access to the laptop, so I control > the password to her account - but she has worked out that she can turn > the screen lock off) > > Using sudo privileges I can change the file permissions on her > dconf/user settings > > steve@steve-laptop:/home/eve$ sudo chmod ug-w ~eve/.config/dconf/user > steve@steve-laptop:/home/eve$ sudo ls -l ~eve/.config/dconf/user > -r--r--r-- 1 eve eve 15965 Apr 28 10:34 /home/eve/.config/dconf/user > > If I then switch to her account, and use the system settings > "Brighness & Lock" app to switch the lock off. I then check the file > permissions on her dconf/user account, and find > > eve@steve-laptop:/home/eve$ sudo ls -l ~eve/.config/dconf/user > -rw-rw-r-- 1 eve eve 15965 Apr 28 10:37 /home/eve/.config/dconf/user > > I don't believe that any user should have permission to overwrite this > file if it has read-only permissions > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: gnome-screensaver 3.6.1-7ubuntu4 > ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 > Uname: Linux 4.4.0-119-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > CurrentDesktop: Unity > Date: Sat Apr 28 10:49:12 2018 > GnomeSessionIdleInhibited: No > GnomeSessionInhibitors: None > GsettingsGnomeSession: >org.gnome.desktop.session session-name 'ubuntu' >
[Bug 1768178] Re: color scheme Solarized Dark is incorrect
> Are you mean new abstraction, third place, preset for background, palette and other? We don't know yet how the user interface would look like. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1768178 Title: color scheme Solarized Dark is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1768178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
I'll keep identifying root cause for this issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
I could reproduce this issue with oem image (somerville 20170614-0). With exactly the same error "dpkg: cycle found while processing triggers:" But can't reproduce this issue with oem image (columbia 20161201-0). Attachment is the log for oem image (columbia 20161201-0). ** Attachment added: "sosreport-u-VirtualBox-20180502021308.tar.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5131826/+files/sosreport-u-VirtualBox-20180502021308.tar.xz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
