[Bug 1915091] Re: Nautilus shows LXD storage pool in sidebar
Ok, so the mount table output confirms that your LXD default storage pool isn't visible in the host's mount table, so that's not what's triggering nautilus. Also, if that was the case, I'd have seen it on my own machine a long time ago ;) My best guess is that it's the loop device (also called default.img) which nautilus is incorrectly showing as some kind of external block device (like a USB stick or SD card). You'll most likely see it in `losetup -a` and it may show up in some `/dev/disk/` sub-directories which I supposed nautilus or something in the gnome desktop is monitoring. Unfortunately unlike actual mount entries that we can hide in a different mount namespace or pass custom mount flags to have the desktop ignore, the same can't be done with block devices, so re-assigning this to nautilus for further investigation. ** Package changed: lxc (Ubuntu) => nautilus (Ubuntu) -- 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/1915091 Title: Nautilus shows LXD storage pool in sidebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896654] Re: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)
*** This bug is a duplicate of bug 1896627 *** https://bugs.launchpad.net/bugs/1896627 I can confirm this problem with Ubuntu 20.10, NVIDIA (prime mode OnDemand) with Xorg. Windows flicker when resizing any windows. -- 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/1896654 Title: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871082] Re: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup)
Fixed with today's 20.10 update (gedit 3.38.0). ** Changed in: gedit (Ubuntu) Status: New => Fix Released -- 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/1871082 Title: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1871082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871082] Re: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup)
Fixed upstream (v3.38). https://gitlab.gnome.org/GNOME/gedit/issues/177 https://gitlab.gnome.org/GNOME/gedit/-/issues/188 Meanwhile, before v3.38 is released and imported, just updating get_active_window (in gedit-app.c) fixes the bug. I built gedit from source and compared before/after, it works fine. ** Bug watch added: gitlab.gnome.org/GNOME/gedit/issues #177 https://gitlab.gnome.org/GNOME/gedit/issues/177 ** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #188 https://gitlab.gnome.org/GNOME/gedit/-/issues/188 -- 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/1871082 Title: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1871082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871082] [NEW] gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup)
Public bug reported: I've had this bug for I'd say a couple of weeks, maybe a month or two. I use a dual screen setup. If the gedit window is on my secondary (right) screen and I open a recent file, gedit does not open it in the current window and creates a new one (which is annoying and unexpected). The bug doesn't happen if gedit is on my primary (left) screen, or if the gedit window is at the edge of my secondary screen. Also, if there is a gedit window on both screens and I try to open a recent file on the secondary monitor, it will open it in the gedit window on the other (primary) screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 12:40:31 2020 InstallationDate: Installed on 2016-10-27 (1256 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2019-11-09 (149 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- 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/1871082 Title: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1871082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870354] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed()
https://github.com/gTile/gTile/issues/124 ** Bug watch added: github.com/gTile/gTile/issues #124 https://github.com/gTile/gTile/issues/124 -- 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/1870354 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870354/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870354] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed()
Tracked it down to gTile being the issue actually, disabling that one with the rest of them on seems to fix it. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1870354 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870354/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866368] Re: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0)
Thanks Rocko. I had this bug too. It used to happen systematically when I moved a Firefox tab over a LibreOffice Writer window. So now, after the gnome-shell 3.36.0-2ubuntu2 update, I tried again and failed to make it crash. Seems fixed. -- 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/1866368 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868260] Re: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement
Note that these settings are additive: for instance, if Display Sleep Mode timeout is 5 mins and Sleep/Alternative Low Power Mode is set to 20 mins, the machine will actually suspend after 20 + 5 = 25 mins. -- 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/1868260 Title: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868260/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
I will look into it. Here is how to reproduce the bug very easily: - open LibreOffice Writer - open Firefox - resize and move the windows so that they don't overlap - drag the Firefox tab (not window) over LibreOffice Then you instantly get the crash. -- 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/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Here is the backtrace and registers. At first I couldn't reproduce the bug by just moving youtube videos (in firefox) around. But then when I had a document in LibreOffice Writer open (which is the situation I was in over the last few days of crashes), it happened very easily. --- Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. 0x7f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 (gdb) bt #0 0x7f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #1 0x7f65563fe3f9 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #2 0x7f65563ff413 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #3 0x7f6556420110 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #4 0x7f65563dee69 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #5 0x7f6555ff0f6f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #6 0x7f6555ff135a in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #7 0x7f6555fb9094 in gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #8 0x7f6555ff1006 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #9 0x7f6556ef0fbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f6556ef1240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f6556ef1533 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f65563bb970 in meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #13 0x560782a19d85 in ?? () #14 0x7f655613d1e3 in __libc_start_main (main=0x560782a19930, argc=1, argv=0x7ffe0362fc48, init=, fini=, rtld_fini=, stack_end=0x7ffe0362fc38) at ../csu/libc-start.c:308 #15 0x560782a19f5e in ?? () (gdb) info registers rax0xffb0 -80 rbx0x56078765c2c0 94590336352960 rcx0x7 7 rdx0x5607850dab40 94590297025344 rsi0x5607857211d0 94590303605200 rdi0x0 0 rbp0x 0x rsp0x7ffe0362f698 0x7ffe0362f698 r8 0x7f650c003300 140071969764096 r9 0x56078a5d8740 94590386145088 r100x560784463018 94590283952152 r110x7ffe0362f538 140728955237688 r120x1 1 r130x7f650c003350 140071969764176 r140x56078765c2c0 94590336352960 r150x560784e680b0 94590294458544 rip0x7f6555da3624 0x7f6555da3624 eflags 0x10202 [ IF RF ] cs 0x3351 ss 0x2b43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 -- 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/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Here is a log with a few crashes. It seems to always come after a few of these: Mar 6 01:24:57 wolfenstein rtkit-daemon[1197]: Supervising 9 threads of 5 processes of 1 users. Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: message repeated 19 times: [ Supervising 9 threads of 5 processes of 1 users.] Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: Successfully made thread 122522 of process 122427 owned by '1000' RT at priority 10. The log lacks the last crash (~19:20) since I attached gdb to the running gnome-shell process but couldn't switch back to the console gdb was started from (frozen screen, but I could hear the video was still playing). Will try attaching through ssh from another computer next time. ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+attachment/5334373/+files/log.txt -- 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/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Got the same bug (GNOME Shell crashed with signal 11 after a short video freeze) on 20.04. It's pretty recent, it's been crashing my computer a couple of times a day since March 3 (according to the logs). I keep my computer updated every day. Seems to happen when I move a video from one monitor to the other. -- 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/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1405005] Re: GNOME Calendar doesn't show correct first day of the week
** Package changed: calendar (Ubuntu) => gnome-calendar (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1405005 Title: GNOME Calendar doesn't show correct first day of the week To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1405005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1577527] Re: Calendar Theme Issue
** Package changed: calendar (Ubuntu) => gnome-calendar (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1577527 Title: Calendar Theme Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1577527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757068] Re: Night light brakes when screen dims
Phew, thankfully every so often I was able to access the command line with Ctrl + Alt + F2 without it flashing back to the boot messages (maybe once every twenty times) and then removed the flag from the .desktop file. Took me a couple of hours as it was really erratic behaviour. (The recovery mode didn't help either, same flashing between bootup commands and black screen.) I won't try that flag again! Any other way I can provide a useful log? -- 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/1757068 Title: Night light brakes when screen dims To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1757068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757068] Re: Night light brakes when screen dims
Hi Sebastien I added `--debug` to the Exec line in org.gnome.SettingsDaemon.Color.desktop but now I get stuck on this when booting up: started hold until boot process finishes up. Could that be related? I can't think of anything else fancy I did, and now I can't use my computer :/ -- 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/1757068 Title: Night light brakes when screen dims To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1757068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 896836] Re: Segmentation fault when asking help() for the list of modules
Still present in Ubuntu 18.04, using the python3.6 prompt in the shell:
```
>>> help('modules')
Please wait a moment while I gather a list of all available modules...
[ecc] warning: libsecp256k1 library not available, falling back to python-ecdsa
WARNING:root:can not import unity GI Namespace Dbusmenu not available
/usr/lib/python3/dist-packages/matplotlib/cbook/deprecation.py:106:
MatplotlibDeprecationWarning: The mpl_toolkits.axes_grid module was deprecated
in version 2.1. Use mpl_toolkits.axes_grid1 and mpl_toolkits.axisartist provies
the same functionality instead.
warnings.warn(message, mplDeprecation, stacklevel=1)
Segmentation fault
```
No issue when doing the same thing with Python 3.7.1 provided by
Anaconda.
** Also affects: python3.6 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in Ubuntu.
https://bugs.launchpad.net/bugs/896836
Title:
Segmentation fault when asking help() for the list of modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/pygtk/+bug/896836/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757068] Re: Night light brakes when screen dims
With `journalctl -r`, the only thing I get when the screen starts dimming and the nightlight is deactivated, is this line (username and machine name not shown): Jan 20 22:42:02 x-x gnome-screensav[4274]: Source ID 1654 was not found when attempting to remove it Hope this helps! -- 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/1757068 Title: Night light brakes when screen dims To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1757068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757068] Re: Night light brakes when screen dims
Okay I just did some more testing on only my built-in laptop display. It is not the "dim screen when inactive" setting that breaks the night light, that works fine, the screen is dimmed at once, and the night light is still active. What breaks the night light is the progressive dimming of the screen brightness that directly precedes the blanking of the screen when the "blank screen" setting is on (i.e. not set to "never"). When the night light is "broken" by the pre-blanking progressive dimming, it does not re-activate either when stopping the process by moving the mouse, nor when turning the display on again after the screen was blanked. To re-activate the night light, we have to go to the Night Light settings / widget and turn it off and on again. Still on Ubuntu Budgie 18.04 derivative, with all packages up to date (bionic-security + bionic-updates). Hopefully that makes it clearer, and @jesse111 can confirm. -- 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/1757068 Title: Night light brakes when screen dims To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1757068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757068] Re: Night light brakes when screen dims
Just adding to my previous comment #4: the external monitor behaviour is inconsistent. With a different brand, the original workaround (turning night light off and back on) works, without needing to unplug the monitor. -- 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/1757068 Title: Night light brakes when screen dims To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1757068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757068] Re: Night light brakes when screen dims
I believe I have the same issue. I originally reported it as the current duplicate Bug #1791659. The issue is as described here: the night light mode turns off as the screen starts dimming right before it blanks. The mode then needs to be turned off and on to work again. If I have an external monitor connected, as "join monitors", the external monitor is the one that loses the night light, whereas the built-in display still has it. The workaround around this is unplugging and plugging the screen back in. I use the following: gnome-control-center version: 1:3.28.2-0ubuntu0.18.04.2 gnome-shell version: 3.28.3-0ubuntu0.18.04.2 System details: OS: Ubuntu 18.04.1 LTS x86_64 Host: N230WU Kernel: 4.15.0-33-lowlatency Uptime: 3 days, 1 hour, 12 mins Packages: 2921 Shell: bash 4.4.19 Resolution: 1920x1080, 1920x1080 DE: Budgie WM: Mutter(Budgie) Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: tilix CPU: Intel i7-8550U (8) @ 4.000GHz GPU: Intel UHD Graphics 620 Memory: 4168MiB / 15918MiB -- 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/1757068 Title: Night light brakes when screen dims To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1757068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791659] Re: night light is off on external monitor after screen goes to sleep
*** This bug is a duplicate of bug 1757068 *** https://bugs.launchpad.net/bugs/1757068 Hm actually, I think it might be a duplicate of this one: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1757068 I just tested it further, and the same happens without an external monitor. Also, I noticed that the night light stops working as the screen dims right before it blanks. Marking this as a dupe. Probably good news. ** This bug has been marked a duplicate of bug 1757068 Night light brakes when screen dims -- 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/1791659 Title: night light is off on external monitor after screen goes to sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1791659/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791659] [NEW] night light is off on external monitor after screen goes to sleep
Public bug reported: Using the night light on both the built-in screen and an external monitor (connected via VGA) in "Join Displays" mode, everything works fine until the screen goes to sleep (aka "blank screen" in "Settings > Power > Power Saving): the night light is still active on the built-in screen but not on the external monitor anymore. I have to unplug and plug back in the VGA for the night light to be restored on the external monitor. Turning the night light on and off does not restore it on the external monitor. I have checked other bug reports related to night light, but couldn't find a description of my issue. gnome-control-center version: 1:3.28.2-0ubuntu0.18.04.2 gnome-shell version: 3.28.3-0ubuntu0.18.04.2 System details: OS: Ubuntu 18.04.1 LTS x86_64 Host: N230WU Kernel: 4.15.0-33-lowlatency Uptime: 3 days, 1 hour, 12 mins Packages: 2921 Shell: bash 4.4.19 Resolution: 1920x1080, 1920x1080 DE: Budgie WM: Mutter(Budgie) Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: tilix CPU: Intel i7-8550U (8) @ 4.000GHz GPU: Intel UHD Graphics 620 Memory: 4168MiB / 15918MiB ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Description changed: Using the night light on both the built-in screen and an external monitor (connected via VGA) in "Join Displays" mode, everything works fine until the screen goes to sleep (aka "blank screen" in "Settings > Power > Power Saving): the night light is still active on the built-in screen but not on the external monitor anymore. I have to unplug and plug back in the VGA for the night light to be restored on the external monitor. Turning the night light on and off does not restore it on the external monitor. + I have checked other bug reports related to night light, but couldn't + find a description of my issue. + gnome-control-center version: 1:3.28.2-0ubuntu0.18.04.2 gnome-shell version: 3.28.3-0ubuntu0.18.04.2 System details: - OS: Ubuntu 18.04.1 LTS x86_64 - Host: N230WU - Kernel: 4.15.0-33-lowlatency - Uptime: 3 days, 1 hour, 12 mins - Packages: 2921 - Shell: bash 4.4.19 - Resolution: 1920x1080, 1920x1080 - DE: Budgie - WM: Mutter(Budgie) - Theme: Adwaita [GTK2/3] - Icons: Adwaita [GTK2/3] - Terminal: tilix - CPU: Intel i7-8550U (8) @ 4.000GHz - GPU: Intel UHD Graphics 620 + OS: Ubuntu 18.04.1 LTS x86_64 + Host: N230WU + Kernel: 4.15.0-33-lowlatency + Uptime: 3 days, 1 hour, 12 mins + Packages: 2921 + Shell: bash 4.4.19 + Resolution: 1920x1080, 1920x1080 + DE: Budgie + WM: Mutter(Budgie) + Theme: Adwaita [GTK2/3] + Icons: Adwaita [GTK2/3] + Terminal: tilix + CPU: Intel i7-8550U (8) @ 4.000GHz + GPU: Intel UHD Graphics 620 Memory: 4168MiB / 15918MiB -- 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/1791659 Title: night light is off on external monitor after screen goes to sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1791659/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1277641] Re: German keyboard layout loses tilde dead key
For anyone affected in 18.04, I have found in "Settings > Language and Region > Input Sources > + > ... > Other" the layout "German (dead tilde)". This fixes my issue, and I wonder if this is the solution previous posters here were hoping for: the default German layout with only the tilde key behaviour modified. -- 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/1277641 Title: German keyboard layout loses tilde dead key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1277641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Hello Markus, or anyone else affected, Accepted console-setup into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/console- setup/1.178ubuntu2.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed verification-failed-bionic ** Tags added: verification-needed verification-needed-bionic -- 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/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
** Changed in: console-setup (Ubuntu Bionic) Status: Confirmed => Fix Committed -- 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/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732411] Re: On upgrade, daemon-reexec should only be issued if safe
Marking the lxc task as invalid since LXC does not drop any such capabilities by default, so such failure isn't lxc's fault. It's either the user's fault (by dropping capabilities that Ubuntu/Debian consider as required) or the systemd's package fault (for not doing a capability check). ** Changed in: lxc (Ubuntu) Status: New => Invalid -- 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/1732411 Title: On upgrade, daemon-reexec should only be issued if safe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1732411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718771] [NEW] Incorrect handling of link-local IPv6 DNS servers
Public bug reported: We've recently seen odd looking DNS failures on autopkgtest: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/d/docker.io/20170921_065231_181b8@/log.gz This shows a fe80:: link-local IPv6 address as one of the DNS servers on the interface. That's because dnsmasq includes both the link-local and global addresses of its DNS server in the router advertisement. systemd-networkd appears to pick that up and send it to resolved, which includes it in its config but apparently doesn't know how to actually query it, leading to the failure above. This is racy because once DHCPv4 completes, the resolved config will then work properly again. I've confirmed that dnsmasq properly answers on all addresses: http://paste.ubuntu.com/25588197/ I've uploaded a workaround for this issue as part of the docker.io package. ** 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/1718771 Title: Incorrect handling of link-local IPv6 DNS servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713149] [NEW] resolv.conf symlink is broken after clean debootstrap
Public bug reported: Reproducer: - debootstrap artful artful Expected: - "chroot artful cat /etc/resolv.conf" doesn't fail. - /etc/resolv.conf is a symlink to something valid in /run Actual: - "chroot artful cat /etc/resolv.conf" gets you "No such file or directory" - /etc/resolv.conf is a symlink to "../run/resolvconf/resolv.conf" - "../run/resolvconf/resolv.conf" is a symlink to "../run/systemd/resolve/stub-resolv.conf" which is an invalid symlink as that points to /run/run/systemd/resolve/stub-resolv.conf" rather than "/run/systemd/resolve/stub-resolv.conf" This causes all LXC image creation to fail, causing autopkgtest to fail (as noticed by the kernel team) and has been causing all images to fail building on the upstream build system for the past two days. root@vm04:~# chroot artful ls -lh /etc/resolv.conf /run/resolvconf/ lrwxrwxrwx 1 root root 29 Aug 25 20:20 /etc/resolv.conf -> ../run/resolvconf/resolv.conf /run/resolvconf/: total 4.0K -rw-r--r-- 1 root root0 Aug 25 20:21 enable-updates drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface lrwxrwxrwx 1 root root 39 Aug 25 20:18 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf root@vm04:~# chroot zesty ls -lh /etc/resolv.conf /run/resolvconf/ lrwxrwxrwx 1 root root 29 Aug 25 20:20 /etc/resolv.conf -> ../run/resolvconf/resolv.conf /run/resolvconf/: total 8.0K -rw-r--r-- 1 root root0 Aug 25 20:20 enable-updates drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface -rw-r--r-- 1 root root 357 Aug 25 20:15 resolv.conf ** Affects: systemd (Ubuntu) Importance: Undecided Status: 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/1713149 Title: resolv.conf symlink is broken after clean debootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1709536] [NEW] snapd 2.26.14 on ubuntu-core won't start in containers anymore
Public bug reported: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). ** Affects: snapd Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: lxd ** 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/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1709536/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
I'm not seeing a compelling reason to switch to 3.24 and the newer vte other than the version bump. If your argument is that after this revert, both gnome-terminal and vte are effectively identical feature-wise as what we have in the archive right now, then you're not introducing or removing features, in which case you don't need a Feature Freeze Exception in the first place. If this change does introduce/remove features to gnome-terminal and vte, please list them in a readable format (not an upstream git log/diff). I think the pcre2 MIR could do with an API diff between pcre3 and pcre2. Your massive patch suggests that the two APIs are very much different and that it's not something we can do as a typical transition, making the need for both of them to live in main together much clearer. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1656024] Re: hostnamectl does not work inside lxd
Looks like the problem is to do with systemd and it failing to spawn units that have: PrivateNetwork=yes I'm not sure exactly what systemd attempts to do which doesn't work in an unprivileged container, but the answer is almost certainly to have it not do that :) Re-assigning bug to systemd. ** Package changed: lxd (Ubuntu) => systemd (Ubuntu) ** Summary changed: - hostnamectl does not work inside lxd + Units using PrivateNetwork=yes don't work inside user namespaces -- 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/1656024 Title: Units using PrivateNetwork=yes don't work inside user namespaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1656024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1577001] Re: Installing lxd leaves /var/lib/lxd/unix.socket with wrong group ownership
Moving over to systemd, our unit is very clear about the expected owner for the socket. The needed group is created in preinst so is guaranteed to be there by the time systemd is poked in postinst. LXD itself doesn't change socket ownership when socket activated and if it did, it would honor the --group option which would have it chown to the right group. ** Package changed: lxd (Ubuntu) => systemd (Ubuntu) -- 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/1577001 Title: Installing lxd leaves /var/lib/lxd/unix.socket with wrong group ownership To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1577001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1576341] Re: fails in lxd container
LXC doesn't drop many capabilities, we only really drop mac_admin, mac_override, sys_time, sys_module and sys_rawio. That's because we do run workloads which do need the other capabilities, including cap_sys_admin. Now in an unprivileged container, having those capabilities will only do you good against resources owned by the container and will (obviously) not let you gain any more rights than you had as the owning uid prior to entering the container. So you absolutely do have cap_sys_admin and it will let you do a bunch of things against the network devices owned by your container or mount entries owned by the container, ... but it will not let you mess with things that aren't namespaced and that you wouldn't be allowed to touch as a normal unprivileged user. The kernel has a nice ns_capable(ns, CAP) function which lets you check whether you do have the named capability against a given resource, I'm not aware of a userspace equivalent though. Having us drop a bunch of capabilities is the wrong answer though and we won't be doing that. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- 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/1576341 Title: fails in lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1540803] [NEW] systemd doesn't respect /etc/fstab for internal mounts
Public bug reported: Under upstart, I can have the following line in my /etc/fstab: tmpfs /run tmpfs defaults,size=10M 0 0 At mount time, mountall will use /etc/fstab as an override for the internal fstab (/lib/init/fstab) and so I end up with /run mounted with a 10MB limit. Under systemd, the exact same fstab appears to be ignored and I end up with a /run that has a limit of half my memory. This may very well surprise users upgrading production environments from 14.04 to 16.04 or users that have to follow some strict partitioning and mount configuration policies (we've seen a couple of those by now) so it'd be good to have this resolved. I did testing with /run in LXD containers on 14.04 (upstart) and 16.04 (systemd). ** 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/1540803 Title: systemd doesn't respect /etc/fstab for internal mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1540803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.
As a reminder: - http://lists.freedesktop.org/archives/systemd-devel/2015-January/027246.html - http://lists.freedesktop.org/archives/systemd-devel/2015-January/027323.html http://cgit.freedesktop.org/systemd/systemd/commit/?id=874d3404cbf2363604106c8f86683db4082691ea The code change at that point was to ignore all mounts under /dev, /proc and /sys, maybe things changed since and re-introduced the issue somehow, or we missed a code path somewhere. ** No longer affects: lxd (Ubuntu) -- 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/1519499 Title: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown
Thanks, that does indeed seem to point towards a systemd issue, I've added a systemd task, Martin should be able to pick things up from there. Can you also tell us what version of the kernel you're using? We've seen some weird behavior with systemd on some specific kernel releases in the past. Also, does "journalctl" in the container after attempting a shutdown print any useful information or error messages? Thanks! ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: lxd (Ubuntu) Status: Incomplete => Triaged -- 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/1519499 Title: [systemd] SIGPWR doesn't always lead to shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1477130] Re: timedatectl fails inside container
Seems to work fine here: root@ubuntu:~# timedatectl Local time: Mon 2015-11-09 18:33:40 UTC Universal time: Mon 2015-11-09 18:33:40 UTC RTC time: n/a Time zone: Etc/UTC (UTC, +) Network time on: yes NTP synchronized: yes RTC in local TZ: no That's with a 15.10 container on a 14.04 host. I suspect this was actually a systemd issue where the daemon side of this wasn't starting somehow. ** Package changed: lxc (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/1477130 Title: timedatectl fails inside container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1477130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1500992] [NEW] networkd: Don't reset forwarding unless told to do so in config
Public bug reported: It's been reported by several LXC users that systemd-networkd will turn off per-interface forwarding for all network interfaces when it starts. Presumably upstream expects users to go and manually edit their config to allow it when needed. This breaks LXC, libvirt, ... anything which ships a bridge that then NAT or route outgoing traffic. Requiring the user to do the config change would be a massive regression in user friendliness and having lxc, libvirt, ... do it for the user would be a policy violation. As a result, I'd recommend we patch systemd to not interfere with forwarding unless explicitly configured by the user. This will allow all our existing scripts to keep setting things up themselves and have it all run fine. ** 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/1500992 Title: networkd: Don't reset forwarding unless told to do so in config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1500992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 867749] Re: Permission Denied error when reading a pdf format file whos name doesn't end in .pdf
This also affect Ubuntu 14.04 LTS with evince 3.10.3. Workaround : Modify the Apparmor security profile with these two commands : sudo apt-get install apparmor-utils sudo aa-complain /usr/bin/evince and it should be working -- 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/867749 Title: Permission Denied error when reading a pdf format file whos name doesn't end in .pdf To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/867749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1414544] [NEW] Machine never boots, stuck at network bringup
Public bug reported: root@lantea:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # Physical network interfaces auto eth0 iface eth0 inet manual bond-master bond0 auto eth1 iface eth1 inet manual bond-master bond0 # Bond auto bond0 iface bond0 inet dhcp bond-slaves none bond-mode 802.3ad bond-miimon 100 hwaddress 00:1b:21:2c:0d:4b That's a fairly common bond configuration which works great with upstart but which when booting with systemd will hang at network bringup time. ** 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/1414544 Title: Machine never boots, stuck at network bringup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1414544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314904] Update Released
The verification of the Stable Release Update for shotwell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1314904 Title: Remote publishing does not work in Unity/GNOME/XFCE on trusty/utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1314904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1296275] Update Released
The verification of the Stable Release Update for libgphoto2 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1296275 Title: PTP Cameras not working on 14.04, works flawlessly on 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1296275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1309025] Re: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL
Ok, so after spending some more time on it with Serge, we found and fixed a few problems with the cgmanager patch for systemd-logind. Pretty much each of the fixes could explain what we've been seeing, so hopefully this will be the end of it (combined with the cgmanager fix from Michael Terry which already landed in both utopic and trusty). I'm removing the cgmanager task as I believe this side has now been separately fixed and am tracking these bugfixes for trusty and utopic now. ** Changed in: cgmanager (Ubuntu) Status: Incomplete = Invalid ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cgmanager (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Utopic) Importance: Medium Assignee: Stéphane Graber (stgraber) Status: Confirmed ** Also affects: cgmanager (Ubuntu Utopic) Importance: Medium Status: Invalid ** No longer affects: cgmanager (Ubuntu) ** No longer affects: cgmanager (Ubuntu Trusty) ** No longer affects: cgmanager (Ubuntu Utopic) ** Changed in: systemd (Ubuntu Utopic) Status: Confirmed = In Progress ** Changed in: systemd (Ubuntu Trusty) Status: New = In Progress ** Changed in: systemd (Ubuntu Trusty) Importance: Undecided = High ** Changed in: systemd (Ubuntu Utopic) Importance: Medium = High ** Changed in: systemd (Ubuntu Trusty) Assignee: (unassigned) = Stéphane Graber (stgraber) -- 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/1309025 Title: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1309025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1313250] Re: Shortcut key Ctrl+L no longer sets cursor to page selector in 3.10.3
Hello macho, or anyone else affected, Accepted evince into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/evince/3.10.3-0ubuntu10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- 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/1313250 Title: Shortcut key Ctrl+L no longer sets cursor to page selector in 3.10.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1313250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318581] Re: Tooltips for Next and Previous pages are mixed up
Hello TenLeftFingers, or anyone else affected, Accepted evince into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/evince/3.10.3-0ubuntu10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- 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/1318581 Title: Tooltips for Next and Previous pages are mixed up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1318581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1312179] Re: fit and width hotkeys broken
Hello Krister, or anyone else affected, Accepted evince into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/evince/3.10.3-0ubuntu10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- 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/1312179 Title: fit and width hotkeys broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1312179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1310782] Re: Zoom in shortcut should be =/+, not shift +
Hello Aibara, or anyone else affected, Accepted evince into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/evince/3.10.3-0ubuntu10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- 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/1310782 Title: Zoom in shortcut should be =/+, not shift + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1310782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317179] Re: lxc containers fail to start in trusty with newer kernels
Sorry Martin, I didn't see this bug until after I fixed it... So I added both net_cls and net_prio to utopic (jso we have them all listed just in case), would be great if you could update the git branch to match. I'm also doing the SRU to trusty now. ** Changed in: systemd (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: systemd (Ubuntu Trusty) Assignee: (unassigned) = Stéphane Graber (stgraber) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Stéphane Graber (stgraber) ** Changed in: systemd (Ubuntu Trusty) Status: Triaged = In Progress -- 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/1317179 Title: lxc containers fail to start in trusty with newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1317179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1309025] Re: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL
I don't see anything obviously wrong in the call made by systemd-logind itself, so this may be a problem with cgmanager, adding a task. ** Also affects: cgmanager (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/1309025 Title: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1309025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1307595] [NEW] systemd-logind fails to start in unprivileged containers
Public bug reported: Because of systemd-logind using the limit upstart stanza, it fails to start in unprivileged containers where the ulimit is lower than the requested one. The proposed fix is to call ulimit from the job itself instead and ignore the failure (it'll get logged though in case this ends up causing some issues). ** 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/1307595 Title: systemd-logind fails to start in unprivileged containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1307595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
The stacktrace suggests we are in libcgmanager, so adding a cgmanager task. ** Also affects: cgmanager (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/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301544] Re: cannot boot with latest systemd updates
Moving to cgmanager, cgmanager is supposed to work entirely without /usr, this is a bug and needs fixing ASAP. ** Package changed: systemd (Ubuntu) = cgmanager (Ubuntu) ** Changed in: cgmanager (Ubuntu) Importance: Undecided = Critical ** Changed in: cgmanager (Ubuntu) Status: New = Triaged -- 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/1301544 Title: cannot boot with latest systemd updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1301544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1297363] [NEW] [FFe] Add cgmanager support
Public bug reported: I'd like to add cgmanager support to systemd-logind so that in environment where it doesn't have direct access to the cgroup hierarchy (most notably unprivileged LXC containers), it'll be able to use cgmanager to perform all the operations it needs. This is implemented through a patch directly against our current version of systemd, this isn't upstreamable code as it's a bit hackish and current upstream systemd has now switched logind to using the systemd cgroup API rather than performing direct accesses. The change in question is available at: https://code.launchpad.net/~stgraber/ubuntu/trusty/systemd/logind-cgmanager/+merge/211649 This has been reviewd by Serge Hallyn (author of cgmanager) and Martin Pitt and tested quite a bit here, so I'm pretty confident this will work as intended. For systems that do not ship cgmanager (currently everyone but those using LXC), logind will use the old code path without any change whatsoever, for those with cgmanager installed (detected by the presence of /sys/fs/cgroup/cgmanager/sock), logind will attempt to connect to it and use it. If the connection fails, it'll fallback to using the filesystem directly. I'm sorry for the late FFe, but this was stuck on the security team processing the MIR of cgmanager which took a couple of months... It finally got accepted earlier this week and I'm planning to upload LXC 1.0.2 later this week which will pull it into main, then followed shortly by systemd should this FFe be approved. Landing would happen right after Beta 2 is out. ** 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/1297363 Title: [FFe] Add cgmanager support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1297363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1226962]
Moving to mab4.1 (Bug 60270) because: - 4.0 reached EOL (End Of Life) - bug confirmed in later version -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1238410] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1238410 Title: Inconsistent cursor visibility with cursor plugin enabled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1238410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1198315] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1198315 Title: [network]: gnome-control-center SIGSEGV in append_escaped_text() (invalid utf8 ssid name) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1198315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 805154] Re: gdm-simple-slave crashed with SIGSEGV in _nss_compat_getpwnam_r()
Hello Blümchen, or anyone else affected, Accepted gdm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gdm/3.0.4-0ubuntu15.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gdm (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/805154 Title: gdm-simple-slave crashed with SIGSEGV in _nss_compat_getpwnam_r() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/805154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1241736] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1241736 Title: Wrong menu is being shown if mouse not moved after area selection To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1241736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1000325] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1000325 Title: After unmounting i got error see screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1000325/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1264818] [NEW] Reload file button doesn't show when File explorer is visible
Public bug reported: When the File Explorer pane in visible on the left (F9), the button reload the file is displayed outside of the visible area. This seems to be a display bug. The position of the button seems to be computed without taking into account the width of the File explorer pane, and is displayed outside of the window. Steps to reproduce : - open a text file - display the file explorer (F9) - modify the text file from another source (command line touch myfile.txt) - come back in gedit to see the this file was modified message at the top of the window - It is impossible to reload the file because the button reload is not accessible Workaround : - close the file explorer to see the button (F9) - or use the menu entry ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: Printscreen https://bugs.launchpad.net/bugs/1264818/+attachment/3937258/+files/Capture%20du%202013-12-29%2012%3A30%3A13.png ** Description changed: When the File Explorer pane in visible on the left (F9), the button reload the file is displayed outside of the visible area. This seems to be a display bug. The position of the button seems to be computed without taking into account the width of the File explorer pane, and is displayed outside of the window. Steps to reproduce : - - open a text file - - display the file explorer (F9) - - modify the text file from another source (command line nano or vi) - - come back in gedit to see the this file was modified message at the top of the window - - It is impossible to reload the file because the button reload is not accessible + - open a text file + - display the file explorer (F9) + - modify the text file from another source (command line touch myfile.txt) + - come back in gedit to see the this file was modified message at the top of the window + - It is impossible to reload the file because the button reload is not accessible - Workaround : - - close the file explorer to see the button (F9) - - or use the menu entry + Workaround : + - close the file explorer to see the button (F9) + - or use the menu entry -- 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/1264818 Title: Reload file button doesn't show when File explorer is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1263287] [NEW] gnome-sound-recorder:2846 : GStreamer-WARNING **: Element 'gconfaudiosource' already has parent
Public bug reported: In Ubuntu 13.10, open Sound Recorder from the Dash. It shows : - Record from input Master (no other choice) - Record as : - (empty dropdown, no choice at all) Pressing the record button doesn't start the recording. Impossible to use the application. Launched fromt he terminal, the error displayed when clicking on Recordis the following (from the second click, not the first one) : (gnome-sound-recorder:2846): GStreamer-WARNING **: Element 'gconfaudiosource' already has parent ** Affects: gnome-media (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/1263287 Title: gnome-sound-recorder:2846 : GStreamer-WARNING **: Element 'gconfaudiosource' already has parent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/1263287/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1263287] Re: gnome-sound-recorder:2846 : GStreamer-WARNING **: Element 'gconfaudiosource' already has parent
Possible duplicate of #1203026, I'm not sure. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/1263287 Title: gnome-sound-recorder:2846 : GStreamer-WARNING **: Element 'gconfaudiosource' already has parent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/1263287/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1196523] Re: gedit crashed with SIGSEGV in magazine_chain_pop_head()
Hello Mitsuya, or anyone else affected, Accepted gtk+3.0 into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gtk+3.0/3.8.6-0ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gtk+3.0 (Ubuntu Saucy) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1196523 Title: gedit crashed with SIGSEGV in magazine_chain_pop_head() To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1196523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1235625] Re: fix legacy keygrabber for gnome-ish sessions
Hello Tim, or anyone else affected, Accepted gnome-settings-daemon into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- settings-daemon/3.8.5-0ubuntu11.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-settings-daemon (Ubuntu Saucy) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1235625 Title: fix legacy keygrabber for gnome-ish sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1235625/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859600] Re: Please convert gnome-keyring to multiarch
Hello Riku, or anyone else affected, Accepted gnome-keyring into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- keyring/3.6.1-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-keyring (Ubuntu Quantal) Status: In Progress = Fix Committed ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1094319] Re: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such
Hello Rodney, or anyone else affected, Accepted gnome-keyring into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- keyring/3.6.1-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-keyring (Ubuntu Quantal) Status: In Progress = Fix Committed ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1094319 Title: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome- keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring- pkcs11.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1094319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1198315] Re: [network]: gnome-control-center SIGSEGV in append_escaped_text() (invalid utf8 ssid name)
Hello Cedric, or anyone else affected, Accepted gnome-control-center into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- control-center/1:3.6.3-0ubuntu45.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-control-center (Ubuntu Saucy) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1198315 Title: [network]: gnome-control-center SIGSEGV in append_escaped_text() (invalid utf8 ssid name) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1198315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1198315] Re: [network]: gnome-control-center SIGSEGV in append_escaped_text() (invalid utf8 ssid name)
Hi Sebastien This is what I get when running nmcli dev wifi list: SSID BSSID MODE FREQ RATE SIGNAL SECURITY ACTIVE 'JoinEduroam' 00:25:45:37:1C:40 Infrastructure 2437 MHz 54 MB/s77 -- no 'JoinEduroam' 00:25:45:A3:47:70 Infrastructure 2412 MHz 54 MB/s29 -- no 'eduroam' 00:25:45:37:1C:41 Infrastructure 2437 MHz 54 MB/s100 WPA WPA2 Enterprise no 'Visitor-UQconnect' 00:25:45:A3:49:F2 Infrastructure 2412 MHz 54 MB/s35 -- no 'JoinEduroam' 00:25:45:A3:49:F0 Infrastructure 2412 MHz 54 MB/s35 -- no 'eduroam' 00:25:45:A3:F3:61 Infrastructure 2412 MHz 54 MB/s49 WPA WPA2 Enterprise no 'eduroam' 00:25:45:A3:47:71 Infrastructure 2412 MHz 54 MB/s30 WPA WPA2 Enterprise no 'eduroam' 00:25:45:A3:49:61 Infrastructure 2462 MHz 54 MB/s32 WPA WPA2 Enterprise no 'JoinEduroam' 00:25:45:A3:49:60 Infrastructure 2462 MHz 54 MB/s32 -- no 'Visitor-UQconnect' 00:25:45:A3:F3:62 Infrastructure 2412 MHz 54 MB/s40 -- no 'Visitor-UQconnect' 00:25:45:A3:47:72 Infrastructure 2412 MHz 54 MB/s40 -- no 'JoinEduroam' 00:25:45:A3:F3:60 Infrastructure 2412 MHz 54 MB/s40 -- no 'eduroam' 00:25:45:A3:49:F1 Infrastructure 2412 MHz 54 MB/s54 WPA WPA2 Enterprise yes 'eduroam' 00:25:45:A4:35:91 Infrastructure 2462 MHz 54 MB/s30 WPA WPA2 Enterprise no 'Visitor-UQconnect' 00:25:45:37:1C:42 Infrastructure 2437 MHz 54 MB/s70 -- no 'JoinEduroam' 00:25:45:A4:35:90 Infrastructure 2462 MHz 54 MB/s32 -- no However, something that is not visible here is a network with a weird name in my network list when I go in Network indicator Edit Connections... (see attachment). I just deleted this network and then I could get into System settings... Network without it crashing ! ** Attachment added: Weird network name https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1198315/+attachment/3912952/+files/Selection_085.png -- 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/1198315 Title: [network]: gnome-control-center SIGSEGV in append_escaped_text() (invalid utf8 ssid name) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1198315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1241881] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1241881 Title: gnome-keyring depends on transitional package libgcr-3-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1241881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1225514] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1225514 Title: adding keyboard layouts no longer seems to update xkb correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1225514/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1245874] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1245874 Title: Java JAR files are opened in file-roller instead of Java Runtime (remove application/x-jar=file-roller.desktop from /etc/gnome/defaults.list) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1245874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1236601] Re: wrong background color when editing icons on desktop
Hello Marc, or anyone else affected, Accepted nautilus into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nautilus/1:3.8.2-0ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nautilus (Ubuntu Saucy) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1236601 Title: wrong background color when editing icons on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1236601/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1252099] Re: mouse wheel does not scroll
Does this happen systematically or just when the document is in the background? I noticed too that I can not scroll anymore when the pointer is over the page but evince is not in focus. This works with any other app, and used to work before the last big evince update. -- 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/1252099 Title: mouse wheel does not scroll To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1252099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1252099] Re: mouse wheel does not scroll
OK, I will report another bug. Thanks for the reply! -- 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/1252099 Title: mouse wheel does not scroll To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1252099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1252619] [NEW] Evince does not scroll with mouse wheel when not in focus
Public bug reported: Since a recent Evince update, it is not possible to use the mouse wheel to scroll up and down the document when not in focus. However, it is possible to use the double-finger scroll on the trackpad. This is an extremely useful thing when working with split screen, like when writing text while reading a pdf document. With this bug, the user has to click on the pdf document to be able to scroll, and click back in the text editor to go back to writing. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evince 3.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 19 17:09:09 2013 InstallationDate: Installed on 2013-05-13 (190 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to saucy on 2013-10-26 (24 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1252619 Title: Evince does not scroll with mouse wheel when not in focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1252619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
** Tags added: verification-done-precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/580961/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1198315] Re: [network]: gnome-control-center crashed with SIGSEGV in append_escaped_text()
How are people affected by this? For me: Gnome control center (System settings) crashes systematically shortly after opening the Network settings, making it impossible to configure anything network-related, at least through the GUI. Is that the right bug? -- 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/1198315 Title: [network]: gnome-control-center crashed with SIGSEGV in append_escaped_text() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1198315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1229022] Re: Gnome control center crashes when opening network settings
*** This bug is a duplicate of bug 1198315 *** https://bugs.launchpad.net/bugs/1198315 Great, cheers for that. -- 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/1229022 Title: Gnome control center crashes when opening network settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1229022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1229022] Re: Gnome control center crashes when opening network settings
Here is my list of error reports: 2a09b0ac-45f9-11e3-9183-2c768aafd08c 2e47eb70-448c-11e3-a9d3-e4115b0f8a4a 31173fc6-3295-11e3-bdac-2c768aafd08c 3964f75e-2fed-11e3-9052-e4115b0f8a4a 41c2d2ae-2fed-11e3-bf02-e4115b0f8a4a 6af778a8-447b-11e3-8345-e4115b0f8a4a c831ad78-41eb-11e3-9b3e-e4115b0f8a4a d04c27b4-4668-11e3-ab8e-2c768aafd08c dcaea13e-453d-11e3-a182-2c768aafd08c e080cb0a-41ca-11e3-8a92-e4115b0f8a4a e2fe5b04-41ca-11e3-a675-e4115b0f8a4a I am not sure which one is the right one, sorry. Cheers -- 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/1229022 Title: Gnome control center crashes when opening network settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1229022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246265] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1246265 Title: Empathy won't show contacts for Facebook, AIM. To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1246265/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1209092] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1209092 Title: network : gnome-control-center crashed with SIGABRT in g_assertion_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1209092/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1229022] Re: Gnome control center crashes when opening network settings
I can access the reports, but clicking on them does not bring me to any description as I am told I don't have the rights to do so (on errors.ubuntu.com). -- 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/1229022 Title: Gnome control center crashes when opening network settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1229022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1238266] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1238266 Title: Error setting owner: Operation not permitted when extracting Eclipse in saucy To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1238266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
Hello Christopher, or anyone else affected, Accepted gnome-settings-daemon into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- settings-daemon/3.4.2-0ubuntu0.6.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-settings-daemon (Ubuntu Precise) Status: New = Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed ** Changed in: xkeyboard-config (Ubuntu Precise) Status: New = Fix Committed -- 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/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Please test proposed package
Hello Christopher, or anyone else affected, Accepted xkeyboard-config into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/xkeyboard- config/2.5-1ubuntu1.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1229022] Re: Gnome control center crashes when opening network settings
I still have this problem after updating to 13.10. -- 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/1229022 Title: Gnome control center crashes when opening network settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1229022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1229022] Re: Gnome control center crashes when opening network settings
I changed the status to incomplete as it was previously invalid. which definition is not applicable here: Not a bug. May be a support request or spam. ** Changed in: gnome-control-center (Ubuntu) Status: Invalid = Incomplete -- 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/1229022 Title: Gnome control center crashes when opening network settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1229022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1227173] Re: On every startup Onboard asks for enabling accessibility
** Changed in: onboard (Ubuntu) Milestone: ubuntu-13.10 = saucy-updates ** Changed in: gnome-settings-daemon (Ubuntu) Milestone: ubuntu-13.10 = saucy-updates -- 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/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1180721] Re: replaygain crashing on second play
** Changed in: rhythmbox (Ubuntu) Milestone: ubuntu-13.10 = saucy-updates -- 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/1180721 Title: replaygain crashing on second play To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1180721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1234392] Re: gnome-control-center on precise crashes when the network panel is closed
Hello errors.ubuntu.com, or anyone else affected, Accepted gnome-control-center into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- control-center/1:3.4.2-0ubuntu0.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- 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/1234392 Title: gnome-control-center on precise crashes when the network panel is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1234392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1234392] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1234392 Title: gnome-control-center on precise crashes when the network panel is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1234392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1229022] Re: Gnome control center crashes when opening network settings
I don't understand what a stack trace is, but here is what is in var/crash. Does this help? ** Attachment added: _usr_bin_gnome-control-center.1000.crash https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1229022/+attachment/3880764/+files/_usr_bin_gnome-control-center.1000.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/1229022 Title: Gnome control center crashes when opening network settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1229022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
Hello Jeff, or anyone else affected, Accepted upower into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/upower/0.9.20-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: upower (Ubuntu Raring) Status: Confirmed = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
Hello Jeff, or anyone else affected, Accepted upower into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/upower/0.9.15-3git1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: upower (Ubuntu Precise) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1229022] Re: Gnome control center crashes when opening network settings
I mean, it does not bring me to a new bug report through the browser, I am not sure why. -- 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/1229022 Title: Gnome control center crashes when opening network settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1229022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1229022] Re: Gnome control center crashes when opening network settings
I did tell apport to send an error report to help fix this problem several time, and just did it again from the same file I attached just then. Where do those error reports go? Cheers -- 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/1229022 Title: Gnome control center crashes when opening network settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1229022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1215980] Re: [FFe] Freeze exception for converged indicators
Closing this FFe since we're now doing final image generation and that any change affecting binary packages on any of our released images is now forbidden (unless it's a critical bugfix). ** Changed in: indicator-bluetooth (Ubuntu) Status: Confirmed = Fix Released ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1215980 Title: [FFe] Freeze exception for converged indicators To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1215980/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219777] Re: [FFe] update to 0.15
** Changed in: shotwell (Ubuntu) Status: Fix Committed = Fix Released -- 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/1219777 Title: [FFe] update to 0.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1219777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
