[Bug 2059818] Re: Regression: Jammy to Noble, set_label no longer functions
I installed the 58-1 version of gnome-shell-extension-appindicator from noble-proposed and rebooted and can confirm that I now see the label on an appindicator (indicator-sensors in this case) as expected. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059818 Title: Regression: Jammy to Noble, set_label no longer functions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] [NEW] gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Public bug reported: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039577] Re: gnome-control-center incorrectly claims remote login is off
** Information type changed from Private Security to Public Security -- 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/2039577 Title: gnome-control-center incorrectly claims remote login is off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2039577/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2044588] Re: Gnome crash after suspend mode , all openapps auto closed
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/2044588 Title: Gnome crash after suspend mode , all openapps auto closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2041478] Re: /usr/bin/gnome-calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event
Ah I see this is already in 45.1-1 in noble ** Also affects: gnome-calendar (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-calendar (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: gnome-calendar (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2041478 Title: /usr/bin/gnome- calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2041478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2041478] Re: /usr/bin/gnome-calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event
I can reliably reproduce this by just launching gnome-calendar on mantic. This looks to be the same issue as the upstream https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1106 which has an associated fix in https://gitlab.gnome.org/GNOME/gnome- calendar/-/merge_requests/366 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #1106 https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1106 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2041478 Title: /usr/bin/gnome- calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2041478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039607] Re: ClamTK not working properly
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Package changed: gnome-terminal (Ubuntu) => clamtk (Ubuntu) -- 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/2039607 Title: ClamTK not working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamtk/+bug/2039607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031406] Re: [MIR] libei
I reviewed libei 1.0.0-0ubuntu2 as checked into mantic. This shouldn't be considered a full audit but rather a quick gauge of maintainability. libei is a library to emulate input, particularly for the Wayland graphics stack. It provides 3 components - libei - the library to emulate inputs on the client side - libeis - a library to process these inputs on the server side - oeffis - a library for communicating with the XDG RemoteDesktop Portal - CVE History - None - Build-Depends - No interesting / security relevant dependencies - No pre/post inst/rm scripts - No init scripts - No systemd units - No dbus system/session services - No setuid binaries - No binaries in PATH - No sudo fragments - No polkit files - No udev rules - unit tests / autopkgtests - No autopkgtests but since this package is just a library with minimal external depencies, I don't think this should be a blocker. - unit tests look quite comprehensive: 1/9 libei / unit-tests-utils OK 0.02s 2/9 libei / unit-tests-ei OK 0.02s 3/9 libei / unit-tests-eisOK 0.02s 4/9 libei / unit-tests-oeffis OK 0.01s 5/9 libei / eierpeckenOK 0.08s 6/9 libei:python / python-black OK 0.49s 7/9 libei:python / scanner-pytest OK 0.52s 8/9 libei:python / oeffis-pytest OK 2.58s 9/9 libei:python / protocol-test OK 6.61s Ok: 9 Expected Fail: 0 Fail: 0 Unexpected Pass:0 Skipped:0 Timeout:0 - No cron jobs - Build logs contain a couple warnings - the second of which should ideally be fixed: ../tools/ei-demo-client.c:102:9: warning: ignoring return value of read declared with attribute warn_unused_result [-Wunused-result] ../src/util-sources.c:311:9: warning: ignoring return value of read declared with attribute warn_unused_result [-Wunused-result] - No processes spawned - Memory management - Given this is written in C there is suprisingly little dynamic memory management - when malloc() etc are used, the code has a tendency to use assert() to die immediately if memory fails to be allocated. Whilst not very graceful, this is pretty standard in higher order libraries like glib etc so is not really concerning to see it here. In general the code appears quite defensive too. - File IO - Only really used for creating a lock file and reading its own cmdline - again this is quite safe. - Logging - Appears quite careful, no apparent uses of directives that might be vulnerable to string-format attacks etc - Environment variable usage - Only uses XDG_RUNTIME_DIR and its own LIBEI_SOCKET environment variables - No apparent use of privileged functions - Uses rand() to assign a non-overlapping token for requests to xdg-desktop-portal - this is fine, they are not expected to be cryptographically secure etc, they just need to be unique within a session - No use of temp files - Uses AF_UNIX sockets for local communication - No use of WebKit - No use of PolicyKit - No significant cppcheck results - One significant Coverity result - I reported this upstream https://gitlab.freedesktop.org/libinput/libei/-/issues/43 who fixed it within 24 hours - along with a related issue they noticed - No significant shellcheck results - No significant bandit results - all issues identified are in the test suite and most can be ignored (ie. use of assert etc.) - No significant govulncheck results - No significant Semgrep results In general libei looks to be quite a well-written and maintained code- base. The upstream is responsive to issues and easy to work with as well. Security team ACK for promoting libei to main. ** Bug watch added: gitlab.freedesktop.org/libinput/libei/-/issues #43 https://gitlab.freedesktop.org/libinput/libei/-/issues/43 ** Changed in: libei (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- 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/2031406 Title: [MIR] libei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libei/+bug/2031406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982422] Re: Multiple vulnerabilities in Bionic, Focal and Jammy
> All the CVEs fixed by the attached debdiffs have priority low or negligible. > Therefore, these updates should not be sponsored until a higher priority issue > is found in GIMP. I don't think it is right to try and say these should not be sponsored until a higher priority issue is found - it is just that other higher priority updates for other packages will usually take precedence. Please try not to talk with authority about things which you do not have authority over. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1982422 Title: Multiple vulnerabilities in Bionic, Focal and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1982422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
>> I don't think it's appropriate to display that in the settings app. > I suppose that not knowing is more secure? Yes if you consider the risk of users DoS'ing themselves by having to potentially hack around in the CLI / BIOS settings to try and find the right incantations to get a green check mark to appear. The status quo is a lack of awareness - so we need to trade of the risks of showing something which is unactionable and potentially alarming vs. keeping things as they are. Once there is support to rectify these issues from the GUI then I am not at all opposed to showing this information and would welcome it. However even then, we will want to ensure this is a robust process since we don't want to say make it easy to enable Secure Boot and then prevent machines from booting since the user doesn't actually run a signed kernel, or say end up having hardware devices silently disabled on a subsequent reboot since they were previously using unsigned modules etc. There is a lot of complexity and corner cases here so it is prudent to be conservative in our approach IMO. -- 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/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
Indeed - I don't think it is useful to have such information displayed prominently when there is nothing that user's can do to affect this (in general) and so this will only cause alarm. Like Marc said, it is then not useful to display this without offering actionable tasks that a user an perform to increase their security, since then as jbicha suggested, some users will likely try and manually workaround these findings to 'increase' their security and potentially break their systems. Whilst it is commendable that GNOME is trying to perhaps raise security awareness for users, doing this in a way where users don't really have any control over the results is likely to cause more harm than good. So I agree, this should not be part of the standard gnome-control-center at this stage for Ubuntu. -- 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/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 283115] Re: Gimp: toolbox windows can't be minimized
** Changed in: gimp (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/283115 Title: Gimp: toolbox windows can't be minimized To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/283115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
** Changed in: apparmor (Ubuntu Jammy) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
I have verified this as follows: # enable proposed so we can install apparmor from there # https://wiki.ubuntu.com/Testing/EnableProposed cat
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
** Description changed: - Just switched from Ubuntu 20.04 to 22.04 and realized that Document - Viewer no longer open on the last viewed page and doesn't remember the - side pane preference even after using the "Save Current Settings as - Default" option. Kindly advise + [Impact] - ProblemType: Bug - DistroRelease: Ubuntu 22.04 - Package: evince 42.1-3 - ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 - Uname: Linux 5.15.0-25-generic x86_64 - NonfreeKernelModules: nvidia_modeset nvidia - ApportVersion: 2.20.11-0ubuntu82 - Architecture: amd64 - CasperMD5CheckResult: unknown - CurrentDesktop: ubuntu:GNOME - Date: Fri Apr 22 15:58:50 2022 - InstallationDate: Installed on 2022-03-19 (34 days ago) - InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) - ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: evince - UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) + * Evince does not behave as expected and launches with a very small + window resulting in a poor user experience + + * Fixing this requires only a minor change to the exo-open abstraction + and results in correctly functioning evince + + * By removing the dbus deny rule in the exo-open abstraction, evince is + able to correctly communicate with gvfs and start up as normal + + [Test Plan] + + * Start dbus-monitor to watch for AppArmor denials + + $ dbus-monitor --session | grep AppArmor + + * Launch evince and there should be no AppArmor message shown above + from dbus-monitor + + [Where problems could occur] + + * By removing this deny rule from the exo-open abstraction, AppArmor + will be more permissive for anything which uses the exo-open abstraction + and potentially allow it access to gvfs where it did not before. + + * This should not result in any regressions as we are granting extra + functionality which wasn't allowed before, however perhaps in the case + of an application which expects *not* to be able to use gvfs as this was + previously explicitly denied, it may now be able to (if it has a less + specific allow rule) and hence it may function differently than before. + + [Other Info] + + * Whilst on the surface by removing this deny rule it may appear that this grants additional permissions to anything which uses the exo-open abstraction, this is not necessarily true as AppArmor denies all accesses by default unless explicitly allowed by a profile. And so in general this will not grant permission to use a DBus interface that an application did not have before. However, due to the way that deny rules take precedence over allow rules in AppArmor, if an application had been allowed generic dbus access to the user's session bus, the previous deny rule in the exo-open abstraction would then have denied them access to just gvfs via dbus. With this new proposed change, this is not explicitly denied and so is now allowed as expected. But for applcations which may have used the exo-open abstraction and which did *not* have DBus access before, this change will not result in them obtaining DBus access either. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
@georgia so the usual process (as per https://wiki.ubuntu.com/StableReleaseUpdates) from here would be to first get the changes into apparmor/evince in the current devel release (kinetic) and once it is verified that they are working fine there, then we backport them to jammy etc. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
** Also affects: evince (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: evince (Ubuntu Kinetic) Importance: High Status: In Progress ** Also affects: apparmor (Ubuntu Kinetic) Importance: High Status: Confirmed ** Changed in: apparmor (Ubuntu Kinetic) Status: Confirmed => In Progress ** Changed in: apparmor (Ubuntu Jammy) Status: New => In Progress ** Changed in: apparmor (Ubuntu Kinetic) Assignee: (unassigned) => Alex Murray (alexmurray) ** Changed in: apparmor (Ubuntu Jammy) Assignee: (unassigned) => Alex Murray (alexmurray) ** Changed in: apparmor (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
FYI I have sent a MR to the upstream AppArmor project to remove this dbus deny rule from the exo-open abstraction: https://gitlab.com/apparmor/apparmor/-/merge_requests/884 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1968402 Title: Ubuntu 20.04.3 boots to black screen, no TTY available To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1968402/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal
Upstream bug filed https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5242 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5242 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5242 -- 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/1964442 Title: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal
I personally don't think this should be low priority - this affects any application which ends up causing the gnome shell prompt dialog to appear - so in my case when reading my email and opening a GPG encrypted email I get prompted for my GPG passphrase - whilst this is happening my email client is repeatedly getting sent to it, causing it to advance forward to the next email and mark the current one as read - so this has a real usability impact IMO. This is not just relevant to terminal applications etc. -- 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/1964442 Title: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965837] [NEW] Erroneous / extra input generated in requesting application when prompting to unlock keys
Public bug reported: Recently I have noticed that when I am being prompted for the passphrase for to unlock a GPG/SSH key via the gnome-shell prompter, whilst the prompt is visible the requesting window seems to get spammed by input - this can be reproduced via running the following (but replace the gpg recipient with the one of your own user's private key): $ echo RELOADAGENT | gpg-connect-agent; echo foo | gpg --encrypt --recipient alex.mur...@canonical.com | gpg --decrypt See attached for a short video demonstrating the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 11:43:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-03 (230 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-01-14 (66 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screencast from 22-03-22 11:45:41.webm" https://bugs.launchpad.net/bugs/1965837/+attachment/5571537/+files/Screencast%20from%2022-03-22%2011%3A45%3A41.webm -- 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/1965837 Title: Erroneous / extra input generated in requesting application when prompting to unlock keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965837] Re: Erroneous / extra input generated in requesting application when prompting to unlock keys
If it is not clear from the video - watch the terminal window in the background when the prompt for the passphrase appears - it keeps scrolling as though getting input by newlines all the time - and this then persists even after the prompt is dismissed until I manually provide some input myself. -- 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/1965837 Title: Erroneous / extra input generated in requesting application when prompting to unlock keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
See this related debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1006368 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
This appears to be caused (for me at least) by upower 0.99.16-1 - after upgrading today to 0.99.16-2 things are working again as expected. ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1006368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962351] [NEW] login screen shown on inactive monitor
Public bug reported: My laptop is docked with the lid closed and connected to 2 external monitors. After upgrading a bunch of packages from jammy in the last 24 hours I notice that when logging in, both of my external monitors just show the purple background whilst the login dialog was actually displayed on the closed lid of my laptop. Wasn't sure if this should be filed against some other package as it doesn't look like gnome-shell or gdm3 have changed lately (I only see gnome-shell-extension-appindicator and gnome-shell-extension-ubuntu-dock in my apt history that could be related...) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 09:52:39 2022 InstallationDate: Installed on 2021-08-03 (206 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-01-14 (42 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1962351 Title: login screen shown on inactive monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1962351/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
See https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962127 for an ubuntu-bug of the gnome-shell crash file when this occurred for me yesterday. -- 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/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946578] Re: Placeholder for CVE-2021-41133
** Also affects: flatpak (Ubuntu Impish) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: New ** Also affects: flatpak (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1946578 Title: Placeholder for CVE-2021-41133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1946578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Is there any option to do this via portals - ie can evince use https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus- org.freedesktop.portal.OpenURI to open the URI? Would then this allow to avoid going via xdg-open? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892456] security audit
I reviewed malcontent 0.10.0-2 as checked into impish. This shouldn't be considered a full audit but rather a quick gauge of maintainability. malcontent provides a library and application to manage "parental" restrictions for users. It allows to define restrictions on what applications should be presented to the user to be able to be launched, as well as what kinds of applications (as defined by their OARS rating) are allowed to be installed by the user via gnome-software or similar. Currently this is limited to flatpak application IDs so if this was intended to support snaps Ubuntu would have to patch malcontent (as well as potentially gnome-shell and gnome-software/snap-store etc) to support snaps. It does not perform any enforcement itself, instead it provides a means for configuring the policy via a GUI and an library which would then be used by gnome-shell / gnome-software etc and these applications would then do the actual enforcement by filtering their results accordingly. malcontent also includes a PAM plugin to check session time limits and only allow a user to log in if they have not exceeded their allocated time. By design, malcontent states that it is not a security boundary as it's restrictions can potentially be circumvented by simply using applications to launch/install software that do not integrate with the malcontent system. As such, installing or launching applications via the command-line directly would appear to circumvent the malcontent restrictions. As such I do not feel malcontent requires a full security audit as part of the MIR process, however the following is provided as a high-level summary nonetheless. - No CVE History - Interesting Build-Depends: - policykit-1 - pre/post inst/rm scripts - libpam-malcontent: - postinst script registers the pam plugin - prerm script removes the pam plugin - malcontent - postinst script restarts the accounts-daemon service - postrm scripts restarts the accounts-daemon service - No init scripts - No systemd units - No dbus services - No setuid binaries - binaries in PATH: - malcontent: - -rwxr-xr-x root/root 23077 2020-12-10 03:23 ./usr/bin/malcontent-client - malcontent-gui: - -rwxr-xr-x root/root 63792 2021-02-10 00:41 ./usr/bin/malcontent-control - No sudo fragments - polkit files - malcontent: -rw-r--r-- root/root 39834 2021-02-10 00:41 ./usr/share/polkit-1/actions/com.endlessm.ParentalControls.policy -rw-r--r-- root/root 1517 2021-02-10 00:41 ./usr/share/polkit-1/rules.d/com.endlessm.ParentalControls.rules -rw-r--r-- root/root 393 2021-02-10 00:41 ./var/lib/polkit-1/localauthority/10-vendor.d/com.endlessm.ParentalControls.pkla - configures policykit to ensure only admins can modify policies but allows users to introspect their own restrictions. - No udev rules - No autopkgtests - Unit tests run during the build - No cron jobs - Build logs are relatively clean - Processes spawned - GUI supports spawning gnome-control-center to show the user accounts page - this looks safe from command-injection etc. - Memory management - Is written in C but uses glib/gobject APIs and appears quite defensive. - No obvious File IO - Logging is via glib macros and appears careful to avoid overflows / string format vulns etc. - No environment variable usage - No use of privileged functions - No use of cryptography / random number sources etc - No use of temp files - No use of networking - No use of WebKit - Uses PolicyKit to authorise changes to the various restrictions that can be performed via libmalcontent but this is done solely via installing policykit policies for the various actions - No significant cppcheck results - No significant Coverity results Security team ACK for promoting malcontent to main. ** Tags added: security-review-done ** Changed in: malcontent (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to malcontent in Ubuntu. https://bugs.launchpad.net/bugs/1892456 Title: [MIR] malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/1892456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
** Also affects: flatpak (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2
** Also affects: flatpak (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Hirsute) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1911473 Title: Update for ghsa-4ppf-fxf6-vxg2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867735] Re: Can't login after computer locks on idle
gnome-shell is responsible for the lock screen so reassigning to that ** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu) -- 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/1867735 Title: Can't login after computer locks on idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866042] Re: AppIndicator labels are not vertically centered
Image demonstrating the issue ** Attachment added: "Screenshot from 2020-03-04 21-21-01.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1866042/+attachment/5333430/+files/Screenshot%20from%202020-03-04%2021-21-01.png ** Summary changed: - AppIndicator labels are not vertically centered + AppIndicator labels are not centered vertically -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1866042 Title: AppIndicator labels are not centered vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1866042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866042] [NEW] AppIndicator labels are not centered vertically
Public bug reported: After a recent gnome-shell + yaru-theme update, AppIndicator labels are now shown aligned with the top of the top bar instead of aligned vertically centered as previously https://imgur.com/a/jKVP5w9 (This is the indicator-sensors snap, which creates an AppIndicator with a label as per https://github.com/alexmurray/indicator- sensors/blob/master/indicator-sensors/is-indicator.c#L211) Whilst this only became evident after the most recent gnome-shell upgrade it is not clear to me which package this should be filed against, and so am filing it against the appindicator extension initially as directed by Laney in #ubuntu-desktop :) Let me know if there is anything I can do to help debug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 32-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 21:26:31 2020 InstallationDate: Installed on 2019-11-18 (106 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to focal on 2020-01-22 (42 days ago) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Assignee: Marco Trevisan (Treviño) (3v1n0) Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1866042 Title: AppIndicator labels are not centered vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1866042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857539] Re: nautilus crashed with SIGSEGV
@seb128 - I just noticed this - Apport popped up just after login saying Files (aka nautilus) had crashed - and pointed at this bug report. This was the first time I have seen it so not sure if it is reproducible and I didn't take any particular steps to make it occur. -- 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/1857539 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
Thanks for the patch - I've rebuilt gnome-software with it here https://launchpad.net/~alexmurray/+archive/ubuntu/lp1862158 and will let you know how that behaves. -- 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/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
Happened again this morning - see attached for some screenshots which demonstrate the various elements. -- 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/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
Also note after choosing 'Cancel' for the authentication, it notifies to say updates were successfully installed which is very odd :/ ** Attachment added: "Notification of updated snaps even though operation was not authorised" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+attachment/5326026/+files/Screenshot%20from%202020-02-07%2008-18-20.png -- 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/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
Happened again this morning - see attached for some screenshots which demonstrate the various elements. ** Attachment added: "polkit dialog trigged automatically with no user interaction" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+attachment/5326025/+files/Screenshot%20from%202020-02-07%2008-18-07.png -- 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/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
** Attachment added: "journalctl --grep gnome-software --since 'Thu 2020-02-06 05:40:25 ACDT'" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+attachment/5325864/+files/journalctl--grep-gnome-software-for-today.log -- 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/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
Attached log output for gnome-software (if there is a better way to obtain this or more complete logs for gnome-software please let me know). -- 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/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862158] [NEW] gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
Public bug reported: Every morning about ~30mins after powering on my focal machine I get (unprompted) a gnome-shell policykit authorisation popup saying 'authentication is required to install software' - I haven't yet actually authorised it since I wasn't sure what was causing it, however I notice that if I cancel the authorisation then I see a bunch of notifications from gnome-software about updates having been successfully installed (even though I presume it hasn't been since I never authorised it). Is gnome-software fighting snapd to refresh snaps? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 21:37:29 2020 InstallationDate: Installed on 2019-11-18 (79 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.2-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
@gunnarhj - updated packages for ibus are now available in the ubuntu- security-proposed PPA at https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa Also I note the bug descriptions lists ibus in Focal as Fix Released - but the latest version in focal (1.5.21-1~exp2ubuntu2) is the one with the patch reverted - would you like me to upload an updated focal version as well to the above PPA? -- 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/1844853 Title: IBus no longer works in Qt applications after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828116] Re: Password works uppercase and lowercase
** Information type changed from Private Security to Public Security ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- 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/1828116 Title: Password works uppercase and lowercase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor
>From a security PoV this is basic security by obscurity and effectively pointless - they are simply XORing each byte with a fixed value and then base64 encoding it - since the source code is public anyone can easily find this out and hence easily decode it - the only way to do this securely would be to have the DBus peers negotiate a session key and encrypt it properly using this - so I don't think there is any point adding this faux-encryption in this case. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1828124 Title: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772791] Re: Lock/login screen displays password in clear text occasionally
https://gitlab.gnome.org/GNOME/gnome-shell/issues/460#note_331931 seems to offer a pretty compelling explanation of why this might be seen inadvertently. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #460 https://gitlab.gnome.org/GNOME/gnome-shell/issues/460 -- 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/1772791 Title: Lock/login screen displays password in clear text occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772791/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821003] Re: Screen locking issue
*** This bug is a duplicate of bug 1772791 *** https://bugs.launchpad.net/bugs/1772791 ** This bug has been marked a duplicate of bug 1772791 Lock/login screen displays password in clear text occasionally ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1821003 Title: Screen locking issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1821003/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812436] Re: Display locking leaves the Ubuntu dock available and functional
*** This bug is a duplicate of bug 1769383 *** https://bugs.launchpad.net/bugs/1769383 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1769383, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Information type changed from Private Security to Public Security ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1769383 Ubuntu dock/launcher is shown on the lock screen -- 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/1812436 Title: Display locking leaves the Ubuntu dock available and functional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812436/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770871] Re: [MIR] libcue
I reviewed libcue (2.2.1-2) from disco. This is not a full security audit but rather a quick gauge of maintainability. libcue is a library to parse CUE sheets / files (metadata which describes how tracks of a CD or DVD are layed out). Stored as plain text and commonly have the .cue extension. Parsed via flex / bison. - Build dependencies: - bison, cmake, debhelper-compat, flex - No CVE history - no pre or postinst scripts - no systemd unit files - no system dbus services - no setuid files - no binaries in PATH - no sudo fragments - no udev rules - tests run during the build, seems reasonably extensive - no cron jobs - clean build log other than warning regarding possible buffer overflow in time_frame_to_mmssff() - see below - doesn't spawn other processes - memory management looked careful - file IO - reads from FILE* via flex, doesn't directly open files - minimal logging, looked fine - no environment variables used - no ioctl() or other privileged syscalls - Does not use cryptography - Does not use DBus - Does not use webkit - Does not use temporary files - Does not use javascript - No cppcheck errors - Does not use polkit - Potential for signed integer overflow in time_msf_to_frame() if time is negative - Potential for buffer overflow in time_frame_to_mmssff() if time is negative - Both would be fixed if time was treated everywhere as an unsigned quantity rather than signed integral types (int/long) - ACK from security team to promote to main. ** Changed in: libcue (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libcue in Ubuntu. https://bugs.launchpad.net/bugs/1770871 Title: [MIR] libcue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcue/+bug/1770871/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
Tested the new version in cosmic-proposed on an up-to-date cosmic VM by inserting a USB drive with the attached autorun.inf and it passes. Steps to test locally as follows: 1. Enabled cosmic-proposed 2. sudo apt-get dist-upgrade 3. sudo reboot On next boot with the autorun.inf on a local USB drive: $ dmesg | grep gvfs $ apt-cache policy gvfs gvfs: Installed: 1.38.1-0ubuntu1.1 Candidate: 1.38.1-0ubuntu1.1 Version table: *** 1.38.1-0ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.38.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
Tested the version from bionic-proposed in an up-to-date VM and it passed Steps to test locally as follows: 1. Enabled bionic-proposed 2. sudo apt-get dist-upgrade 3. sudo reboot On next boot with the autorun.inf on a local USB drive: $ dmesg | grep gvfs $ apt-cache policy gvfs gvfs: Installed: 1.36.1-0ubuntu1.2 Candidate: 1.36.1-0ubuntu1.2 Version table: *** 1.36.1-0ubuntu1.2 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.36.1-0ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1.36.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
Tested the version from cosmic-proposed in an up-to-date VM and it failed - looks like this is not actually applied during the build - see the build log https://launchpadlibrarian.net/398362236/buildlog_ubuntu- cosmic-amd64.gvfs_1.38.1-0ubuntu1_BUILDING.txt.gz and notice it is never listed during unpacking Steps to test locally as follows: 1. Enabled cosmic-proposed 2. sudo apt-get dist-upgrade 3. sudo reboot On next boot with the autorun.inf on a local USB drive: $ dmesg | grep gvfs [ 57.813663] gvfs-udisks2-vo[1777]: segfault at 7fe470b0a180 ip 7fe470a5b6a6 sp 7ffeeec746f0 error 4 in libpcre.so.3.13.3[7fe470a45000+52000] [ 176.066448] gvfs-udisks2-vo[2294]: segfault at 7f9bf21c9180 ip 7f9bf211a6a6 sp 7ffd2cc2ef60 error 4 in libpcre.so.3.13.3[7f9bf2104000+52000] $ apt-cache policy gvfs gvfs: Installed: 1.38.1-0ubuntu1 Candidate: 1.38.1-0ubuntu1 Version table: *** 1.38.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.38.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages ** Tags removed: verification-needed-cosmic ** Tags added: verification-failed-cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
@Seb - also I rebuilt gvfs locally for bionic with that upstream patch added and can confirm it does not segfault after that - would be happy to test your SRUd version and confirm it as well if needed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
@Seb - so there is an autorun.inf in the original tarball which can be used (I will attach it separately here as well) - and this reproduces the crash for me - I just copied it to a FAT formatted USB drive, plugged it in and then in dmesg: [ 40.361136] gvfs-udisks2-vo[1563]: segfault at 7f3c60a485e0 ip 7f3c6099ef86 sp 7ffe34884e10 error 4 in libpcre.so.3.13.3[7f3c60983000+7] [ 51.023933] gvfs-udisks2-vo[1805]: segfault at 7fb5ef2205e0 ip 7fb5ef176f86 sp 7fff3e059160 error 4 in libpcre.so.3.13.3[7fb5ef15b000+7] And eventually apport popped up as well (gvfs-udisks2-volume-monitor crashed with SIGSEGV in pcre_exec()). ** Attachment added: "autorun.inf" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+attachment/5212446/+files/autorun.inf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802981] Re: Lockscreen shown dash when screen was locked
*** This bug is a duplicate of bug 1769383 *** https://bugs.launchpad.net/bugs/1769383 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1769383, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Information type changed from Private Security to Public Security ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1769383 Ubuntu dock/launcher is shown on the lock screen -- 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/1802981 Title: Lockscreen shown dash when screen was locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1802981/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802349] Re: video is not playing in the default player and ear phone sound is not working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1802349 Title: video is not playing in the default player and ear phone sound is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1802349/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798725] Re: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*=
This was fixed in upstream commit https://gitlab.gnome.org/GNOME/gvfs/commit/a23eb6f14eb3cffa1585d4e5e566f779337d1e04 Uncertain whether this qualifies as a security issue - there doesn't seem to be any real security impact from the bug - so unmarking this as a security issue now. ** Information type changed from Public Security to Public ** Summary changed: - Content "n\xff=" can crash libpcre when an application is matching the pattern \s*= + gvfs may crash when parsing non-valid UTF8 in autorun.inf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798725] Re: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*=
Seems this is a bug in gvfs not properly validating as UTF8 before calling into glib: https://bugs.exim.org/show_bug.cgi?id=2330#c9 ** Package changed: pcre3 (Ubuntu) => gvfs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793973] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1793973 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/ubuntu/+source/gnome-menus/+bug/1793973/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791433] Re: Path traversal vulnerability
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1791433 Title: Path traversal vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1791433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784888]
*** This bug is a duplicate of bug 1784852 *** https://bugs.launchpad.net/bugs/1784852 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1784852, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1784852 Login / switch user passwords visible on screen! -- 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/1784888 Title: password appears in clear after login with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1784888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784852] Re: Login / switch user passwords visible on screen!
Ignore comment #2 - I misread bug #1779637 - this bug is distinct from that. Can you provide any details as to whether you are using the X or the Wayland session? ** This bug is no longer a duplicate of bug 1779637 Password visible at login screen -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1784852 Title: Login / switch user passwords visible on screen! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1784852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784888] Re: password appears in clear after login with gdm3
*** This bug is a duplicate of bug 1784852 *** https://bugs.launchpad.net/bugs/1784852 Also wrong duplicate - ignore comment #4 as well. -- 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/1784888 Title: password appears in clear after login with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1784888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784888]
*** This bug is a duplicate of bug 1784852 *** https://bugs.launchpad.net/bugs/1784852 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1779637, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. -- 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/1784888 Title: password appears in clear after login with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1784888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784888] Re: password appears in clear after login with gdm3
*** This bug is a duplicate of bug 1784852 *** https://bugs.launchpad.net/bugs/1784852 Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Information type changed from Public to Public Security -- 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/1784888 Title: password appears in clear after login with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1784888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784888] Re: password appears in clear after login with gdm3
*** This bug is a duplicate of bug 1784852 *** https://bugs.launchpad.net/bugs/1784852 Apologies - ignore comment #2 - wrong bug. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1784888 Title: password appears in clear after login with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1784888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784852] Re: Login / switch user passwords visible on screen!
*** This bug is a duplicate of bug 1779637 *** https://bugs.launchpad.net/bugs/1779637 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1779637, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Information type changed from Private Security to Public Security ** Changed in: gdm (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1779637 Password visible at login screen -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1784852 Title: Login / switch user passwords visible on screen! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1784852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
Ok so any guidance as to how to proceed - Jeremy do you have a preference for how this should work? Would you like it to also support Debian in a similar manner and link to the Debian CVE tracker? In this case would you prefer runtime detection (via say /etc/os-release) or compile-time selection of which CVE tracker to link to? -- 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/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784489] Re: nautilus-desktop crashed with SIGSEGV in discovered_cb()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1784489 Title: nautilus-desktop crashed with SIGSEGV in discovered_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1784489/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
The upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=579859 ** Bug watch added: GNOME Bug Tracker #579859 https://bugzilla.gnome.org/show_bug.cgi?id=579859 -- 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/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
The other option would be to do it "properly" the way upstream want - ie. to have the user be able to configure their one linkification. I am happy to rework the patch - is there any interest in carrying this just in Ubuntu or would the preference be to push it to Debian and get it into Ubuntu that way? Also do we know if Debian are interested - since I'd rather not rework the patch a lot unless there was a clear path to getting it into Debian first. -- 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/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775329] [NEW] Feature request: Add a handler for CVE URLs
Public bug reported: Provide automatic link handling for CVE identifiers back to the Ubuntu Security team's CVE database (useful when looking at package changelog's which have security fixes etc). ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Debdiff against current bionic version adding this feature" https://bugs.launchpad.net/bugs/1775329/+attachment/5149173/+files/gnome-terminal_3.28.1-1ubuntu1.2.debdiff -- 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/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 708382] Re: [regression] cannot create "custom" preferred applications
This also affects other mail applications like gnome-gmail (bug #729357) and desktop-webmail since neither can set themselves as the default mail application - at the moment there is a patch for gnome-gmail in the attached bug, but it would seem a better solution would be to fix this in gnome-control-center so all apps work like they did previously, rather than having to patch each app's desktop file individually. -- 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/708382 Title: [regression] cannot create "custom" preferred applications -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty
@Chris - sorry to bug you but just wanted to ping you again about sponsoring this Thanks. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty
Thanks Chris. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty
@pitti - Any update on when this will be uploaded? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty
Have just finished successfully building and testing the patch in Natty (see description for link to build log). Any update on the FFE? Any more info required? ** Description changed: Binary package hint: gnome-power-manager The version of upower (0.9.8) in Natty now has support for controlling keyboard backlights via dbus, and upstream g-p-m git HEAD (soon to be released 3.0 for GNOME 3) just added support for controlling these, however the version of g-p-m shipped in Natty (2.32) does not have any such support. Keyboard backlight support was previously available via HAL in Hardy but was then removed when the dehalsification started and no such support has been available since, and as such adding support to g-p-m in Natty is (and has been for a while) greatly needed. I have written a patch against g-p-m 2.32 which provides such support and is similar to the support recently added to g-p-m 3.0. This patch adds a new GpmBacklightKbd object to g-p-m (which is based on the existing GpmBacklight object which controls the LCD backlight) to control the UPower KbdBacklight DBus interface and the patch provides support for: * controlling the backlight via the appropriate backlight up / down buttons * automatically dimming the backlight on idle when the lcd is dimmed * automatically shutting of the keyboard backlight when the lcd is shut off * displaying the keyboard brightness level via notify-osd (like we do for lcd backlight level) when changed by the user I have tested this patch significantly myself over numerous days with no issues. After a quick post on the ubuntuforums (http://ubuntuforums.org/showthread.php?t=1694678) at least one other user has also confirmed this patch as working well and providing a reasonable improvement over current sub-optimum methods of controlling the keyboard backlight (such as using pommed, which is only available for MacBook machines and does not support other laptops with keyboard backlights such as various Asus models, which the upower + g-p-m method does). I am requesting a FFE to merge the attached patch into g-p-m in Natty to provide such support. - A build log for g-p-m 2.32 in Maverick using the attached patch is - available my ppa (amd64 version - https://launchpad.net/~alexmurray/+archive/ppa/+buildjob/2283751/+files - /buildlog_ubuntu-maverick-amd64.gnome-power- - manager_2.32.0-0ubuntu2_BUILDING.txt.gz). - - I am currently installing a natty daily vm to test building of the Natty - version of g-p-m 2.32 with this patch, but due to the almost identical - nature of g-p-m in Natty and Maverick I do not expect any problems. + A build log for g-p-m 2.32 in Natty using the attached patch is + available my ppa (http://launchpadlibrarian.net/65256989 + /buildlog_ubuntu-natty-i386.gnome-power- + manager_2.32.0-2ubuntu2_BUILDING.txt.gz). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty
Have updated bug description with info for the FFE. Will update again soon once I confirm the patch is correct for Natty. ** Description changed: Binary package hint: gnome-power-manager - upower 0.9.8 supports controlling keyboard backlights and exposes an - appropriate dbus interface to control them. + The version of upower (0.9.8) in Natty now has support for controlling + keyboard backlights via dbus, and upstream g-p-m git HEAD (soon to be + released 3.0 for GNOME 3) just added support for controlling these, + however the version of g-p-m shipped in Natty (2.32) does not have any + such support. - g-p-m can simply access this to control keyboard backlights in much the - same way as it does for lcd / display backlights. + Keyboard backlight support was previously available via HAL in Hardy but + was then removed when the dehalsification started and no such support + has been available since, and as such adding support to g-p-m in Natty + is (and has been for a while) greatly needed. - Attached is a patch to implement such support - this is against g-p-m in - maverick but should apply pretty cleanly for natty since we are still - using the same version. + I have written a patch against g-p-m 2.32 which provides such support + and is similar to the support recently added to g-p-m 3.0. + + This patch adds a new GpmBacklightKbd object to g-p-m (which is based on + the existing GpmBacklight object which controls the LCD backlight) to + control the UPower KbdBacklight DBus interface and the patch provides + support for: + + * controlling the backlight via the appropriate backlight up / down buttons + * automatically dimming the backlight on idle when the lcd is dimmed + * automatically shutting of the keyboard backlight when the lcd is shut off + * displaying the keyboard brightness level via notify-osd (like we do for lcd backlight level) when changed by the user + + I have tested this patch significantly myself over numerous days with no + issues. After a quick post on the ubuntuforums + (http://ubuntuforums.org/showthread.php?t=1694678) at least one other + user has also confirmed this patch as working well and providing a + reasonable improvement over current sub-optimum methods of controlling + the keyboard backlight (such as using pommed, which is only available + for MacBook machines and does not support other laptops with keyboard + backlights such as various Asus models, which the upower + g-p-m method + does). + + I am requesting a FFE to merge the attached patch into g-p-m in Natty to + provide such support. + + A build log for g-p-m 2.32 in Maverick using the attached patch is + available my ppa (amd64 version + https://launchpad.net/~alexmurray/+archive/ppa/+buildjob/2283751/+files + /buildlog_ubuntu-maverick-amd64.gnome-power- + manager_2.32.0-0ubuntu2_BUILDING.txt.gz). + + I am currently installing a natty daily vm to test building of the Natty + version of g-p-m 2.32 with this patch, but due to the almost identical + nature of g-p-m in Natty and Maverick I do not expect any problems. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty
** Summary changed: - g-p-m should add support for controlling keyboard backlight via upower in natty + FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: FFE: Add support to g-p-m for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: g-p-m should add support for controlling keyboard backlight via upower in natty
No worries Chris, will see what I can get together - should I file a separate bug report for the FFE or just put all the required information into this one? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: g-p-m should add support for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: g-p-m should add support for controlling keyboard backlight via upower in natty
Upstream have accepted the updated patch (http://git.gnome.org/browse /gnome-power- manager/commit/?id=7e5fedb32bfb9dc6428c5b0eb21ef48a27602a27) so there is no worries that we are deviating too far with this extra patch against 2.32. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: g-p-m should add support for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: g-p-m should add support for controlling keyboard backlight via upower in natty
A similar patch has been sent upstream http://mail.gnome.org/archives /gnome-power-manager-list/2011-February/msg00017.html which should hopefully get accepted - the upstream codebase is quite a bit different now after transitioning to Gtk 3 and other Gnome 3 related changed so the patch here is a bit different but it achieves the same outcomes. Would be great to see it get included for natty. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: g-p-m should add support for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: g-p-m should add support for controlling keyboard backlight via upower in natty
I've got packages in my ppa to test this implementation under maverick if interested (currently waiting to build...) https://launchpad.net/~alexmurray/+archive/ppa ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: g-p-m should add support for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] Re: g-p-m should add support for controlling keyboard backlight via upower in natty
** Patch added: "Patch to implement keyboard backlight support in g-p-m 2.32 for natty" https://bugs.launchpad.net/bugs/724324/+attachment/1868852/+files/99-keyboard-backlight-support.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: g-p-m should add support for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 724324] [NEW] g-p-m should add support for controlling keyboard backlight via upower in natty
Public bug reported: Binary package hint: gnome-power-manager upower 0.9.8 supports controlling keyboard backlights and exposes an appropriate dbus interface to control them. g-p-m can simply access this to control keyboard backlights in much the same way as it does for lcd / display backlights. Attached is a patch to implement such support - this is against g-p-m in maverick but should apply pretty cleanly for natty since we are still using the same version. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/724324 Title: g-p-m should add support for controlling keyboard backlight via upower in natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 583660] Re: GDM doesn't start at boot time (I need to run it from terminal)
*** This bug is a duplicate of bug 459639 *** https://bugs.launchpad.net/bugs/459639 ** This bug is no longer a duplicate of bug 532436 nvidia driver sometime does not load at boot ** This bug has been marked a duplicate of bug 459639 X server starts randomly in failsafe when starting from cold boot -- GDM doesn't start at boot time (I need to run it from terminal) https://bugs.launchpad.net/bugs/583660 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 555585] Re: No battery level indication
*** This bug is a duplicate of bug 427805 *** https://bugs.launchpad.net/bugs/427805 ** This bug has been marked a duplicate of bug 427805 usb_find_devices() crashed with SIGSEGV in free() -- No battery level indication https://bugs.launchpad.net/bugs/85 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 555585] Re: No battery level indication
This is due to a crash in upowerd which is inturn caused by a bug in libusb, marking as dupe against bug #427805 -- No battery level indication https://bugs.launchpad.net/bugs/85 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 513716] Re: [lucid] battery status not detected/shown until /proc entry viewed
@Vladimir - that doesn't sound like a bug to me - of course it will fail to display if set to only display when charging / discharging and battery is at 100% with AC since it *isn't* charging / discharging, it's full. This is just the correct, expected behaviour for that setting. If you want it to be always visible regardless of if its charging / discharging then change that setting appropriately. -- [lucid] battery status not detected/shown until /proc entry viewed https://bugs.launchpad.net/bugs/513716 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544864] Re: rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed.
As a note - this is actually an assert failure in nspluginwrapper, rather than flashplayer itself - which is needed for the 32-bit flash player on 64-bit ubuntu - as a result it can be worked around by manually installing the native 64-bit adobe flash plugin from http://labs.adobe.com/downloads/flashplayer10_64bit.html (simply copy libflashplayer.so to $HOME/.mozilla/plugins - you may need to create the directory). ** Also affects: nspluginwrapper (Ubuntu) Importance: Undecided Status: New -- rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. https://bugs.launchpad.net/bugs/544864 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544864] Re: rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed.
Why low importance? This crash makes the music store completely useless when adobe-flash-plugin is installed as it consistently crashes... -- rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. https://bugs.launchpad.net/bugs/544864 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544864] Re: rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed.
accidentally assigned to ubuntu, reverting ** Also affects: rhythmbox-ubuntuone-music-store Importance: Undecided Status: New ** Package changed: rhythmbox (Ubuntu) => ubuntu ** Package changed: ubuntu => rhythmbox (Ubuntu) ** Changed in: rhythmbox-ubuntuone-music-store Assignee: (unassigned) => Rodrigo Moya (rodrigo-moya) -- rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. https://bugs.launchpad.net/bugs/544864 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 545180] Re: Rhythmbox crashes when trying to view albums in U1MS
*** This bug is a duplicate of bug 544864 *** https://bugs.launchpad.net/bugs/544864 Marked as dupe against #544864 as this has a stack trace from the crash and appears symtom-wise identical ** This bug has been marked a duplicate of bug 544864 rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. -- Rhythmbox crashes when trying to view albums in U1MS https://bugs.launchpad.net/bugs/545180 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu (via bug 544864). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544864] Re: rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed.
As can be seen from the stacktrace this looks like a crash in the flash player, and after uninstalling adobe flash player I can no longer reproduce this crash. Will try later with gnash or swfdec perhaps... this is a shame as in general the adobe flash plugin is perfectly stable in Chrome / Firefox -- rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. https://bugs.launchpad.net/bugs/544864 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544864] Re: rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed.
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/41695726/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/41695727/Disassembly.txt ** Attachment added: "GConfNonDefault.txt" http://launchpadlibrarian.net/41695728/GConfNonDefault.txt ** Attachment added: "GstreamerVersions.txt" http://launchpadlibrarian.net/41695729/GstreamerVersions.txt ** Attachment added: "LogAlsaMixer.txt" http://launchpadlibrarian.net/41695730/LogAlsaMixer.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/41695731/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/41695732/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/41695733/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/41695734/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/41695735/ThreadStacktrace.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/41695737/XorgLog.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/41695738/XsessionErrors.txt ** Also affects: rhythmbox-ubuntuone-music-store (Ubuntu) Importance: Undecided Status: New -- rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. https://bugs.launchpad.net/bugs/544864 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544864] [NEW] rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed.
Public bug reported: Binary package hint: rhythmbox Crashed when trying to use ubuntuone-music-store plugin - as am in Australia I get the world store, and I simply clicked on the first item listed in 'World Store Top Picks' on the front page (Oasis - Definitely Maybe) and rhythmbox crashed. I can reliably reproduce this by clicking any item on the front page. ProblemType: Crash Architecture: amd64 AssertionMessage: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. CrashCounter: 1 Date: Tue Mar 23 19:02:18 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1) NonfreeKernelModules: wl nvidia Package: rhythmbox 0.12.7-0ubuntu7 ProcCmdline: rhythmbox ProcEnviron: LANG=en_AU.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Signal: 6 SourcePackage: rhythmbox StacktraceTop: raise () from /lib/libc.so.6 abort () from /lib/libc.so.6 __assert_fail () from /lib/libc.so.6 ?? () ?? () Title: rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. Uname: Linux 2.6.32-16-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Affects: rhythmbox-ubuntuone-music-store (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lucid -- rhythmbox assert failure: rhythmbox: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. https://bugs.launchpad.net/bugs/544864 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 493398] Re: Funny Dialog Box?
To reproduce, lock your screen, then click the leave a message button, and type in ' Give me your password' or whatever you want, then click OK. Finally unlock the screen and voila! ** Changed in: gnome-screensaver (Ubuntu) Status: Incomplete => Invalid -- Funny Dialog Box? https://bugs.launchpad.net/bugs/493398 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
