[Bug 1879122] Re: Cannot enable wifi hotspot on the first attempt
** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879122 Title: Cannot enable wifi hotspot on the first attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1879122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879188] Re: python 3.8 pyvenv "You must install..." loop
Was able to reproduce using the steps set out above. ** Changed in: python3.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879188 Title: python 3.8 pyvenv "You must install..." loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1879188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755452] Re: ubiquity crashed with ValueError in command(): I/O operation on closed file.
Able to recreate on Ubuntu Desktop amd64 20.10 daily 20200516 ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755452 Title: ubiquity crashed with ValueError in command(): I/O operation on closed file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872222] [NEW] [WH-CH700N, playback] fails after a while
Public bug reported: Whether I'm watching something, or doing something else whilst listening to playback, the playback stops and starts intermittently. Only happens on Bluetooth, not on Aux. CPU/RAM usage not high when issue occurs. As well as this, my bluetooth driver is not supported out of the box, so had to download 3rd party firmware file. Firmware file from here: https://github.com/winterheart/broadcom-bt-firmware Was the only solution that worked, possibly defective? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1395 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 19:18:26 2020 InstallationDate: Installed on 2020-04-10 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: WH-CH700N Symptom_PulseAudioLog: Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:56:08 tom-Laptop systemd[803]: pulseaudio.service: Succeeded. Apr 11 18:56:18 tom-Laptop systemd[803]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [WH-CH700N, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.50:bd10/08/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTUE-04L00VEN:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.sku: INVALID dmi.product.version: PSKTUE-04L00VEN dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: [WH-CH700N, playback] fails after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853838] [NEW] gnome-control-center crashes with SIGSEGV when selecting display
Public bug reported: Ubuntu eoan gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status I have a DELL XPS 13 9370 and I have it connected to two monitors through a Dell Thunderbolt Dock. Only one monitor is active. When I try to activate the other one 1. What I expected to happen I am able to select the second external monitor (or the built-in display for that matter) and change its settings. 2. What happened instead gnome-control-center disappears I have attached lshw output and the gdb backtrace and would be grateful for any help with this. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gdb backtrace" https://bugs.launchpad.net/bugs/1853838/+attachment/5307688/+files/gnome-control-center_backtrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853838 Title: gnome-control-center crashes with SIGSEGV when selecting display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1853838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853838] Re: gnome-control-center crashes with SIGSEGV when selecting display
** Attachment added: "lshw.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1853838/+attachment/5307689/+files/lshw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853838 Title: gnome-control-center crashes with SIGSEGV when selecting display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1853838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842986] [NEW] [snap] libreoffice cannot open files in /tmp (e.g. opened by browser)
Public bug reported: With the libreoffice snap, I get an error trying to open a .docx file from Firefox, saying that the file cannot be found. This appears to be because Firefox puts the file under /tmp, but libreoffice has a different /tmp in its process. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842986 Title: [snap] libreoffice cannot open files in /tmp (e.g. opened by browser) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1842986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663645] Re: Installation hangs at 66% "Installing GRUB boot loader"
Follow-up: I was able to get around the problem using the reaction workaround described in this debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=853187#25 Had to kill two dmcreate processes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663645 Title: Installation hangs at 66% "Installing GRUB boot loader" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1663645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663645] Re: Installation hangs at 66% "Installing GRUB boot loader"
I have the same problem on a Fujitsu TX150 S7 with Xeon X3450. Installing with mdadm on two SSDs. Going to leave it overnight as well and will see what happens. The last debug messages are os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sdb1 [this is the second member of the mdadm RAID1 array] 50mounted-tests: debug: creating device mapper device /dev/mapper/osprober-linux-sdb [cuts off] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663645 Title: Installation hangs at 66% "Installing GRUB boot loader" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1663645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310351]
Thanks, Rex. I happen to be a GNOME user myself, but more importantly, I need an xdg-screensaver that works for users there. If you have any suggestions that you'd be happier with, I'm all ears. Note that we're talking about GNOME 3/gnome-shell, so gnome-screensaver can't be assumed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310351]
The SimulateActivity interface is not actually specified in the fd.o spec: http://people.freedesktop.org/~hadess/idle-inhibition- spec/re01.html The only methods offered there are Inhibit and UnInhibit. SimulateActivity is not implemented in GNOME 3, so the patch will not work there. The route I suggest will work on any system implementing the fd.o spec. In general, I think that while one does have to be careful about dependencies in general. First, it is not unreasonable to assume that any system running one of the desktop environments that implement this DBus interface will have Perl installed. Of course, the Perl DBus implementation is not part of core Perl; I would be happy to make my patch emit a helpful error if it can't find the module. Secondly, for most users, xdg-utils will be installed from a system package, which can depend on the relevant Perl package (which is not large); as well, of course, as depending on Perl (since Perl is installed by default on many systems, e.g. Ubuntu and Mac OS X, the latter dependency will often not be needed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310351]
Created attachment 111737 Patch to fix this bug This patch fixes the bug. It necessitates a helper Perl script. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070823] Re: chromium-browser deletes modified autostart files
As far as I can tell, this is no longer a problem. In particular, I have a ~/.config/autostart/chromium-browser.desktop file with a timestamp from 2017, and it is set to run Chromium normally (without --no-startup- window). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070823 Title: chromium-browser deletes modified autostart files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1070823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660605] Re: multiple caffeinated processes: suspends after first completes
I'm the maintainer of caffeinate. This shouldn't happen: caffeinate creates a separate window whose ID is passed to xdg-screensaver on each invocation. I had a look at caffeinate, and I can't see any faults in its logic (of course, I welcome reports to the contrary!). In particular, I tested to make sure that it uses a different window ID when it is run in parallel in several instances. As ever for bugs with caffeine and its friends, the way to find out where the bug is is to run the relevant xdg-screensaver commands manually: $ xdg-screensaver suspend WINDOW_ID_1 $ xdg-screensaver suspend WINDOW_ID_2 $ xdg-screensaver resume WINDOW_ID_1 where WINDOW_ID_1 and WINDOW_ID_2 are the IDs of two different windows, obtained for example by running the following command twice: $ xwininfo | grep "Window id" | cut -d " " -f 4 and in each case clicking on a different window. Whichever window it is, it must remain open for the duration of the experiment. After running the 3 commands above, if the screensaver is now active again, that's a bug in xdg-screensaver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660605 Title: multiple caffeinated processes: suspends after first completes To manage notifications about this bug go to: https://bugs.launchpad.net/caffeine/+bug/1660605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Desktop is not restored correctly after screen saver
Thanks for the explanation, and I agree that the bug is "Invalid" for Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Desktop is not restored correctly after screen saver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Desktop is not restored correctly after screen saver
For anyone else having the same problem as me, a patched version of the Hamster time tracker extension is available; see https://github.com/projecthamster/hamster-shell-extension/issues/295 ** Bug watch added: github.com/projecthamster/hamster-shell-extension/issues #295 https://github.com/projecthamster/hamster-shell-extension/issues/295 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Desktop is not restored correctly after screen saver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Desktop is not restored correctly after screen saver
I had several of these extensions. I started by disabling them all. This fixed the problem (thanks!). I then re-enabled most of them one at a time (because they are all things I find extremely useful—I do not like to install extensions unless I have to!). In the end, I was able to reinstall all but one of the extensions I need, namely 'cont...@projecthamster.org' I had no problem with: 'nohotcor...@azuri.free.fr' 'switc...@landau.fi' 'topIcons@adel.gadl...@gmail.com' 'windowIsReady_Remover@nunofarr...@gmail.com' 'windowoverlay-ic...@sustmidown.centrum.cz' 'window-search-provi...@quelltexter.org' I am interested in how you made the list, @vanvugt; is there some reason to suspect the other extensions listed are problematic too? In any case, my immediate problem seems to be solved (thanks very much), and I now need to find a fix for using Project Hamster, as I rely on it to time work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Desktop is not restored correctly after screen saver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Desktop is not restored correctly after screen saver
@vanvugt: I had a look at the other bug and its proposed fix. I do not have the package gnome-shell-extension-ubuntu-dock installed, and the recent update's changelog suggests that the update fixes a bug in that package, so I'm not sure how it could be the cause of this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Desktop is not restored correctly after screen saver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Desktop is not restored correctly after screen saver
Thanks for the pointer; I've subscribed to that bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Desktop is not restored correctly after screen saver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Desktop is not restored correctly after screen saver
It's always been grey on Ubuntu GNOME as far as I'm aware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Desktop is not restored correctly after screen saver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Desktop is not restored correctly after screen saver
I notice that if I use the mouse to deactivate the screen saver, I do still see the screen shield, so that appears to be working normally. When the shield lifts, I get the "login screen without login widget" described above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Desktop is not restored correctly after screen saver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Desktop is not restored correctly after screen saver
I tried disabling the lock screen with $ gsettings set org.gnome.desktop.lockdown disable-lock-screen true and that makes no difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Desktop is not restored correctly after screen saver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Desktop is not restored correctly after screen saver
I have updated the bug to reflect that it's related to the screen saver (desktop idleness), not specifically the lock screen. ** Summary changed: - Lock screen stopped working + Desktop is not restored correctly after screen saver ** Description changed: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, - the lock screen stopped working properly. + the screen saver stopped working properly. - When I enter lock, either manually (by clicking the lock screen icon) or - automatically (by waiting for the lock screen timeout), the screen - either freezes with the desktop still showing, or shoes the same grey - background as the login screen; it does not show the normal lock screen - image. + When the screen is locked manually (by clicking the lock screen icon), + the screen either freezes with the desktop still showing, or shows the + same grey background as the login screen; it does not show the normal + lock screen image. - Pressing a key such as space, which would normally raise the screen - shield and reveal the login dialog, has no effect. + When the screen saver is activated automatically, the screen turns off + as normal, but when I press a key, the grey background as for the login + screen is shown (in fact, it's the same as the login screen, but without + the login widget; that is, the normal icons are shown at the top of the + screen). + Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Desktop is not restored correctly after screen saver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Lock screen stopped working
In case it was a kernel problem (I have also had a kernel update since I last rebooted, from 4.15.0-42 to -43), I installed the latest HWE 18.04 kernel, but that did not help. I should note that in fact the screen shield *does* sometimes activate; but when it does, pressing a key reveals only the grey background, not the login dialog. Another potential culprit might be gdm3, but of course there has been no update to that package recently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Lock screen stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Lock screen stopped working
I tried building 3.28.3-0ubuntu0.18.04.3 and installing that, but that doesn't fix the problem, so it looks as though the cause may lie elsewhere, in some other update that has happened in the same period. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Lock screen stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812373] Re: Lock screen stopped working
(The issue doesn't seem to me to be serious enough to warrant keeping the bug private.) ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812373 Title: Lock screen stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 827028] Re: Uses 100% CPU after starting
Unfortunately I no longer use rygel, so I can't say whether things have improved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827028 Title: Uses 100% CPU after starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rygel/+bug/827028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1462186] Re: Add MATE support
@pilotbob42, thanks for the extra material. From looking at the patch and MATE thread it seems the main difference is that MATE uses a different DBus path for its screen saver; unfortunately, this is already taken account of in the current xdg-screensaver, so the actual problem must be some other detail that is different. However, it does mean that it should be easy to fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462186 Title: Add MATE support To manage notifications about this bug go to: https://bugs.launchpad.net/caffeine/+bug/1462186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1462186] Re: Add MATE support
@pilotbob42, thanks for the explanation, that makes more sense. However, xdg-utils has explicit support for MATE, so if it's broken, it's a bug and should be fixed. (xdg-screensaver has ad hoc support for a wide range of desktop environments; there is no requirement to support a particular mechanism). Comments in xdg-screensaver say: # DBUS interface for mate-screensaver # This is same as gnome's for now but may change in the future as MATE # does not follow gnome's developement necessarily. If this therefore is no longer the case, then the code needs updating; simple as that! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462186 Title: Add MATE support To manage notifications about this bug go to: https://bugs.launchpad.net/caffeine/+bug/1462186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1462186] Re: Add MATE support
@pilotbob42, if xdg-screensaver works, then the bug is in Caffeine, and you can report a bug against Caffeine. mate-screensaver is not involved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462186 Title: Add MATE support To manage notifications about this bug go to: https://bugs.launchpad.net/caffeine/+bug/1462186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1462186] Re: Add MATE support
@pilotbob42 if you could test Ubuntu 18.04.1's xdg-screensaver under MATE, and report a bug against xdg-utils if it doesn't work, that would be great. I'm sorry that Caffeine 2.9.4 doesn't work for you, but it's no longer under Caffeine's control (conversely, fixing xdg-screensaver for MATE fixes it for everyone, not just Caffeine users!). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462186 Title: Add MATE support To manage notifications about this bug go to: https://bugs.launchpad.net/caffeine/+bug/1462186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087075] Re: Duplex options ignored for printing Postscript
I can confirm that this bug still exists in Ubuntu 16.04.5: specifically, I tried printing two pages of a PostScript file from Evince with Duplex set to "Long Edge (Standard)", and instead of a single sheet with both pages, the printer printed on two sheets. I also had the following error on the terminal from which I launched Evince: "fatal internal error -100" eight times, without a newline between the repetitions. It would be good to find a solution to this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087075 Title: Duplex options ignored for printing Postscript To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1087075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 489655] Re: ebook-convert command-line arguments ignored
Sure, please close it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/489655 Title: ebook-convert command-line arguments ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/489655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159884] Re: References to ~/.xsession-errors in /etc/gdm/
I tried changing the remote bug watch, but Launchpad won't accept the GitLab URL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159884 Title: References to ~/.xsession-errors in /etc/gdm/ To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1159884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159884] Re: References to ~/.xsession-errors in /etc/gdm/
The upstream bug has been migrated to the new GNOME bug-tracker at GitLab: https://gitlab.gnome.org/GNOME/gdm/issues/157 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159884 Title: References to ~/.xsession-errors in /etc/gdm/ To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1159884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159884] Re: References to ~/.xsession-errors in /etc/gdm/
This bug appears to be still present in package gdm3 (see /etc/gdm3/PreSession/Default). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159884 Title: References to ~/.xsession-errors in /etc/gdm/ To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1159884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1202001] Re: aptitude show doesn't work without architecture suffix even if the package is available only in one (foreign) architecture
*** This bug is a duplicate of bug 892074 *** https://bugs.launchpad.net/bugs/892074 This works now, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1202001 Title: aptitude show doesn't work without architecture suffix even if the package is available only in one (foreign) architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1202001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68924] Re: provide support for changing volume labels
I can find no evidence that this bug has ever been fixed, even in Ubuntu. Can anyone point me to evidence that it has been? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/68924 Title: provide support for changing volume labels To manage notifications about this bug go to: https://bugs.launchpad.net/hal/+bug/68924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
