[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Same issue upgrading from 22.04 to 24.04, confirmed the fix of `sudo apt install systemd-resolved` fixes the issue. Had a crash partway through the upgrade where I was left with the UI showing "something went wrong", which was partially fixed by dropping into a terminal and commadning `sudo dpkg --configure -a`, but it was left in this state afterwards. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2021446] [NEW] rhythmbox plugin grilo no longer discovers UPNP media share
Public bug reported: In Ubuntu <=22.10 the grilo rhythmbox plugin automatically discovered a UPnP media share from my Synology Network Attached Storage device on my local network. When I upgraded to Ubuntu 23.04, rhythmbox no longer detects the media share. I've confirmed that the share is detected on a computer with 22.10 but not on two computers with 23.04 (all on the same LAN). I've also confirmed that VLC media player detects the share on the Ubuntu 23.04 computers. I first posted a report here, thinking it was due to an update on the NAS: https://community.synology.com/enu/forum/1/post/160502 I then opened this issue on Rhythmbox's bug tracker: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/2047 I expected Rhythmbox+Grilo to automatically discover a UPnP share on my local area network when on Ubuntu 22.10, but it does not discover the share. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2021446 Title: rhythmbox plugin grilo no longer discovers UPNP media share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2021446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015056] Re: No wallpaper / no option to open the dialog for changing the wallpaper
Installing ```apt-get install gnome-control-center``` resolved the issue. Seems this is removed during the upgrade. -- 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/2015056 Title: No wallpaper / no option to open the dialog for changing the wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2015056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015056] [NEW] No wallpaper / no option to open the dialog for changing the wallpaper
Public bug reported: # System information: System has upgraded from 22.10 -> 23.04 # How to reproduce 1. start up the computer. No wallpaper visible just black background. 2. right click on desktop "Change background" # Expected result Wallpaper visible / ability to change wallpaper. # output on logfile ``` 2023-04-03T10:16:46.216657+02:00 utopia-Ubuntu gnome-shell[3652]: DING: (gjs:4392): Gjs-CRITICAL **: 10:16:46.213: JS ERROR: TypeError: desktopFile is null 2023-04-03T10:16:46.216882+02:00 utopia-Ubuntu gnome-shell[3652]: DING: _createDesktopBackgroundMenu/<@/usr/share/gnome-shell/extensions/d...@rastersoft.com/desktopManager.js:1114:13 2023-04-03T10:16:46.216971+02:00 utopia-Ubuntu gnome-shell[3652]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js:206:13 ``` ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gjs 1.76.0-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 10:22:09 2023 InstallationDate: Installed on 2022-11-19 (134 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gjs UpgradeStatus: Upgraded to lunar on 2023-03-31 (3 days ago) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- 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/2015056 Title: No wallpaper / no option to open the dialog for changing the wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2015056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983117] Re: "Focus Follow Mouse" auto-raises windows when it shouldn't
The thread-jack by Bloodyiron on 1969602 #6 is describing the same issue as here, but this is not about Alt-Tab misbehavior, that seems to be something else. None of the other focus issue seem similar. -- 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/1983117 Title: "Focus Follow Mouse" auto-raises windows when it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983117] [NEW] "Focus Follow Mouse" auto-raises windows when it shouldn't
Public bug reported: Steps to reproduce on Jammy LTS: 1. Create a new empty user and login under Wayland 2. Using gnome-tweaks select "Windows" -> "Window Focus" -> "Focus on Hover" 3. Notice that "Raise Windows When Focused" is disabled Windows auto-raise when changing workspaces: 1. Open two terminal windows and partially overlap them 2. Place the mouse over the lower terminal window so that it remains lowered 3. Do not move the mouse: Press Super-End to change to another workspace, then Super-Begin to go back 4. Observe that the terminal window the mouse is over has been raised The expected behaviour is that windows are not auto-raised when changing workspaces Windows auto-raise when closing windows: 1. Open three terminal windows such that parts of all windows are visible but all windows overlap. 2. Place the mouse inside the topmost terminal so that it is within the visible lowest terminal 3. Without moving the mouse Ctrl-D the terminal to close it 4. Observe that the lowest terminal window the mouse is over has been raised to the top. The expected behaviour is that windows are not auto-raised when closing windows Logout/Login using X and repeat these actions. Notice that window ordering remains fixed in order. This has been the expected behaviour of gnome for the last 10 years or so. This is a behaviour regression for Ubuntu users upgrading from the last LTS (using X). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 12:11:27 2022 InstallationDate: Installed on 2022-06-25 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1983117 Title: "Focus Follow Mouse" auto-raises windows when it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983115] [NEW] Keybinding "Lower window below other windows" lowers windows below the desktop icons
Public bug reported: Steps to reproduce on Jammy LTS: 1. Create an new empty user 2. Login using Wayland 3. Open "Settings" -> "Keyboard" -> "View and Customize Shortcuts" -> "Windows" -> "Lower window below other windows" 4. Click on the setting "Lower window below other windows" and assign a keybinding, eg Alt-Down 5. Close settings 3. Find the "Home" icon on the desktop 5. Open a terminal and place it over the home icon 6. Press the keybinding "Lower window below other windows" and observe that the terminal window is lowered below the Home icon. eg the Home icon becomes visible on top of the terminal window 7. Try click on the Hamburger Menu in terminal and observe the menu does not open but the window raises above the Home icon. Logout, login under X mode and repeat. Notice that the window does not lower below the home icon and that the Hamburger Menu works on the first click. This is the expected behaviour of this feature going back at least 10 years. For Ubuntu users coming from the previous LTS (using X) this is a behaviour regression. I'm guessing this is mutter because it is wayland specific and mutter src has the "lower" keybinding which is described as the same "Lower window below other windows" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 11:58:21 2022 InstallationDate: Installed on 2022-06-25 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1983115 Title: Keybinding "Lower window below other windows" lowers windows below the desktop icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1978366] [NEW] unlocking screen hangs for 20-40sec before working
Public bug reported: Ever since installing (not upgrading) Ubuntu-22.04, I've noticed that quite often (but not always) unlocking the screensaver freezes the entire system. By that I mean I will tap my keyboard, the blank screen will lighten up and show the password field, I start typing, get the "***" characters, and then it freezes: typing doesn't continue, mouse stops moving. If I wait, 30-40 (ish) seconds later it will catch up and start responding again and I can continue. Quite often the freeze doesn't occur until I have entered my password and hit ENTER - but it does freeze earlier too. I have figured out that if this happens, I can speed up the process by hitting Ctrl-Alt-F3 to go to a tty, then immediately Alt-F2 to go back to gnome - and that flushes out the problem. Definitely shaves many seconds off waiting around for the fault to clear by itself. I was also talking to a collegue who installed Ubuntu-22.04 this week - he's noticed the same issue. Also a Dell laptop - but different model. I would guess Wayland related - but don't have any evidence for that, so I put this as gnome-shell Thanks! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:02:34 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-13 (89 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1978366 Title: unlocking screen hangs for 20-40sec before working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966602] [NEW] Screen not locked after inactivity
Public bug reported: I did a fresh install of Ubuntu-22.04 two weeks ago. I don't think the automatic lock on idle feature has worked the entire time (and I've been patching all the time when available). If I manually lock the screen it works - but if I don't, I can go to bed and the next day it's still unlocked. syslog doesn't show any obvious gnome-screensaver error, so I wonder if this is actually a Wayland issue - ie it isn't telling gnome- screensaver about inactivity triggers? I dunno - just guessing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver 3.6.1-13ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 07:06:47 2022 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 900 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2022-03-13 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-screensaver Symptom: security Title: Screen not locked after inactivity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (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 gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1966602 Title: Screen not locked after inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1966602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1943491] [NEW] GIMP Batch Process crashes after doing a batch format change
Public bug reported:
```
GNU Image Manipulation Program version 2.10.24
git-describe: GIMP_2_10_24
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
9.3.0-17ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
# Libraries #
using babl version 0.1.86 (compiled against version 0.1.86)
using GEGL version 0.4.30 (compiled against version 0.4.30)
using GLib version 2.64.6 (compiled against version 2.64.6)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.44.7 (compiled against version 1.44.7)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> GIMP-CRITICAL: _gimp_wire_read_int8: assertion 'count >= 0' failed
Stack trace:
```
# Stack traces obtained from PID 36692 - Thread 36692 #
[New LWP 36693]
[New LWP 36694]
[New LWP 36695]
[New LWP 36696]
[New LWP 36697]
[New LWP 36698]
[New LWP 36699]
[New LWP 36700]
[New LWP 36701]
[New LWP 36702]
[New LWP 36721]
[New LWP 36774]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffcf5b33ea0, fd=19) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7f0320673340 (LWP 36692) "gimp-2.10" __libc_read (nbytes=256,
buf=0x7ffcf5b33ea0, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f031ff27700 (LWP 36693) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f031f726700 (LWP 36694) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7f031ef25700 (LWP 36695) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7f031e724700 (LWP 36696) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7f031df23700 (LWP 36697) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
7Thread 0x7f031d722700 (LWP 36698) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7f031cf21700 (LWP 36699) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7f02ff49c700 (LWP 36700) "gmain" 0x7f03214afaff in
__GI___poll (fds=0x55bd93ad1d90, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
10 Thread 0x7f02fec9b700 (LWP 36701) "gdbus" 0x7f03214afaff in
__GI___poll (fds=0x55bd93ae3ef0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
11 Thread 0x7f02f0861700 (LWP 36702) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
12 Thread 0x7f02e7066700 (LWP 36721) "dashboard" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
13 Thread 0x7f02e7fff700 (LWP 36774) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 13 (Thread 0x7f02e7fff700 (LWP 36774)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f03217a5623 in g_cond_wait () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f0321caa3ad in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7f0321781ad1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f0321595609 in start_thread (arg=) at
pthread_create.c:477
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139650458973952,
[Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown
Also see this on 20.10 on a Dell XPS 15 9550. -- 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/1280300 Title: Desktop contents displayed on resume, before lock screen is shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925742] Re: IMAP broken in Evolution
Bug is also present in Groovy and Hirsute. -- 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/1925742 Title: IMAP broken in Evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870830] Re: gnome-shell-extension-prefs not installed with base GNOME Shell installation
Actually, I don't think this is a wishlist item - this is a bug. If I right click the 9-dot grid "Show Applications" button at the bottom left, the click "Dash to Dock settings" on a brand new 20.04 installation, I get "Execution of gnome-shell-extension-prefs failed." ** Attachment added: "Screenshot from 2020-04-07 10-30-48.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870830/+attachment/5348752/+files/Screenshot%20from%202020-04-07%2010-30-48.png -- 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/1870830 Title: gnome-shell-extension-prefs not installed with base GNOME Shell installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870830] Re: gnome-shell-extension-prefs not installed with base GNOME Shell installation
If this is intentional, then the package should also be added as a dependency to gnome-shell-extension-dash-to-panel and other gnome-shell- extension-* packages which require settings access. -- 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/1870830 Title: gnome-shell-extension-prefs not installed with base GNOME Shell installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870830] [NEW] gnome-shell-extension-prefs not installed with base GNOME Shell installation
Public bug reported: This package is required for access to the settings dialog for any Gnome Shell extension, which will throw an error without it. It is no longer installed in 20.04 by default and has to be manually installed by the user, but I believe it should be installed by default. Here are some relevant discussions: https://www.reddit.com/r/Ubuntu/comments/fql7zz/ubuntu_2004_gnome_extensions/ https://bugs.launchpad.net/ubuntu/focal/+source/gnome-shell-extension- dash-to-panel/+bug/1866070/comments/3 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1870830 Title: gnome-shell-extension-prefs not installed with base GNOME Shell installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866146] Re: GNOME Shell 3.35.91 extension's preferences doesn't load
I don't think the user should need to take additional action to install this package - it should already be there, as in other distros including 3.36. This package has been present by default in previous versions of Ubuntu as well. -- 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/1866146 Title: GNOME Shell 3.35.91 extension's preferences doesn't load To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867678] [NEW] package xrdp 0.9.12-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1
Public bug reported: Upgrade from 18.04 to 20.04 failed on Hyper-V VM ProblemType: Package DistroRelease: Ubuntu 20.04 Package: xrdp 0.9.12-1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Mon Mar 16 15:10:59 2020 DuplicateSignature: package:xrdp:0.9.12-1 Installing new version of config file /etc/xrdp/xrdp_keyboard.ini ... ln: failed to create symbolic link '/etc/xrdp/cert.pem': File exists dpkg: error processing package xrdp (--configure): installed xrdp package post-installation script subprocess returned error exit status 1 ErrorMessage: installed xrdp package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.10 SourcePackage: xrdp Title: package xrdp 0.9.12-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-03-16 (0 days ago) mtime.conffile..etc.xrdp.sesman.ini: 2019-04-07T00:20:37.926477 mtime.conffile..etc.xrdp.xrdp.ini: 2019-04-07T00:20:37.918476 ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xrdp in Ubuntu. https://bugs.launchpad.net/bugs/1867678 Title: package xrdp 0.9.12-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1867678/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
Applying the patch fixed my problem with my Sony WH-H900N headphones. Probably a different bug but if I open Sound Settings -> Input and change the input from "Internal Microphone Built-in Audio" to "Headset WH-H900N (h.ear)" the quality degrades and the Output profile changes to "Headset Head Unit (HSP/HFP)". If I change the Output profile back to "High Fidelity Playback (A2DP Sink)" I get high quality audio again but the Input changes back to "Internal Microphone Built-in Audio". Or is it that you can't use the headset microphone and get high quality audio at the same time? -- 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/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Just ran into this issue on a fresh install of 19.10 with all updates installed as of 2019/11/30. The lock icon in the menu is missing and the keyboard shortcut is non-functional. The Screen Lock dialog in settings is greyed out entirely. chris-18's fix from earlier worked. Setting org/gnome/desktop/lockdown/disable-lock-screen to disabled: enabled the icon, the keyboard shortcut, and the Screen Lock dialog in settings. -- 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/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] Re: Snap installs software without user having sudo access
Unfortunately it isn't that easy in my case. I need to have every action attempted logged. That will still give it to me, but modifying what's happening by changing what's being requested. So, if a normal user attempts something, the best case is for it to ask for the users password and fail when they don't have permission to do the action, or the password entered is wrong. Second best, is to fall back to asking for the root password. I can deal with the logging inaccuracy. But not always ask for the root password in every case which is what that override will do. I'm going to be needing to implement some custom polkit/apparmour stuff eventually anyway (now that I've seen this), but this came about as I am not a Debian/Ubuntu person. So I hit something that _shouldn't_ have been happening in my mind (hey, no sudoers access, no way to run as root) ... It threw me that it was happening. But thanks to everyone for digging into this with me. -- 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/1850977 Title: Snap installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] Re: Snap installs software without user having sudo access
As an addition... If I remove the 51-ubuntu-admin.conf file, when I run `snap install blender --classic`, it pops up a dialog box asking for the "Administrator" password. Entering roots password will install it. This is the behaviour wanted. Not install it with only the users authentication. -- 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/1850977 Title: Snap installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] Re: Snap installs software without user having sudo access
That's what I want though. I want control through sudoers, not polkit. The file: /etc/polkit-1/localauthority.conf.d/50-localauthority.conf ... still contains: ``` [Configuration] AdminIdentities=unix-user:0 ``` I don't know why you need to say root is an admin, but whatever it's there... And that *should* be the only admin. No other user should have administrative privileges on their own, without using sudo or becoming root. Full stop. This isn't for a single desktop home system, but a corporate controlled system. A user that can install software just because they want to isn't going to fly (or pass Government regulations we need to). And not all admins are created equal. -- 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/1850977 Title: Snap installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] Re: Snap installs software without user having sudo access
Thank You!!! Can you set it like: ``` [Configuration] AdminIdentities= ``` So *nothing* is considered an Admin? That file has `unix-group:sudo;unix-group:admin` ... by default from what I can tell. But at least that I know this thing exists and hey, you can elevate privileges without being in sudoers (Ugh... another thing to restrict for regulations). Does that deal only with the *name* of the group, or what it sees as the GID? I mean, I can make another user named `bob` with a UID of 0 ... so I'm still effectively root even if I'm logged in as bob. Does this work that way with GID's? Or is it looking explicitly at the name only even if the name is irrelevant is actual system usage? Meaning, I can have groups named: Admin, AdminA, AdminB, AdminC with different members but the same GID. In this way anything on the filesystem owned by the `Admin` group, can be accessed by any of the Admin groups since it's the GID that matters. Does PolicyKit take GIDs into account, or just the name? -- 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/1850977 Title: Snap installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] Re: Snap installs software without user having sudo access
The above still stands... but that isn't it for `snap` ... I changed all
the `isIngroup("sudo")` to use `sudoA` since that's the actually group
that's in sudoers...
And snap is still letting me install the blender snap in `--classic`
mode. So How do you find out what polkit rules are running at any
given time?
The `io.snapcraft.snapd.manage' action has:
```
auth_admin
```
But where is what `auth_admin` does defined? It *looks* like it's seeing
it as a local login and just allowing it. If I log in through SSH and
try the same command I get:
$ snap install blender --classic
error: access denied (try with sudo)
Being a locally logged in user does not mean you should have the ability to
install software. Again, that's an incorrect assumption being made :/
--
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/1850977
Title:
Snap installs software without user having sudo access
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] Re: Snap installs software without user having sudo access
Seems to be more appropriate to assign this to snapd than gnome- software. ** Summary changed: - gnome-software installs software without user having sudo access + Snap installs software without user having sudo access ** Tags added: snap ** Package changed: gnome-software (Ubuntu) => snapd (Ubuntu) -- 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/1850977 Title: Snap installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1850977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] Re: gnome-software installs software without user having sudo access
Attached is a screenshot of the VM window where the terminal install was done. ** Attachment added: "Installation using snap on account without sudo access" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+attachment/5303117/+files/Screenshot_2019-11-05_15-28-49.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/1850977 Title: gnome-software installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] Re: gnome-software installs software without user having sudo access
Here's the lines from journalctl -b 0 The "sudo" was from me doing: sudo su - ... just prior to the "snap install blender --classic" --- start cut --- Nov 05 15:15:39 jms-u18t sudo[18049]: pam_unix(sudo:auth): authentication failure; logname= uid=1031 euid=0 tty=/dev/pts/0 ruser=jason rhost= user=jason Nov 05 15:15:39 jms-u18t sudo[18049]:jason : user NOT in sudoers ; TTY=pts/0 ; PWD=/home/users/jason ; USER=root ; COMMAND=/bin/su - Nov 05 15:15:43 jms-u18t gnome-shell[16877]: polkitAuthenticationAgent: Received 3 identities that can be used for authentication. Only considering one. Nov 05 15:15:46 jms-u18t polkit-agent-helper-1[18065]: pam_unix(polkit-1:auth): authentication failure; logname= uid=1031 euid=0 tty= ruser=jason rhost= user=jason Nov 05 15:15:46 jms-u18t polkitd(authority=local)[881]: Operator of unix-session:116 successfully authenticated as unix-user:jason to gain TEMPORARY authorization for action io.snapcraft.snapd.manage for unix-process:18050:34595600 [snap install blender] (owned by unix-user:jason) Nov 05 15:15:46 jms-u18t snapd[860]: api.go:952: Installing snap "blender" revision unset Nov 05 15:16:02 jms-u18t gnome-shell[16877]: polkitAuthenticationAgent: Received 3 identities that can be used for authentication. Only considering one. Nov 05 15:16:05 jms-u18t polkit-agent-helper-1[18083]: pam_unix(polkit-1:auth): authentication failure; logname= uid=1031 euid=0 tty= ruser=jason rhost= user=jason Nov 05 15:16:05 jms-u18t polkitd(authority=local)[881]: Operator of unix-session:116 successfully authenticated as unix-user:jason to gain TEMPORARY authorization for action io.snapcraft.snapd.manage for unix-process:18068:34597431 [snap install blender --classic] (owned by unix-user:jason) Nov 05 15:16:05 jms-u18t snapd[860]: api.go:952: Installing snap "blender" revision unset Nov 05 15:16:11 jms-u18t systemd[1]: Reloading. Nov 05 15:16:11 jms-u18t systemd[1]: Mounting Mount unit for blender, revision 33... Nov 05 15:16:11 jms-u18t systemd[1]: Mounted Mount unit for blender, revision 33. Nov 05 15:16:14 jms-u18t audit[18150]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.blender" pid=18150 comm="apparmor_parser" Nov 05 15:16:14 jms-u18t audit[18151]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.blender.blender" pid=18151 comm="apparmor_parser" Nov 05 15:16:14 jms-u18t kernel: audit: type=1400 audit(1572988574.599:142): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.blender" pid=18150 comm="apparmor_parser" Nov 05 15:16:14 jms-u18t kernel: audit: type=1400 audit(1572988574.599:143): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.blender.blender" pid=18151 comm="apparmor_parser" Nov 05 15:16:15 jms-u18t gnome-shell[16877]: Some code accessed the property 'refreshPropertyOnProxy' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a Nov 05 15:16:15 jms-u18t pkexec[18154]: pam_unix(polkit-1:session): session opened for user root by (uid=1031) Nov 05 15:16:15 jms-u18t pkexec[18154]: jason: Executing command [USER=root] [TTY=unknown] [CWD=/home/users/jason] [COMMAND=/usr/lib/update-notifier/package-system-locked] --- end cut --- So, we have here from polkitd: "successfully authenticated as unix- user:jason to gain TEMPORARY authorization for action io.snapcraft.snapd.manage" So... installing thorough snap, as long as you know the users password... lets you install something on the system? Without needing root privileges? Is this some apparmor policy thing? -- 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/1850977 Title: gnome-software installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] Re: gnome-software installs software without user having sudo access
A dialog box appears. It just shows the Full Name field, and the name shown is "Jason Stover" (login: jason) for the LDAP account. The Local Admin account name is "Jason Local" (login: jlocal). The passwords between the two accounts is also different incase it was showing the name of the logged in user, but asking for the password of the local account, the passwords wouldn't have matched up. -- 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/1850977 Title: gnome-software installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] [NEW] gnome-software installs software without user having sudo access
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it pops
up and asks for my users password. I enter this in, and the software
then installs (tested with blender, libreoffice, opencl driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-software (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
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/1850977
Title:
gnome-software installs software without user having sudo access
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846955] Re: Gnome crashes on adding system title bars to Chrome under Wayland in EOAN
Thank you very much for the direction. This will be helpful when I report any future bugs. I hadn't had time to look at this till today. I decided to try and reproduce the bug to generate a new crash file, but have been unable to reproduce it. One of the updates from the past few days must have solved it. Thank you. -- 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/1846955 Title: Gnome crashes on adding system title bars to Chrome under Wayland in EOAN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846955] [NEW] Gnome crashes on adding system title bars to Chrome under Wayland in EOAN
Public bug reported: To reproduce: 1. Open Chrome under Wayland session in 19.10 beta 2. Maximize Chrome 3. Right click on empty space beside tabs and from the menu select "Use system titlebar and borders" Chrome immediately crashes and gnome begins to become less and less responsive until it finally freezes. Does not occur when doing the equivalent in Firefox BTW - Gnome is super responsive in Eoan! Keep up the good work. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl output for the specified event" https://bugs.launchpad.net/bugs/1846955/+attachment/5294771/+files/journal.txt ** Summary changed: - Gnome crashes on adding system title bars under Wayland in EOAN + Gnome crashes on adding system title bars to Chrome under Wayland in EOAN -- 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/1846955 Title: Gnome crashes on adding system title bars to Chrome under Wayland in EOAN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I too am experiencing this issue when using: Ubuntu 18.04.2 LTS Gnome 3.28.2 Mouse moves but unable to click anything for a minute or two. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834084] [NEW] Selecting Text and CLICKING Permanently Removes Text
Public bug reported: It seems a prior bug has resurfaced, with a slightly different behavior now. (This is *not* a duplicate of gtk#1447) **Version:** 3.32.1-2 **OS:** Ubuntu MATE 19.04 In the email composer window, if you select text in the body, and *click* anywhere else in the composition pane, the text you selected is sometimes permanently deleted (cannot be accessed from undo). When this happens, the undo history itself is mangled, so pressing Ctrl+Z will try to "undo" as if the text were still there, meaning intentionally deleted text will be inserted in strange places, etc. This can be a bit unpredictable. For example, if you change the style of text (Normal/Preformatted/Header) first, it seems to prevent it. There seem to be other actions that can sometimes prevent it, or sometimes it just won't happen at all, even following the steps below exactly. (It happens about half the time for me...usually more often when the email is important, ha ha.) 1. Open a new Compose window. 2. Type some text in the body. 3. Using the mouse, select some text. 4. Click elsewhere in the composition pane. Be advised, **modifier keys, arrow keys, or clicking outside the composer window do NOT cause the text to be deleted.** Be advised, this was previously reported at https://gitlab.gnome.org/GNOME/evolution/issues/500 and dismissed as "blame the environment". ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1834084 Title: Selecting Text and CLICKING Permanently Removes Text To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1834084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827751] Re: Shield screen is displayed after blanking even when lock screen disabled
Thank you for the update and the explanation. I will post some feedback on gitlab. -- 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/1827751 Title: Shield screen is displayed after blanking even when lock screen disabled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827751] Re: Lock screen displayed after screen blanking even when lock screen disabled
Correction: I have to push the Enter key to dismiss the screen, not any other key. -- 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/1827751 Title: Lock screen displayed after screen blanking even when lock screen disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827751] Re: Lock screen displayed after screen blanking even when lock screen disabled
Sorry, but I am not sure I could tell the difference so I will try and describe it as best I can. There is no place to enter a password, but I also have my system set to automatically log in, so I'm not sure if it would ask me for a password if it was displayed. I do have to press a key to get past the screen. I have attached a picture of the screen. I was not able to do a screen capture as it would not let me with the screen displayed, so I used my phone's camera. I will also attached a screen capture showing my settings for choice of background and lock screen in the next comment as I can only attach one file per comment. Hopefully this will clarify things. ** Attachment added: "Lock Screen.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+attachment/5264673/+files/Lock%20Screen.jpg -- 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/1827751 Title: Lock screen displayed after screen blanking even when lock screen disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827751] Re: Lock screen displayed after screen blanking even when lock screen disabled
Here is the screen capture with the background settings. ** Attachment added: "Screen Capture.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+attachment/5264674/+files/Screen%20Capture.png -- 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/1827751 Title: Lock screen displayed after screen blanking even when lock screen disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827751] Re: Lock screen displayed after screen blanking even when lock screen disabled
My mistake, it is still present. I just wasn't waiting long enough after the screen blank before waking the screen up. Waited a bit and it is back, even with the extension running. -- 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/1827751 Title: Lock screen displayed after screen blanking even when lock screen disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827751] Re: Lock screen displayed after screen blanking even when lock screen disabled
Also tried editing /etc/default/acpi-support and commenting out the line LOCK_SCREEN=true. That did not work. Just found a workaround that seems to take care of the problem. Install the Gnome Extension: Disable Screen Shield and activate it. The lock screen no longer appears after screen blanking. -- 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/1827751 Title: Lock screen displayed after screen blanking even when lock screen disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827751] [NEW] Lock screen displayed after screen blanking even when lock screen disabled
Public bug reported: Ubuntu 19.04 Gnome Screen lock is set to off in Settings->Privacy. Blank Screen is set to 10 minutes in Settings->Power. On returning from Screen Blank, Lock Screen is present. Does not occur after manual suspend (ie closing laptop lid) and resuming. In dconf I have set org/gnome/desktop/lockdown/disable-lock-screen to true. org/gnome/desktop/screensaver/lock-enabled is set to false org/gnome/desktop/screensaver/ubuntu-lock-on-suspend is set to false ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 4 19:25:36 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-22 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-04-24T23:58:15.215728 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1827751 Title: Lock screen displayed after screen blanking even when lock screen disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr
It says the sender of this error is gnome-session-b? who's that? where's the code that generates this error? I'm on 18.10, upgraded from 18.04 CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812527] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787], often when running Android emulator (QEMU)
@Pavel++ This also helps me out too. Thanks! My issue is reproducible as per the bug report 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 -- 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: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787], often when running Android emulator (QEMU) 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 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
Also affecting my Ubuntu 16.04 LTS laptop, all updates installed. -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
I don't understand this logic. So all of us using 18.04 LTS will have to live with this? Doesn't long term support indicate that this will get fixed? There's no workaround? -- 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/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon
Found the following two entries had been added to /etc/apt/sources.list following automatic updates. deb [trusted=yes] http://ftp.us.debian.org/debian experimental main deb [trusted=yes] http://ftp.us.debian.org/debian sid main Commented them out and performed apt update. Then purged the following packages: apt purge gnome-settings-daemon gdm3 gnome-control-center gnome-initial-setup gnome-power-manager gnome-shell uatter ubuntu-desktop ubuntu-session This removed these packages, then reinstalled all pre-existing packages. Reboot returned system to normal functionality. -- 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/1802677 Title: Unmet Dependencies: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon
If you reboot after receiving this error you will be unable to get back into the system. Boot up will hang at "Started Update UTMP about System Runlevel Changes. Alt-F2 allows you to switch to login prompt. However, attempts to purge gnome and related dependencies or perform any updates fail. -- 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/1802677 Title: Unmet Dependencies: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon
Affecting Ubuntu 18 since updates on 11/27. Update log file attached. /opt/symas/share/man/man1$ uname -a Linux launchpad.*.*** 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 GNU/Linux sudo apt-get install gnome-settings-daemon-schemas Reading package lists... Done Building dependency tree Reading state information... Done gnome-settings-daemon-schemas is already the newest version (3.28.1-0ubuntu1.1). gnome-settings-daemon-schemas set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (= 3.28.1-0ubuntu1) but 3.28.1-0ubuntu1.1 is to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: greybird-gtk-theme grub-gfxpayload-lists iputils-arping libart-2.0-2 libasn1-8-heimdal libfile-copy-recursive-perl libgcrypt20:i386 libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libkrb5-26-heimdal liblz4-1:i386 libpcre3:i386 libroken18-heimdal libselinux1:i386 libsysmetrics1 libthunarx-2-0 libwind0-heimdal networkd-dispatcher python3-macaroonbakery python3-nacl python3-protobuf python3-pymacaroons python3-rfc3339 python3-tz thunar-data xubuntu-icon-theme zlib1g:i386 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: gnome-settings-daemon The following packages will be upgraded: gnome-settings-daemon 1 upgraded, 0 newly installed, 0 to remove and 477 not upgraded. 1098 not fully installed or removed. Need to get 0 B/856 kB of archives. After this operation, 4,219 kB of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 299204 files and directories currently installed.) Preparing to unpack .../gnome-settings-daemon_3.30.1.2-1_amd64.deb ... Unpacking gnome-settings-daemon (3.30.1.2-1) over (3.28.1-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/gnome-settings-daemon_3.30.1.2-1_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/61-gnome-settings-daemon-rfkill.rules', which is also in package gnome-settings-daemon-schemas 3.28.1-0ubuntu1.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/gnome-settings-daemon_3.30.1.2-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Attachment added: "Update Log File" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+attachment/5217740/+files/dpkg.log -- 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/1802677 Title: Unmet Dependencies: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798790] Re: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot
As mentioned in the above askubuntu posting, removing the nvidia driver got me past the problem. -- 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/1798790 Title: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796004] [NEW] package xrdp 0.9.6-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1
Public bug reported: error occurred during upgrade running under Hyper-V on Windows 10 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: xrdp 0.9.6-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Wed Oct 3 12:34:58 2018 DuplicateSignature: package:xrdp:0.9.6-1 Installing new version of config file /etc/xrdp/xrdp_keyboard.ini ... ln: failed to create symbolic link '/etc/xrdp/cert.pem': File exists dpkg: error processing package xrdp (--configure): installed xrdp package post-installation script subprocess returned error exit status 1 ErrorMessage: installed xrdp package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0~rc2ubuntu1 SourcePackage: xrdp Title: package xrdp 0.9.6-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to cosmic on 2018-10-03 (0 days ago) mtime.conffile..etc.xrdp.sesman.ini: 2018-08-15T14:36:40.232083 mtime.conffile..etc.xrdp.xrdp.ini: 2018-08-15T14:36:40.228083 ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xrdp in Ubuntu. https://bugs.launchpad.net/bugs/1796004 Title: package xrdp 0.9.6-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1796004/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782679] [NEW] systemd-resolved can't resolve at all, need to add nameservers to resolve.conf
Public bug reported: I'm running Ubuntu 18.04 (upgraded from 17.10) on a machine with both ethernet and wifi interfaces. When I boot, my ethernet connection enp0s31f6 is brought up by Network Manager and given three nameserver addresses via DHCP, 10.1.13.10, 10.1.141.10, 10.1.13.36. Running nmcli shows the three nameservers under "DNS configuration". Running "systemd- resolve --status" shows them under a "Link 2 (enp0s31f6)" section. I can do a "ip route get to X" and ping each one successfully. No other connection is active. testuser ☼ systemd-resolve --status Global DNS Domain: orgsdomain.net DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp4s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp0s31f6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.1.13.10 10.1.141.10 10.1.13.36 DNS Domain: orgsdomain.net However, when I actually try to resolve a name, even the name of one of the nameservers, dig claims that "connection timed out: no servers could be reached". testuser ☼ dig dcpdc001.orgsdomain.net +nocookie ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> dcpdc001.orgsdomain.net +nocookie ;; global options: +cmd ;; connection timed out; no servers could be reached Note that this name should resolve to 10.1.13.10, the first nameserver. The "+nocookie" option is there to work around an issue with Windows DNS servers. But other than that, the servers themselves work fine if I tell dig where to look: testuser ☼ dig dcpdc001.orgsdomain.net +nocookie @10.1.13.10 ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> dcpdc001.orgsdomain.net +nocookie @10.1.13.10 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61294 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;dcpdc001.orgsdomain.net. IN A ;; ANSWER SECTION: dcpdc001.orgsdomain.net. 3600IN A 10.1.13.10 ;; Query time: 2 msec ;; SERVER: 10.1.13.10#53(10.1.13.10) ;; WHEN: Fri Jul 20 10:56:27 AEST 2018 ;; MSG SIZE rcvd: 65 I have configured resolvconf to use dynamic updates. /etc/resolv.conf points to /run/resolvconf/resolv.conf. This file contains only (non- comments): nameserver 127.0.0.53 search orgsdomain If I add "nameserver 10.1.13.10" to this file manually, suddenly dig can resolve again (without the @...), and anything else that needs to resolve names can do so. Removing the nameserver breaks that again. I don't know much about the servers. They're part of a Windows-based network, but since I can use them if I edit resolv.conf or give dig the address, I don't think they're the issue (except in the sense that maybe they require a feature that systemd-resolved doesn't support?). I increased the logging level of systemd-resolved to "debug" and "journalctl -f -u systemd-resolved" shows this during a failed query: Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Got DNS stub UDP query packet for id 19836 Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Looking up RR for dcpdc001.orgsdomain.net IN A. Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Switching to DNS server 10.1.13.10 for interface enp0s31f6. Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Cache miss for dcpdc001.orgsdomain.net IN A Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Transaction 12728 for scope dns on enp0s31f6/*. Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Using feature level UDP+EDNS0+DO+LARGE for transaction 12728. Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Using DNS server 10.1.13.10 for transaction 12728. Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Sending query packet with id 12728. Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]:
[Bug 1767693] Re: 18.04 GNOME displays at 60fps even if the monitor is set to 144hz
Seems related to https://bugzilla.gnome.org/show_bug.cgi?id=781296 There are hardcoded values at 60fps / 60hz / 16667. I rebuilt mutter and clutter with values at 144fps / 144hz / 6944, so far it seems to have helped but it's still not as smooth as other desktops. ** Bug watch added: GNOME Bug Tracker #781296 https://bugzilla.gnome.org/show_bug.cgi?id=781296 -- 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/1767693 Title: 18.04 GNOME displays at 60fps even if the monitor is set to 144hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1767693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767264] Re: Window manager refresh rate is different from monitor refresh rate
Also posted in #1767693 : Seems related to https://bugzilla.gnome.org/show_bug.cgi?id=781296 There are hardcoded values at 60fps / 60hz / 16667. I rebuilt mutter and clutter with values at 144fps / 144hz / 6944, so far it seems to have helped but it's still not as smooth as other desktops. ** Bug watch added: GNOME Bug Tracker #781296 https://bugzilla.gnome.org/show_bug.cgi?id=781296 -- 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/1767264 Title: Window manager refresh rate is different from monitor refresh rate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1767264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage
This also affects me, May 5 17:45:33 hulk gnome-software[8798]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed May 5 17:45:33 hulk gnome-software[8798]: Ignoring unexpected response May 5 17:45:33 hulk gnome-software[8798]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed May 5 17:45:33 hulk gnome-software[8798]: Ignoring unexpected response May 5 17:45:33 hulk gnome-software[8798]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed May 5 17:45:33 hulk gnome-software[8798]: Ignoring unexpected response Continues to fill up /var/log file system. -- 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/1723362 Title: gnome-software spams error messages to journald and causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767544] Re: While running the Orca screen reader, system hangs while gnome-control-center is open
On my computer, Orca tried to read part of the Wi-Fi settings screen before it locked up and exhibited the same behavior that was described in Jeremy's audio recording. -- 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/1767544 Title: While running the Orca screen reader, system hangs while gnome- control-center is open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices
linuxcub, my apologies for not replying sooner -- I don't think I got a notification of your messages for some reason... Its odd that installing/reinstalling portions of Ubuntu seem to fix the issue. It looks like the Bionic beta only relased IOSs for Kubuntu, Budgie, Kylin, MATE, and Xubuntu. I wonder if their GNOME flavor is still in development and was updated to a broken version when you installed. Force-installing the ubuntu-gnome-desktop and gnome-control- center packages may have brought down a fixed version? Without an official GNOME ISO for me to test, it'll be hard for me to replicate your issue to see if its still present. -- 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/1753525 Title: Wacom tablet not recognized in Settings > Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed
I haven't tried 4.16 but it is present in mainline 4.15.8 ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed ** Changed in: systemd (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Kernel 4.9+ regression: Suspend - Freezing of tasks failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices
The "stylus not recognized" part of this issue is almost certainly https://bugzilla.gnome.org/show_bug.cgi?id=793499. No access to the pad device on the other hand is not an issue I'm familiar with. The old unity-control-center bug that OP linked do was due to an issue with GNOME not being compatible with tablets whose pens don't have an eraser. That issue was fixed in GNOME 3.16, however, and shouldn't be present in the current version of the gnome-control-center. I do see a reference to somebody else having similar pad issues upstream at https://bugzilla.gnome.org/show_bug.cgi?id=789287 but it doesn't look like anyone has begun to dig into the bug. My own (Arch Linux) system doesn't exhibit the pad issue with an Intuos Art Medium (CTH-690) and GNOME 3.26, for what its worth. linuxcub: You should have both a "Stylus" and "Tablet" button at the top of the Wacom control panel, next to "Test your Settings". The "Stylus" button shows "Stylus not Recognized", but what message appears when the "Tablet" button is pressed? Or are the buttons missing? That might give a place to start digging... ** Bug watch added: GNOME Bug Tracker #793499 https://bugzilla.gnome.org/show_bug.cgi?id=793499 ** Bug watch added: GNOME Bug Tracker #789287 https://bugzilla.gnome.org/show_bug.cgi?id=789287 -- 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/1753525 Title: Wacom tablet not recognized in Settings > Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1749890] [NEW] Cannot connect to WebDAV (Owncloud): "Not a WebDAV enabled share"
Public bug reported: Under 17.04, I had added an Owncloud account to the Gnome Online Accounts under Gnome 3. This created an entry in Nautilus' sidebar that allowed me to remotely browse my Owncloud account. Since upgrading to 17.10, clicking on the entry just brings up an error dialog: Unable to access "@" Not a WebDAV enabled share [OK] I get exactly the same error if I type "davs:///remote.php/webdav/" into the location field. I had earlier accessed the same server successfully that morning under 17.04, and I'm certain nothing's changed server side. Rebooting doesn't help, installing davfs2 doesn't help, neither does fusedav. I've tried removing and re-adding the account in Online Accounts. The server is accessible via web and the desktop sync client sees it fine. The server is not internal, it's on the public internet. There is a corporate proxy for which I use CNTLM. But again, this hasn't changed since before the upgrade. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 16 14:28:56 2018 InstallationDate: Installed on 2017-04-25 (296 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2018-01-24 (22 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session -- 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/1749890 Title: Cannot connect to WebDAV (Owncloud): "Not a WebDAV enabled share" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1749890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724955] Re: unable to drag monitors in Display Arrangement
I have three screens: builtin laptop screen and two external monitors. If I turn off the builtin laptop screen, I am not able to rearrange the remaining two screens with the mouse. But if I have all 3 screens enabled I can arrange them as desired and then turn off the builtin screen after. This confirms dreamwalker's solution. -- 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/1724955 Title: unable to drag monitors in Display Arrangement To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1724955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt
I just upgraded from 17.04, but it's impossible to complete the upgrade because of this. -- 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/1730672 Title: Proxy settings not applied system-wide, are not used by Software Update or apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"
** Changed in: gdm3 (Ubuntu) Status: Confirmed => Fix Released -- 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/1706939 Title: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736583] Re: Evince annotations lost on save
Sorry, that was supposed to be Evince 3.24.0 on Ubuntu 17.04. -- 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/1736583 Title: Evince annotations lost on save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1736583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736583] Re: Evince annotations lost on save
This was using Evince 3.24.0 on Ubuntu 17.10. -- 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/1736583 Title: Evince annotations lost on save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1736583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736583] [NEW] Evince annotations lost on save
Public bug reported: I used Evince to annotate a ~70 page PDF. Over a few hours I added a handful of annotations to each page. After every 5th page or so I would "Save a Copy" in a new file name (same filename on every save). When I finished editing the document I saved and noticed that the modified time was not updating on the file. When opening the copy, no annotations were present. I tried saving as different file names and the same thing occurred. Then, stupidly, I opened the original file and it closed the file I had open with the hundreds of annotations and now no files have the annotations. My computer is currently at this state. I would really like to be able to recover the annotations if they happen to be in a cache file somewhere. Secondly, this seems to be a bug. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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/1736583 Title: Evince annotations lost on save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1736583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1692528] Re: gnome-control-center assert failure: *** Error in `gnome-control-center': malloc(): memory corruption (fast): 0x0000556f8e277810 ***
Can confirm @AsciiWolf's comment. Clicking "Region & Language" will cause the gnome-control-center to crash. -- 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/1692528 Title: gnome-control-center assert failure: *** Error in `gnome-control- center': malloc(): memory corruption (fast): 0x556f8e277810 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1692528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1668089] Re: Picasa API 501 Not Implemented
Since the feature is gone, it would be nice if we could select and drag photos from Shotwell into the photos.google.com browser interface. Currently you have to find the files on the file system to be able to drag them. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1668089 Title: Picasa API 501 Not Implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1668089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1671274] Re: network interface doesn't come up after installation in VM
maas 2.2.0~beta3+bzr5787-0ubuntu1~16.04.1 python3-curtin 0.1.0~bzr460-0ubuntu1~16.04.1 curtin config: http://paste.ubuntu.com/24146369/ There is nothing in /etc/network/interfaces.d/*.cfg ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671274 Title: network interface doesn't come up after installation in VM To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1671274/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 151365] Re: Autosave doesn't work for Unsaved Documents
I dug into the code to try and fix this, but it's a lot more complex than it looks. If anyone wants to start digging, look at `gedit- tab.c:248` - that's the first catch conditional. Also look at the function getting called if that conditional passes - there's a similar catch conditional in there. The main problem is that auto-save pulls in the file object, which doesn't exist if the document is unsaved. Autosave would actually have to save the file to some special "temporary" directory. Easier said than done. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/151365 Title: Autosave doesn't work for Unsaved Documents To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/151365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1668089] Re: Picasa API 501 Not Implemented
How unfortunate. This is one of my most used Shotwell features. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1668089 Title: Picasa API 501 Not Implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1668089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1668089] [NEW] Picasa API 501 Not Implemented
Public bug reported: I tried to publish an album to picasaweb and get a "501 Not Implemented" message (screenshot attached). Shotwell 0.24.5. ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Selection_149.jpg" https://bugs.launchpad.net/bugs/1668089/+attachment/4827216/+files/Selection_149.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1668089 Title: Picasa API 501 Not Implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1668089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'
Confirmed #15 workaround works for me. Note, reboot/relogin is needed after editing the file. Ubuntu 16.10 fresh install. -- 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/1633162 Title: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents' To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1633162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640947] Re: Can't scroll in events with Shotwell 0.22 in Ubuntu 16.10
Is this going to be fixed in Ubuntu 16.10? That's the main issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1640947 Title: Can't scroll in events with Shotwell 0.22 in Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1640947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640947] [NEW] Can't scroll in events with Shotwell 0.22 in Ubuntu 16.10
Public bug reported: I upgraded to Yakkety and the latest Shotwell is unusable due to the inability to scroll through any of the windows that show events or images. In particular the event screen doesn't allow scrolling. ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1640947 Title: Can't scroll in events with Shotwell 0.22 in Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1640947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639785] [NEW] Textbox appears when typing on empty desktop.
Public bug reported: If I have a clear desktop (i.e. no windows showing) and I start typing, a text box appears. I don't know what it's for, and it seems to have no purpose. Expected behavior: Nothing should happen when I type on a clear desktop. Screen shot attached. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nautilus 1:3.20.3-1ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 7 07:31:44 2016 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'651x716+65+24'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2016-11-02 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "unity desktop bug croped.png" https://bugs.launchpad.net/bugs/1639785/+attachment/4774011/+files/unity%20desktop%20bug%20croped.png -- 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/1639785 Title: Textbox appears when typing on empty desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1639785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1632767] [NEW] yakkety: desktop ISO fails to reboot after install: Failed deactivating swap
Public bug reported: The 20161012.1 yakkety desktop ISO fails to reboot after the install completes (see attached screenshot). Tested on QEMU in BIOS and UEFI mode, which is where the screenshot is from. Same thing is seemingly happening on hardware (reboot hangs), although I don't see this particular debugging output on hardware. The systemd related logging might be a red haring... I'm not sure this is actually a systemd bug, just that it seems the correct starting point. Thanks! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety ** Attachment added: "Screenshot from 2016-10-12 06-14-05.png" https://bugs.launchpad.net/bugs/1632767/+attachment/4759958/+files/Screenshot%20from%202016-10-12%2006-14-05.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1632767 Title: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632767/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1597876] [NEW] installing/upgrading packages containing systemd services results in prompt for cryptoswap passphrase [xenial]
Public bug reported:
This is an extremely odd bug that requires a very specific scenario to
reproduce:
1) You need to be using an ecryptfs-style cryptoswap partition (as would
be setup when you choose "Encrypt my home directory" during the
installation)
2) The underlying physical swap partition used for the cryptoswap needs
to be on a GPT partitioned drive
3) The GUID specific bit 63 ("no auto mounting") must *not* be set on
the underlying physical swap partition
In this scenario, installing/upgrading/reinstalling seemingly *any*
package with a systemd service will result in the user getting *twice*
prompted for a passphrase to unlock their cryptoswap partition. If
upgrades are performed using the graphical Software Updater, the user
wont be aware of this issue unless they've expanded the details,
resulting in the Software Updater hanging indefinitely.
For example, if you have the needed setup, you can easily reproduce this
bug with:
sudo apt-get install --reinstall whoopsie
After which you'll encounter something like this:
(Reading database ... 177827 files and directories currently installed.)
Preparing to unpack .../whoopsie_0.2.52.1_amd64.deb ...
Please enter passphrase for disk primary (cryptswap1) on none!
Unpacking whoopsie (0.2.52.1) over (0.2.52) ...
Preparing to unpack .../libwhoopsie0_0.2.52.1_amd64.deb ...
Unpacking libwhoopsie0:amd64 (0.2.52.1) over (0.2.52) ...
Processing triggers for systemd (229-4ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Setting up libwhoopsie0:amd64 (0.2.52.1) ...
Setting up whoopsie (0.2.52.1) ...
Please enter passphrase for disk primary (cryptswap1) on none!
Processing triggers for libc-bin (2.23-0ubuntu3) ...
(You can just hit enter each time the "Please enter passphrase for..."
prompt comes up.)
For some background: in modern systemd times, ecryptfs-style cryptoswaps
are broken when the underlying physical GPT swap partition does not have
bit 63 set:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1447282
During the boot the user is erroneously prompted for a passpharase to
unlock the cryptoswap (you can hit enter for an empty passphrase, or
enter any passphrase you want... either way, nothing seems to actually
be done with it). After the boot completes, the underlying physical swap
partition will be mounted normally (ie, you wont actually be using
encrypted swap... so a false sense of security, which is of course
concerning).
Although lp:1447282 has been fixed for the most common hardware
configurations, it's still possible for users to encounter this problem
in the real-word: ecryptfs-setup-swap currently fails to set bit 63 when
the physical GPT swap partition is on an NVMe or MMC drive:
https://bugs.launchpad.net/ecryptfs/+bug/1597154
So one way to reproduce this is to install Ubuntu 16.04 onto an NVMe
drive and choose "Encrypt my home directory" during the installation.
To make debugging this easier without requiring an NVMe drive (and
especially so it's easier to debug in a UEFI VM), I'm attaching a script
that will unset bit 63 on the underlying GPT swap partitions used by any
ecryptfs-style cryptoswaps that are present.
If you run my script:
sudo python3 unset-bit-63.py
And then reboot, you should now be able to reproduce this bug.
Even though fixing lp:1597154 will mean users shouldn't encounter
(during normal real-world usage) this strange behavior when
installing/upgrading/reinstalling packages that contain systemd
services, I have a strong hunch that the fact this can happen at all
indicates something is quite wonky in either systemd itself or in the
Debian/Ubuntu specific systemd trigger handling.
Thanks!
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "unset-bit-63.py"
https://bugs.launchpad.net/bugs/1597876/+attachment/4692952/+files/unset-bit-63.py
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1597876
Title:
installing/upgrading packages containing systemd services results in
prompt for cryptoswap passphrase [xenial]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1500039] Re: Ubuntu Phone is not getting a mobile network cell triangulation position
Confirmed on on Bq E4.5 on rc-proposed (r741) the following: Wifi ON, mobile data ON - network based location does NOT work. Wifi ON, mobile data OFF - network based location works. Wifi OFF, mobile data ON - network based location does NOT work. And there is nothing wrong with my mobile data. The network based location used to work until some time ago, so this is definitely a regression. I couldn't find a more appropriate bug for this so adding to this one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1500039 Title: Ubuntu Phone is not getting a mobile network cell triangulation position To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1583879] Re: apt-get update hangs indefinitely, appstreamcli using 100% CPU
Also, the graphical Ubuntu Software Updater is likewise hanging indefinitely. And I've confirmed this on 3 different systems so far. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1583879 Title: apt-get update hangs indefinitely, appstreamcli using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1583879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1583879] [NEW] apt-get update hangs indefinitely, appstreamcli using 100% CPU
Public bug reported: Just ran `sudo apt-get update`, which is hanging indefinitely after the downloads complete, the last CLI output from which is: Fetched 733 kB in 1s (399 kB/s) Looking at `top` suggests `appstreamcli` is the culprit as it's pegged at near 100% CPU usage: 100 0.1 18:29.02 appstreamcli If I kill the hung `sudo apt-get update` process with Control+C, the `appstreamcli` process goes away. Retrying `sudo apt-get update` has the same result. On a whim I also tried `sudo apt update`, but it seems to have the same problem. It hangs indefinitely and running it results in an `appstreamcli` process consuming 100% CPU. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 19 20:53:40 2016 SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1583879 Title: apt-get update hangs indefinitely, appstreamcli using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1583879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1575484] Re: "Set document metadata failed"
** Attachment removed: "Browser.png" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1575484/+attachment/4655693/+files/Browser.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1575484 Title: "Set document metadata failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1575484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1575484] Re: "Set document metadata failed"
I have a similar issue. I was already unable to access a NAS network share, but after sudo gediting smb.conf, the network icon is missing from the file browser. jason@jason-MS-7721:~$ sudo gedit /etc/samba/smb.conf [sudo] password for jason: ** (gedit:2527): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported jason@jason-MS-7721:~$ sudo gedit /etc/samba/smb.conf (gedit:2578): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (gedit:2578): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-enabled not supported ** (gedit:2578): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported ** (gedit:2578): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-enabled not supported ** (gedit:2578): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported ** (gedit:2578): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported ** Attachment added: "Browser.png" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1575484/+attachment/4655693/+files/Browser.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1575484 Title: "Set document metadata failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1575484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1366221] Re: gnome-calculator does not show application menu anywhere
Using Unity on Ubuntu 16.04 freshly installed: jcurl@leon-ubuntu:~/Programming/SerialPortStream/dll/serialunix/build$ gnome-calculator -v gnome-calculator 3.18.3 The "dconf" tool is a workaround, but I cannot enable the menu by default. Not sure why it's "low", it's a problem for a long time (reported in other forums since 13.04). It would sure be nice to have something to make it easy to move from windows ;) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1366221 Title: gnome-calculator does not show application menu anywhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1366221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 485745]
*** This bug has been marked as a duplicate of bug 93299 *** -- 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/485745 Title: Evince presents PDF with mis-rendered Hebrew To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/485745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 485745]
(In reply to Thomas Freitag from comment #5) > May You have a look at bug 43488 and bug 41104 if Your patch of bug 93299 > fixes them, too? And mark them as duplicate if so? No, my patch does not fix either of those. The files in both of those bugs directly use the glyph IDs to look up glyphs. Which is completely insane for a non-embedded font because glyph IDs are not in any way portable. To get them to work you could install the exact same Arial font. Not just a similar or compatible font like Liberation Sans, but Microsoft's own Arial font. Installing msttcorefonts should work. Might have to also add a fontconfig rule to match ArialMT to Arial. -- 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/485745 Title: Evince presents PDF with mis-rendered Hebrew To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/485745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 485745]
This file would be fixed by my patch in bug 93299. It provides fontconfig some hints about the character encoding so it can do better at choosing an appropriate font. -- 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/485745 Title: Evince presents PDF with mis-rendered Hebrew To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/485745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 667752]
The "narrow text" part of this should be fixed with bug 94054. -- 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/667752 Title: Non-embedded standard fonts in PDF files are not displayed/rendered correctly To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/667752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 33288]
Created attachment 121848 Cache result of inner loop in visitDepthFirst This is an alternative to Brian's patch in comment 65. This speeds up the visitDepthFirst function by caching the result in the inner loop. This provides a similar speedup without changing the output of pdftotext. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/33288 Title: Evince doesn't handle columns properly To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/33288/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1528043] Re: gvfsd samba doesn't work well with Windows under certain circumstances
Hitting F5 to refresh a few times on an affected directory will also cause the file manager Nautilus/Nemo to lock up, probably waiting for gvfs, and not recover. -- 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/1528043 Title: gvfsd samba doesn't work well with Windows under certain circumstances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1528043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1540195] Re: extra toolbar buttons don't show in Fullscreen mode
Ok, sorry. From http://mate-desktop.com/, it seems that atril is a fork of evince. I had thought it was merely a rename to avoid MATE/GNOME conflicts. So I understand better: are you saying that evince doesn't have this bug? And that improvements made to evince will not necessarily show up in atril? -- 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/1540195 Title: extra toolbar buttons don't show in Fullscreen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1540195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1540195] [NEW] extra toolbar buttons don't show in Fullscreen mode
Public bug reported: I used the Edit / Toolbar command to add some buttons to the toolbar. These ordinarily show up, but not in Fullscreen mode. Version info: LInux Mint 17.1, MATE edition, based on Ubuntu 14.04. In MATE, evince is renamed to atril: MATE Document Viewer 1.8.1. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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/1540195 Title: extra toolbar buttons don't show in Fullscreen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1540195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1528043] [NEW] gvfsd samba doesn't work well with Windows under certain circumstances
Public bug reported:
When accessing shares that have files that aren't completely accessible
to the logged in user gfvs will error, not show some files/folders, or
not show any files/folders.
Accessing folders such as C:/, C:/Users, or an actual users folder will
cause the error.
Simply navigate to one of these folders, you should not see all
available files. If you refresh {f5} a few times you'll see all
different behaviours.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gvfs-backends 1.26.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Dec 20 14:55:29 2015
InstallationDate: Installed on 2015-12-20 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gvfs
UpgradeStatus: Upgraded to xenial on 2015-12-20 (0 days ago)
** Affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
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/1528043
Title:
gvfsd samba doesn't work well with Windows under certain circumstances
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1528043/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1526987] [NEW] package systemd 225-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: error on install ProblemType: Package DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Fri Dec 11 17:46:26 2015 DuplicateSignature: package:systemd:225-1ubuntu9:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-02-08 (311 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=0f39d1b3-ff04-41d9-87fd-5bf70bd2f226 ro quiet splash RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: systemd Title: package systemd 225-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-12-12 (4 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1526987 Title: package systemd 225-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1526987/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1368756] Re: "recently used" files not correctly right-clickable
Opened bug report at GNOME as suggested above, link as follows: https://bugzilla.gnome.org/show_bug.cgi?id=758955 ** Bug watch added: GNOME Bug Tracker #758955 https://bugzilla.gnome.org/show_bug.cgi?id=758955 -- 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/1368756 Title: "recently used" files not correctly right-clickable To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1368756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1508766] [NEW] /etc/machine-id not created if missing
Public bug reported: If /etc/machine-id is missing at boot, systemd does not create it. I came across lp:1387090 in which Martin Pitt mentions that it should be created if missing, but is unsure why this doesn't work. I'm likewise unsure why it doesn't work, but this bit from dmesg makes me think it *might* be because systemd is trying to do so while the rootfs is still mounted read-only, before it gets remounted read-write: [ 19.240451] systemd[1]: System cannot boot: Missing /etc/machine-id and /etc is mounted read-only. [ 19.240464] systemd[1]: Booting up is supported only when: [ 19.240466] systemd[1]: 1) /etc/machine-id exists and is populated. [ 19.240467] systemd[1]: 2) /etc/machine-id exists and is empty. [ 19.240468] systemd[1]: 3) /etc/machine-id is missing and /etc is writable. A missing /etc/machine-id file has broad consequences for the boot process. As one example, the Journal Service doesn't get started. This problem appears to have greater impact now that on Wily (desktop) /var/lib/dbus/machine-id is a symlink to /etc/machine-id. Previously the system dbus instance would generate the machine-id with dbus-uidgen if the file was missing, but on Wily desktop it wont. Note that on Wily server /var/lib/dbus/machine-id is a regular file, is not a symlink to /etc/machine-id. I filed lp:1508697 about this separate issue as it seems strange for this to be different between Wily desktop and server. Thanks! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 21 19:57:58 2015 JournalErrors: No journal files were found. -- No entries -- MachineType: System76, Inc. Gazelle Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=424ed0f3-306d-4302-b58c-6b1e7adb7c74 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/16/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp7:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp7:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: Gazelle Professional dmi.product.version: gazp7 dmi.sys.vendor: System76, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1508766 Title: /etc/machine-id not created if missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1508766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1456616]
*** This bug has been marked as a duplicate of bug 66229 *** -- 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/1456616 Title: unable to rotate a pdf coming from Firefox (Google maps) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1456616/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1479524] Re: Totem Crashes at launch from missing libwayland-egl
** Also affects: system76 Importance: Undecided Status: New -- 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/1479524 Title: Totem Crashes at launch from missing libwayland-egl To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1479524/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1479524] Re: Totem Crashes at launch from missing libwayland-egl
** Tags added: 14.04.3 -- 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/1479524 Title: Totem Crashes at launch from missing libwayland-egl To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1479524/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1447282] [NEW] Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs)
Public bug reported: I'm still sorting out the details and eliminating variables, but as far as I can tell: Steps to reproduce === 1) Install Ubuntu using GPT partitioning for the OS drive[*] 2) Choose require my password to login, and check encrypt my home directory Expected behavior === No special user interaction should be required to initialized the crytposwap other than normally logging in Actual behavior Prior to lightdm coming up, you will be prompted to enter your passphrase to unlock the cryptoswap, similar to how you would be prompted to unlock the OS drive when using full disk encryption (see attached photo). When lightdm comes up, you have to enter your password/passphrase again to login. Work-arounds === 1) This only seems to happen when using GTP partitioning, not MBR... so use MBR if you can 2) Even with GTP partitioning, booting with init=/sbin/upstart seems to reliably fix the problem, so it certainly seems systemd related Notes = * As far as I can tell, there isn't a way to force Ubiquity to create a GPT partition table when the OS drive is 2TB, but it will automatically use GPT partitioning when the OS drive is = 2TB. My particular test was done using the System76 imaging server, which by default uses GPT partitioning even when the OS drive is 2TB. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:40:29 2015 EcryptfsInUse: Yes MachineType: System76, Inc. Kudu Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e6c5aea5-d57c-410d-abce-66e96175e946 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Kudu Professional dmi.board.vendor: System76, Inc. dmi.board.version: kudp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: kudp1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnKuduProfessional:pvrkudp1:rvnSystem76,Inc.:rnKuduProfessional:rvrkudp1:cvnSystem76,Inc.:ct9:cvrkudp1: dmi.product.name: Kudu Professional dmi.product.version: kudp1 dmi.sys.vendor: System76, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ecryptfs systemd-boot vivid ** Attachment added: IMG_7979_01.jpg https://bugs.launchpad.net/bugs/1447282/+attachment/4381692/+files/IMG_7979_01.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447282 Title: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 116453]
*** Bug 66569 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/116453 Title: evince can not find ü in attached PDF To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/116453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39890]
*** Bug 13441 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/39890 Title: characters change when selecting text To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/39890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
