[Bug 1765598] [NEW] package apache2 2.4.18-2ubuntu3.5 failed to install/upgrade: trying to overwrite '/var/www/html', which is also in package nginx-common 1.10.3-0ubuntu0.16.04.2
Public bug reported: i don't know anything ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apache2 2.4.18-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 Apache2ConfdDirListing: False ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Apr 20 11:08:10 2018 DuplicateSignature: package:apache2:2.4.18-2ubuntu3.5 Unpacking apache2 (2.4.18-2ubuntu3.8) over (2.4.18-2ubuntu3.5) ... dpkg: error processing archive /var/cache/apt/archives/apache2_2.4.18-2ubuntu3.8_amd64.deb (--unpack): trying to overwrite '/var/www/html', which is also in package nginx-common 1.10.3-0ubuntu0.16.04.2 ErrorMessage: trying to overwrite '/var/www/html', which is also in package nginx-common 1.10.3-0ubuntu0.16.04.2 InstallationDate: Installed on 2018-03-19 (31 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: apache2 Title: package apache2 2.4.18-2ubuntu3.5 failed to install/upgrade: trying to overwrite '/var/www/html', which is also in package nginx-common 1.10.3-0ubuntu0.16.04.2 UpgradeStatus: No upgrade log present (probably fresh install) error.log: modified.conffile..etc.apache2.apache2.conf: [modified] mtime.conffile..etc.apache2.apache2.conf: 2018-04-19T17:48:42.077186 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765598 Title: package apache2 2.4.18-2ubuntu3.5 failed to install/upgrade: trying to overwrite '/var/www/html', which is also in package nginx-common 1.10.3-0ubuntu0.16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1765598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
** Changed in: gstreamer-vaapi (Ubuntu) Status: Confirmed => In Progress ** Also affects: clutter-gst-3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: clutter-gst-3.0 (Ubuntu) Status: New => In Progress ** Changed in: clutter-gst-3.0 (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1698270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763266] Re: Snapd fails to start (failed to parse /proc/self/mountinfo)
I think this is still a TODO for me mvo. I fixed fstab without touching mountinfo IIRC. I will address this today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763266 Title: Snapd fails to start (failed to parse /proc/self/mountinfo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1763266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717449] Re: Titlebar height changes as buttons are added/removed
I think this was fixed in 18.04 recently, probably by: https://launchpad.net/ubuntu/+source/ubuntu-themes/16.10+18.04.20180328-0ubuntu1 ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717449 Title: Titlebar height changes as buttons are added/removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756950] Re: package mariadb-server-10.1 1:10.1.29-6 failed to install/upgrade: installed mariadb-server-10.1 package post-installation script subprocess returned error exit status 1
i was having it before but upgraded my ubuntu to 18 and now even after i purge the package it still is not installing agian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756950 Title: package mariadb-server-10.1 1:10.1.29-6 failed to install/upgrade: installed mariadb-server-10.1 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1756950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765593] [NEW] Cannot start synaptic from Ubuntu-dock
Public bug reported: To reproduce the bug: - click the Synaptic icon in Ubuntu-dock - when Synaptic starts click cancel - click the Synaptic icon in Ubuntu-dock Synaptic will not start It's possible to start Synaptic from the terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Apr 20 07:08:47 2018 InstallationDate: Installed on 2018-04-01 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765593 Title: Cannot start synaptic from Ubuntu-dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1765593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765592] Re: remmina crashed with SIGSEGV in gtk_widget_get_preferred_width()
*** This bug is a duplicate of bug 1754114 *** https://bugs.launchpad.net/bugs/1754114 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754114, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1765592/+attachment/5123264/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765592/+attachment/5123266/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765592/+attachment/5123270/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765592/+attachment/5123271/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765592/+attachment/5123272/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765592/+attachment/5123273/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765592/+attachment/5123274/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1754114 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765592 Title: remmina crashed with SIGSEGV in gtk_widget_get_preferred_width() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1765592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765083] Re: Please cherrypick s390 unwind fix
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765083 Title: Please cherrypick s390 unwind fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1765083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765591] Re: WebKitPluginProcess crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1736281 *** https://bugs.launchpad.net/bugs/1736281 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1736281, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1765591/+attachment/5123254/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765591/+attachment/5123256/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765591/+attachment/5123259/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765591/+attachment/5123260/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765591/+attachment/5123261/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765591/+attachment/5123262/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765591/+attachment/5123263/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1736281 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765591 Title: WebKitPluginProcess crashed with SIGSEGV in ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1765591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
I tried restarting thermald (1.7.0-5) at least 10 times, and the system always see the same broken sensor, the same as in 1.7.0-4 and the same as in 1.7.0-6. Perhaps by luck (or perhaps because some library or compiler version difference) thermald 1.7.0-5 worked fine on my 18.04 setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764355] Re: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login
This bug was fixed in the package xorg - 1:7.7+19ubuntu7 --- xorg (1:7.7+19ubuntu7) bionic; urgency=medium [ Simon Quigley ] * 60x11-common_xdg_path: If $XDG_CONFIG_DIRS is nonempty, don't discard the contents. [ Didier Roche ] * 60x11-common_xdg_path: - protect against multiple additions of the same paths to XDG_CONFIG_DIRS and XDG_DATA_DIRS, resulting to duplication on consecutive logout/logins due to older session hanging in and env being reused. Some consequences is that electron application crashes (LP: #1764355) - remove readdition of defaults if XDG_CONFIG_DIRS isn't empty to respect user's selection (same logic than wayland session). -- Timo AaltonenThu, 19 Apr 2018 17:47:42 +0300 ** Changed in: xorg (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764355 Title: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1764355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765587] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1765587/+attachment/5123228/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765587/+attachment/5123230/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765587/+attachment/5123234/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765587/+attachment/5123235/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765587/+attachment/5123236/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765587/+attachment/5123237/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765587/+attachment/5123238/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765587 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1505368] Re: Bug reports after segmentation fault are never generated
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1505368 Title: Bug reports after segmentation fault are never generated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1505368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697093] Re: Black Screen after boot.
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697093 Title: Black Screen after boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1697093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697786] Re: Graphic drivers may cause problem with booting
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697786 Title: Graphic drivers may cause problem with booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1697786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749675] Re: gnome-shell crashes randomly
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749675 Title: gnome-shell crashes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762175] Re: keep java-common pointing to OpenJDK in -proposed
The attachment "octave-configure-java11.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762175 Title: keep java-common pointing to OpenJDK in -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1762175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
Ok but then you'd need to add/address gnome-software, software- properties-gtk, synaptic, gnome-disk-utility, ect. as any & all of them will cause/experience the same issue, sans a segfault. As soon as 1 app that calls a pkexec auth dialog is canceled then no other app can use pkexec auth until gnome-shell is restarted. As mentioned this does not happen in prior version of gnome-shell. None of the other apps 'crash', they can however get an unresponsive window or in the case of gnome-software (ubuntu-software) it'll just endlessly show installing. There's half a dozen test cases to see this that don't involve g-c-c at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765564] Re: fsnotify: Fix fsnotify_mark_connector race
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765564 Title: fsnotify: Fix fsnotify_mark_connector race To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1765564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717449] Re: Titlebar height changes as buttons are added/removed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717449 Title: Titlebar height changes as buttons are added/removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support
I solved the problem for my with "apt purge nux-tools" ** Summary changed: - LLVMpipe renderer used instead of Intel on Xorg sessions + LLVMpipe renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support ** Summary changed: - LLVMpipe renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support + LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755097 Title: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions
So, after investigating this problem, I finally saw the cause: under X.org, the environment variable LIBGL_ALWAYS_SOFTWARE is set to 1 *always*. Without it, it uses the intel driver as usual: $ LIBGL_ALWAYS_SOFTWARE=0 glxinfo | grep -i opengl OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.0-rc5 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 18.0.0-rc5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.0.0-rc5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: This is probably because I have an old unity file that's running when my session starts (/etc/X11/Xsession.d/50_check_unity_support) with these contents: # This file is sourced by Xsession(5), not executed. # If the hardware does not pass unity_support_test, fall back to LLVMpipe # which does. if [ "x$DESKTOP_SESSION" = "xubuntu" ]; then /usr/lib/nux/unity_support_test || export LIBGL_ALWAYS_SOFTWARE=1 fi And given that the file /usr/lib/nux/unity_support_test doesn't exist anymore, it always exports the variable. I think that there is still a bug here, and some possible fixes: a) Remove the offending file when unity is removed b) Fix the condition to check if unity_support_test exists c) Be sure that ubuntu-bug reports the status of the flag for mesa bugs d) Make that glxinfo prominently warns that the current env forces it to run in software mode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755097 Title: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions
For the record: $ dpkg -S /etc/X11/Xsession.d/50_check_unity_support nux-tools: /etc/X11/Xsession.d/50_check_unity_support $ apt rdepends --installed unity unity Reverse Depends: Breaks: ubuntu-session (<< 7.5.0+17.10.20170619) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755097 Title: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
The trigger may be in gnome-shell, but it would be poor engineering to declare a crash in one process as fixed by modifying another. So any proper fix should also include changes to gnome-control-center to ensure crashing is impossible (even with a faulty gnome-shell). ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765582] Re: vlc crashed with SIGSEGV in mdns_init()
*** This bug is a duplicate of bug 1763771 *** https://bugs.launchpad.net/bugs/1763771 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1763771, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1765582/+attachment/5123212/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765582/+attachment/5123214/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765582/+attachment/5123217/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765582/+attachment/5123218/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765582/+attachment/5123219/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765582/+attachment/5123221/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765582/+attachment/5123222/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1763771 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765582 Title: vlc crashed with SIGSEGV in mdns_init() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1765582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
Not sure why gnome-shell was removed as clearly that's were the issue is. G-c-c may be the only apt actually crashing but this affects any apt that calls a pkexec Auth dialog. Easy examples are software & updates > change something, cancel the auth dialog or synaptic > cancel on the auth. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default
Test PPA is available at $ sudo add-apt-repository ppa:ci-train-ppa- service/3243 ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765173 Title: networkd waits 10 seconds for ipv6 network discovery by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1765173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5
** Attachment added: "test script reproducing the bug on non-patched kernels." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+attachment/5123211/+files/test.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746474 Title: unregister_netdevice: waiting for eth0 to become free. Usage count = 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5
for your records I've added the test script i use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746474 Title: unregister_netdevice: waiting for eth0 to become free. Usage count = 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765563] Re: gegl: CVE-2018-10114 (ppm)
** Changed in: gegl (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765563 Title: gegl: CVE-2018-10114 (ppm) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gegl/+bug/1765563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions
Sorry, I was wrong. It seems the bug is in GTK's titlebar logic. For Xorg sessions that's only used in "modern" apps with the thick headerbar. For Wayland sessions, that's used in all apps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5
the problem also doesn't occur on the Artful test kernel. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746474 Title: unregister_netdevice: waiting for eth0 to become free. Usage count = 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756870] Re: [MIR] socat
I reviewed socat version 1.7.3.2-2build1 as checked into Bionic. This shouldn't be considered a full security audit but rather a quick gauge of reliability. socat is all-purpose fd / socket / pipe manipulator tool. It's either a very deft way to quickly and easily solve a problem or a very high-powered footgun. Proper programmatic use of socat looks *extremely* difficult due to magic environment variables, easy ability to execute other programs, and general flexibility. There are six CVEs against socat currently in our database; some of these might legitimately have been deemed "not a security issue" due to threat models but were handled all the same. One particularly embarrassing CVE included a composite DH parameter. The faulty parameter was available for roughly a year. This incident served as a reminder to the wider community that open source software is vulnerable to malicious contributions the same as proprietary products; I'm glad the socat team were honest. - Build-Depends: debhelper, libssl-dev, libwrap0-dev - Offers cryptography - Does not daemonize (daemon.sh shell script just backgrounds the task from the shell) - Listens to nearly every networking protocol, interface, etc - No pre/post inst/rm scripts - No init scripts - No systemd unit files - No dbus services - No setuid files - socat, procan, and filan programs in PATH - No sudo fragments - No udev rules - There's tests but not run as part of the package build, unknown value - No cron jobs - Some deprecation warnings in the build logs - Subprocesses are spawned, driven by command line parameters if they go through system() or execve() (SYSTEM: and EXEC: methods) - Some memory management was careful, some was 80s-style use of static-sized buffers and "knowing" that inputs won't overflow these buffers. The few cases of unsafe buffer use that I chased down all had static strings as inputs, and thus looked safe. But several CVEs address this very issue. - Files are written too, driven by command line parameters - Logging is extensive, including strace-style wrappers around every system call and library function used. Can also log through syslog. - Extensive environment variable manipulation and use. The manpage describes the full range of environment variables and how they are used. The few that I inspected looked safe. Applications that use socat without being aware of environment use will probably have security vulnerabilities. - Extensive use of ioctls, fchown, chroot, setgroups, setgid, setuid, chmod, chown; some driven by command line options (so calling programs MUST NOT allow unauthenticated unsanitized input here) - Extensive use of cryptography -- can be configured to ignore or perform certificate validation, fake results, etc. - Extensive networking - Code that drops privileges looked careful - No temporary files - No WebKit - No JavaScript - No PolicyKit - cppcheck reports real bugs but most would kill the build, though socat is difficult choice. Its utility is obvious, and I've used it dozens of times to solve little problems over the years. But so much of the code relies upon being perfect C programmers for safety rather than using defensive coding styles. (Very few routines that work on memory buffers take the buffer size as a parameter, for example.) And the collection of #ifdefs to work on dozens of no-longer-mainstream OSes certainly complicate reading and understanding the code. (Which is why cppcheck reports many configurations that can't possibly compile.) Any program that uses socat MUST be very careful. It's got a much larger attack surface than e.g. nc. If nc can solve a problem as well as socat, then nc should be preferred. But socat can handle millions of cases that netcat cannot handle. Some tips for application authors: - Do not allow dynamic input to be used as command line arguments - Do not allow dynamic input to be used as environment variables Trying to sanitize dynamic inputs for these uses would be challenging. Security team ACK for promoting socat to main. This looked like a bug: - xiosetsockaddrenv() is the strcpy() here intentional: case PF_INET6: strcpy(namebuff, lr); Thanks ** Changed in: socat (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756870 Title: [MIR] socat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/socat/+bug/1756870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default
** Description changed: + [Impact] + + * On ipv6 less hosts, boot stalls for 10s + * This is due to implicit RA being on, and wait-online awaiting for RA to timeout + * Expectation is, that since explicit request for RA was not done, it should not block network-online.target, whilst all other aspects of network-online.target should be honored. + + [Test Case] + + * lxc network set lxdbr0 ipv6.address none + * lxc launch ubuntu-daily:bionic lp1765173 + * sleep 20 && lxc exec lp1765173 systemd-analyze blame | head + + Bad result is: + 12.157s systemd-networkd-wait-online.service + Good result is: + less than 3s + + [Regression Potential] + + * If explicit IPv6 dhcp/ra was enabled in .network file, the boot will + be blocked awaiting RA response + + * Only kernel implicit RA configuration will now become "async" + + * This is inline with behaviour of xenial systems + + [Other Info] + + * Original bug report + 1. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. $ apt-cache policy systemd systemd: - Installed: 237-3ubuntu8 - Candidate: 237-3ubuntu8 - Version table: - *** 237-3ubuntu8 500 - 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 237-3ubuntu8 + Candidate: 237-3ubuntu8 + Version table: + *** 237-3ubuntu8 500 + 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 100 /var/lib/dpkg/status 3. systemd-networkd-wait-online doesn't block for 10 seconds waiting on an IPV6 Router Advertisement 4. systemd-networkd sends at least two RA solicitation packets waiting for a response before setting the link to configured. This blocks the boot for every Ubuntu system where it does not have a IPV6 router responding to solicitations. THis includes bionic containers, cloud instances, vms and physical machines. -- We can see that we're spending 13 seconds waiting for networkd to say the network is up. % systemd-analyze blame - 13.326s systemd-networkd-wait-online.service -999ms cloud-init-local.service -954ms cloud-init.service -887ms cloud-config.service -749ms dev-vda1.device -666ms cloud-final.service -248ms keyboard-setup.service -175ms systemd-udev-trigger.service -171ms lxd-containers.service -165ms snapd.service -154ms apparmor.service -147ms ssh.service -144ms systemd-timesyncd.service -133ms grub-common.service -130ms systemd-journald.service -130ms accounts-daemon.service - 99ms systemd-modules-load.service - 98ms systemd-resolved.service - 94ms apport.service - 92ms rsyslog.service - 88ms systemd-logind.service - 80ms lvm2-monitor.service - 75ms iscsid.service - 64ms ebtables.service - 62ms user@1000.service - 54ms dev-mqueue.mount - 53ms ufw.service - 52ms systemd-remount-fs.service - 52ms kmod-static-nodes.service - 34ms systemd-journal-flush.service - 34ms polkit.service - 32ms systemd-tmpfiles-setup-dev.service - 27ms systemd-udevd.service - 26ms systemd-networkd.service - 26ms systemd-sysctl.service - 25ms systemd-tmpfiles-setup.service - 21ms dev-hugepages.mount - 17ms sys-kernel-debug.mount - 16ms console-setup.service - 15ms plymouth-read-write.service - 15ms snapd.socket - 15ms plymouth-quit.service - 14ms systemd-update-utmp.service - 10ms systemd-user-sessions.service - 9ms boot-efi.mount - 8ms sys-fs-fuse-connections.mount - 8ms systemd-update-utmp-runlevel.service - 8ms lxd.socket - 7ms blk-availability.service - 5ms systemd-random-seed.service - 3ms setvtrgb.service - 3ms plymouth-quit-wait.service - 3ms sys-kernel-config.mount - + 13.326s systemd-networkd-wait-online.service + 999ms cloud-init-local.service + 954ms cloud-init.service + 887ms cloud-config.service + 749ms dev-vda1.device + 666ms cloud-final.service + 248ms keyboard-setup.service + 175ms systemd-udev-trigger.service + 171ms lxd-containers.service + 165ms snapd.service + 154ms apparmor.service + 147ms ssh.service + 144ms systemd-timesyncd.service + 133ms grub-common.service + 130ms systemd-journald.service + 130ms accounts-daemon.service + 99ms
[Bug 1761430] Re: linux: 3.13.0-145.194 -proposed tracker
Mark this task as "Fix-released", the replacement is not ready yet. ** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => Fix Released ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761430 Title: linux: 3.13.0-145.194 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763688] Re: linux-lts-xenial: 4.4.0-121.145~14.04.1 -proposed tracker
4.4.0-121.145~14.04.1 - generic Regression test CMPL. Issue to note in amd64: ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_kvm_unit_tests - 27 failed on amaura, 26 failed on pepe (one extra failure due to test case changes) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376) ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build (bug 1699987) ubuntu_qrt_kernel_security - 050 failed (bug 1684776) Issue to note in i386: ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_kvm_unit_tests - failed to build (bug 1765366) MISSING RESULT FROM POWER8 - testing node out-of-order Mark this task as "Fix-released", the replacement is not ready yet. ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763688 Title: linux-lts-xenial: 4.4.0-121.145~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1763688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
** Tags added: artful bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1435093] Re: terminal transparency numix
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1435093 Title: terminal transparency numix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1435093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311546] Re: transparent background doesn't work correctly
*** This bug is a duplicate of bug 561370 *** https://bugs.launchpad.net/bugs/561370 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 561370, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 561370 gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311546 Title: transparent background doesn't work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1311546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518755] Re: broken shadows with transparent background
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518755 Title: broken shadows with transparent background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1518755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315025] Re: gnome-terminal transparency works only when dialog appears.
*** This bug is a duplicate of bug 561370 *** https://bugs.launchpad.net/bugs/561370 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 561370, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 561370 gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315025 Title: gnome-terminal transparency works only when dialog appears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1315025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561370] Re: gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers)
Confirmed in Ubuntu 18.04. In fact it's been broken for so long that I think most of us forgot it used to be transparent. But you can still see the transparency flicker in and out sometimes. ** Tags added: bionic ** Tags added: visual-quality ** Summary changed: - gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers) + gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency) ** Changed in: gnome-terminal (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561370 Title: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/561370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322062] Re: Terminal transparent backgound don`t work
*** This bug is a duplicate of bug 561370 *** https://bugs.launchpad.net/bugs/561370 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 561370, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 561370 gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322062 Title: Terminal transparent backgound don`t work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1322062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477182] Re: Transparency failing gnome-terminal
*** This bug is a duplicate of bug 561370 *** https://bugs.launchpad.net/bugs/561370 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 561370, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 561370 gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477182 Title: Transparency failing gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1477182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561370] Re: gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561370 Title: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/561370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561370] Re: gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers)
** Summary changed: - gnome-terminal transparency no longer works in lucid + gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561370 Title: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/561370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
I re-confirm this. Stock 18.04 has no graphics in pure nvidia mode (on a Thinkpad W520 in discrete graphics). lightdm works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754058] Re: blinking background in gnome-terminal
*** This bug is a duplicate of bug 561370 *** https://bugs.launchpad.net/bugs/561370 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 561370, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 561370 gnome-terminal transparency no longer works reliably (often opaque, but sometimes flickers) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754058 Title: blinking background in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1754058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]
In light of comment #51 above, I shall pursue uploading a udev-udeb with modprobe.d config snippet that forces scsi_mod.scan=sync. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-18.04 ** Changed in: debian-installer (Ubuntu) Milestone: later => ubuntu-18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751813 Title: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765570] Re: libcommons-lang3-java causes NullPointer in surefire/javadoc
** Changed in: libcommons-lang3-java (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765570 Title: libcommons-lang3-java causes NullPointer in surefire/javadoc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcommons-lang3-java/+bug/1765570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default
in summary the consensus is as follows: - cloud-init should not provide accept-ra key to netplan.io - netplan.io should not emit any accept-ra keys to networkd - networkd, when not receiving any accept-ra keys should use kernel implicit default - networkd, when in implicit RA mode, should not block on getting RA as a pre-condition for a link to become ready I believe cloud-init & netplan.io portions are done already. ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released ** Changed in: netplan.io (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765173 Title: networkd waits 10 seconds for ipv6 network discovery by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1765173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759939] Re: Nautilus Rubbish Bin doesn't show deleted items from network mount
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759939 Title: Nautilus Rubbish Bin doesn't show deleted items from network mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1759939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765570] Re: libcommons-lang3-java causes NullPointer in surefire/javadoc
This patch allows libcommons-lang3-java to be build with openjdk-10 by overriding and disabling tests, docs, and doc package install. It also applies 2 required patches to fix: 1) a NullPointerException when the resulting binaries are run with openjdk-10 2) a missing 3 area code locale support After applying this patch surefire can be rebuild and - after that - the build/test/install overrides from this patch can be removed in order to finally rebuild libcommons-lang3-java. ** Patch added: "libcommons-lang3-java_3.5-2_debdiff_3.5-2ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/libcommons-lang3-java/+bug/1765570/+attachment/5123209/+files/libcommons-lang3-java_3.5-2_debdiff_3.5-2ubuntu1.patch ** Tags added: patch ** Bug watch added: Debian Bug tracker #895234 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895234 ** Also affects: libcommons-lang3-java (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895234 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765570 Title: libcommons-lang3-java causes NullPointer in surefire/javadoc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcommons-lang3-java/+bug/1765570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
Confirmed fixed in Debian 1.7.0-6 (amd64 from incoming). Thanks, Colin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765463] Re: Bionic: systemd: rename interface
/etc/systemd/netword/uplink0.link that's invalid path, no? /etc/systemd/network/ is the right path, and should work. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765463 Title: Bionic: systemd: rename interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757573] Re: [CNL-Y] enable kernel support of graphics
File a bug in freedesktop, maybe they could provide some hints. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757573 Title: [CNL-Y] enable kernel support of graphics To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1757573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747296] Re: torbrowser-launcher fails after browser update
Why do we not upgrade this package to a version where this bug does not appear as it makes Tor for me unusable? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747296 Title: torbrowser-launcher fails after browser update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1747296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741978] Re: Add support for ARM events
The patches tracked in this bug are already fix-committed for xenial and artful, we need those packages rebuilt with --enable-arm in debian/rules. Bionic already has these patches and the package for bionic needs to be rebuilt with --enable-arm in debian/rules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741978 Title: Add support for ARM events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765110] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1765110 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765110 Title: [regression] login screen frozen after kernel update 4.13.0-38-generic (but 4.13.0-37-generic works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724105] Re: Privacy : Deactivating screen lock doesn't work
If you still experience screen freezes and have to reboot, please try this: 1. Apply the workaround from bug 994921. 2. After the problem happens next time, reboot and look for files in /var/crash. 3. If you find any crash files then run: ubuntu-bug /var/crash/YOURFILE.crash 4. Tell us here the ID(s) of new bugs created. ** Changed in: gdm3 (Ubuntu) Status: Triaged => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724105 Title: Privacy : Deactivating screen lock doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741978] Re: Add support for ARM events
--- xenial --- debian/rules needs --enable-arm to enable arm events. I have a test build of the rasdaemon package in ppa:centriq-team/lp1741978-rasdaemon. I tested this on an ARM64 system and confirmed with QTI that the output is as expected. The patches tracked in this bug are already fix-committed for xenial. ubuntu@boomer:~$ sudo service rasdaemon status sudo: unable to resolve host boomer ● rasdaemon.service - RAS daemon to log the RAS events Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset Active: active (running) since Fri 2018-04-20 01:57:04 UTC; 7s ago Main PID: 6391 (rasdaemon) Tasks: 1 Memory: 9.3M CPU: 62ms CGroup: /system.slice/rasdaemon.service └─6391 /usr/sbin/rasdaemon -f -r Apr 20 01:57:04 boomer rasdaemon[6391]: Enabled event ras:arm_event Apr 20 01:57:04 boomer rasdaemon[6391]: Can't parse /proc/cpuinfo: missing [vend Apr 20 01:57:04 boomer rasdaemon[6391]: Can't register mce handler Apr 20 01:57:04 boomer rasdaemon[6391]: Can't get traces from ras:aer_event Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Listening to events for cpus Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording mc_event events Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording aer_event events Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording extlog_event events Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording mce_record events Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording arm_event events ubuntu@boomer:~$ grep rasdaemon /var/log/syslog Apr 20 01:57:04 boomer rasdaemon: ras:mc_event event enabled Apr 20 01:57:04 boomer rasdaemon: ras:mc_event event enabled Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: ras:mc_event event enabled Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Enabled event ras:mc_event Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: ras:aer_event event enabled Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Enabled event ras:aer_event Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: ras:arm_event event enabled Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Enabled event ras:arm_event Apr 20 01:57:04 boomer rasdaemon[6392]: rasdaemon: ras:mc_event event enabled Apr 20 01:57:04 boomer rasdaemon[6392]: rasdaemon: ras:aer_event event enabled Apr 20 01:57:04 boomer rasdaemon[6392]: rasdaemon: Can't write to set_event Apr 20 01:57:04 boomer rasdaemon[6392]: rasdaemon: Can't write to set_event Apr 20 01:57:04 boomer rasdaemon[6392]: rasdaemon: ras:arm_event event enabled Apr 20 01:57:04 boomer rasdaemon: Enabled event ras:mc_event Apr 20 01:57:04 boomer rasdaemon: ras:aer_event event enabled Apr 20 01:57:04 boomer rasdaemon: Can't write to set_event Apr 20 01:57:04 boomer rasdaemon: Can't write to set_event Apr 20 01:57:04 boomer rasdaemon: ras:aer_event event enabled Apr 20 01:57:04 boomer rasdaemon: Enabled event ras:aer_event Apr 20 01:57:04 boomer rasdaemon: ras:arm_event event enabled Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags] Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Can't register mce handler Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Can't get ras:extlog_mem_event traces. Perhaps this feature is not supported on your system. Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Can't get traces from ras:aer_event Apr 20 01:57:04 boomer rasdaemon: ras:arm_event event enabled Apr 20 01:57:04 boomer rasdaemon: Enabled event ras:arm_event Apr 20 01:57:04 boomer rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags] Apr 20 01:57:04 boomer rasdaemon: Can't register mce handler Apr 20 01:57:04 boomer rasdaemon: Can't get traces from ras:aer_event Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Listening to events for cpus 0 to 223 Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording mc_event events Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording aer_event events Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording extlog_event events Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording mce_record events Apr 20 01:57:04 boomer rasdaemon[6391]: rasdaemon: Recording arm_event events ubuntu@boomer:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741978 Title: Add support for ARM events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765483] Re: Screen relocks a few seconds after being unlocked
** Summary changed: - Screen locked again after a succesful login + Screen relocks a few seconds after being unlocked ** Tags added: unlock ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Screen relocks a few seconds after being unlocked + Screen automatically relocks a few seconds after being unlocked -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765483 Title: Screen automatically relocks a few seconds after being unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1765483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765576] [NEW] update-boinc-applinks still needed? if so, python3 please
Public bug reported: I can't tell if the script - update-boinc-applinks is still useful/needed. Per the man page it was written only for Debian BOINC. AFAICT today it checks for this directory: /usr/share/boinc-apps/info/, which doesn't exist when boinc is installed, and then exits. >From what I can see it's the only python use in boinc-client/manager so by itself is causing it to bring in python2 (which is longer installed by default in Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: boinc-client 7.9.3+dfsg-4 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 21:48:53 2018 InstallationDate: Installed on 2018-04-14 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: boinc UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.boinc-client.global_prefs_override.xml: [modified] modified.conffile..etc.boinc-client.gui_rpc_auth.cfg: [inaccessible: [Errno 13] Permission denied: '/etc/boinc-client/gui_rpc_auth.cfg'] mtime.conffile..etc.boinc-client.global_prefs_override.xml: 2018-04-16T16:58:06.629829 ** Affects: boinc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765576 Title: update-boinc-applinks still needed? if so, python3 please To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1765576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765565] Re: xfpanel-switch is failing to save panel settings
** Branch linked: lp:~a-j-buxton/xfpanel-switch/orphan-plugins -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765565 Title: xfpanel-switch is failing to save panel settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1765565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Same on Thinkpad P51 (Nvidia Quadro M2200), Ubuntu 18.04, Nvidia 390 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765261] Re: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt
Maybe bug 1285258? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1765261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760201 Title: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
This bug was fixed in the package chrony - 3.2-4ubuntu4 --- chrony (3.2-4ubuntu4) bionic; urgency=medium * d/postrm: re-establish systemd-timesyncd on removal (LP: #1764357) * Notify chrony to update sources in response to systemd-networkd events (LP: #1718227) - d/links: link dispatcher script to networkd-dispatcher events routable and off - d/control: set Recommends to networkd-dispatcher - d/p/lp-1718227-ignore-non-up-down-events-in-nm-dispatcher.patch - d/p/lp-1718227-nm-dispatcher-for-networkd.patch -- Christian EhrhardtMon, 16 Apr 2018 17:04:06 +0200 ** Changed in: chrony (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718227 Title: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
Thanks, Colin. I will test it as soon as I can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764357] Re: uninstalling chrony leaves no time service running
This bug was fixed in the package chrony - 3.2-4ubuntu4 --- chrony (3.2-4ubuntu4) bionic; urgency=medium * d/postrm: re-establish systemd-timesyncd on removal (LP: #1764357) * Notify chrony to update sources in response to systemd-networkd events (LP: #1718227) - d/links: link dispatcher script to networkd-dispatcher events routable and off - d/control: set Recommends to networkd-dispatcher - d/p/lp-1718227-ignore-non-up-down-events-in-nm-dispatcher.patch - d/p/lp-1718227-nm-dispatcher-for-networkd.patch -- Christian EhrhardtMon, 16 Apr 2018 17:04:06 +0200 ** Changed in: chrony (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764357 Title: uninstalling chrony leaves no time service running To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1764357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764541] Re: Model assertions should be written out to /var/lib/snapd/seed/assertions/model
This bug was fixed in the package livecd-rootfs - 2.524 --- livecd-rootfs (2.524) bionic; urgency=medium * Ensure MAAS squashfsi are clean of passwords. LP: #1764991. livecd-rootfs (2.523) bionic; urgency=medium * Allow the configuration of model assertions independent of preseeding snaps. * Allow non-generic model assertions to be configured. * Don't include the name of the model assertion in the path we write it out to (LP: #1764541). -- Dimitri John LedkovThu, 19 Apr 2018 21:23:30 +0100 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764541 Title: Model assertions should be written out to /var/lib/snapd/seed/assertions/model To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1764541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765353] Re: gnome-control-center crashed with SIGSEGV
Tracking in: https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 ** Description changed: + https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 + + --- + Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** No longer affects: gnome-shell (Ubuntu) ** Summary changed: - gnome-control-center crashed with SIGSEGV + gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765353] Re: gnome-control-center crashed with SIGSEGV
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764991] Re: Ability to delay maas-*-controller configuration, until after install
This bug was fixed in the package livecd-rootfs - 2.524 --- livecd-rootfs (2.524) bionic; urgency=medium * Ensure MAAS squashfsi are clean of passwords. LP: #1764991. livecd-rootfs (2.523) bionic; urgency=medium * Allow the configuration of model assertions independent of preseeding snaps. * Allow non-generic model assertions to be configured. * Don't include the name of the model assertion in the path we write it out to (LP: #1764541). -- Dimitri John LedkovThu, 19 Apr 2018 21:23:30 +0100 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764991 Title: Ability to delay maas-*-controller configuration, until after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1764991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765110] Re: [regression] login screen frozen after kernel update
** Summary changed: - login screen frozen after kernel update + [regression] login screen frozen after kernel update ** Tags added: regression-update ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Summary changed: - [regression] login screen frozen after kernel update + [regression] login screen frozen after kernel update 4.13.0-38-generic (but 4.13.0-37-generic works) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765110 Title: [regression] login screen frozen after kernel update 4.13.0-38-generic (but 4.13.0-37-generic works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765572] [NEW] temp_unreadable is not initialized, will lead to thermald not reading thermal zones
Public bug reported: thermald uninitialised member causes loss of temperature control, the patch 0002-Don-t-keep-on-reading-a-sensor-if-the-temperature-is.patch, added in 1.7.0-5, introduces a new cthd_sensor data member temp_unreadable but fails to initialise it. This causes nondeterministic behaviour. If any bits of the uninitialised boolean are nonzero, it will be evaluate to true, and the sensor will be silently disabled, causing loss of temperature control. This bug is critical because loss of temperature control risks physical hardware damage. ** Affects: thermald (Ubuntu) Importance: Critical Assignee: Colin Ian King (colin-king) Status: In Progress ** Changed in: thermald (Ubuntu) Status: New => In Progress ** Changed in: thermald (Ubuntu) Importance: Undecided => Critical ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765572 Title: temp_unreadable is not initialized, will lead to thermald not reading thermal zones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1765572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765574] [NEW] /usr/bin/gnome-control-center:11:acquire_cb:g_simple_async_result_complete:acquire_cb:g_simple_async_result_complete:check_authorization_cb
*** This bug is a duplicate of bug 1765353 *** https://bugs.launchpad.net/bugs/1765353 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.0-0ubuntu6, the problem page at https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic xenial yakkety zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765574 Title: /usr/bin/gnome-control- center:11:acquire_cb:g_simple_async_result_complete:acquire_cb:g_simple_async_result_complete:check_authorization_cb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765574] Re: /usr/bin/gnome-control-center:11:acquire_cb:g_simple_async_result_complete:acquire_cb:g_simple_async_result_complete:check_authorization_cb
*** This bug is a duplicate of bug 1765353 *** https://bugs.launchpad.net/bugs/1765353 ** This bug has been marked a duplicate of bug 1765353 gnome-control-center crashed with SIGSEGV -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765574 Title: /usr/bin/gnome-control- center:11:acquire_cb:g_simple_async_result_complete:acquire_cb:g_simple_async_result_complete:check_authorization_cb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions
Because middle click actions do work in Xorg sessions, and only fail in Wayland. If you find something is broken in a Xorg session then it is not this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759754] Re: Ambiance titlebar gradient doesn't match the menubar colour
** Branch linked: lp:~3v1n0/ubuntu-themes/menubar-colors-fixes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759754 Title: Ambiance titlebar gradient doesn't match the menubar colour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1759754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765570] [NEW] libcommons-lang3-java causes NullPointer in surefire/javadoc
Public bug reported: libcommons-lang3-java requires a patch to work with openjdk-10, without it any packages that depend on it on runtime will fail with a NullPointerException - specially libmaven-javadoc-plugin-java (doc generation) and libsurefire-java (tests), which are used by most (if not all) maven dependent builds, thus a lot of stuff fails. As the libcommons-lang3-java build itself depends on both libmaven-javadoc-plugin-java and libsurefire-java, there's a 3 step to get a build working: 1) build libcommons-lang3-java patched for openjdk-10 (with docs and tests disabled) 2) rebuild surefire (for some reason it embeds libcommons-lang3-java code during build time instead of relying on the system dependency) 3) rebuild libcommons-lang3-java patched for openjdk-10 The resulting debian binary package from each step must be included in the next build steps: step #2 requires the binary from #1; step #3 requires the binaries from #1 and #2. ** Affects: libcommons-lang3-java (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765570 Title: libcommons-lang3-java causes NullPointer in surefire/javadoc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcommons-lang3-java/+bug/1765570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764607] Re: Upgrade indicator-china-weather to 2.2.8
** Changed in: indicator-china-weather (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764607 Title: Upgrade indicator-china-weather to 2.2.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-china-weather/+bug/1764607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765569] Re: [china-weather-indicator]reset.applet-position.desktop:10:Nodisplay=trues
** Changed in: ubuntukylin Assignee: kobe (kobe24-lixiang) => quankang (quankang) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765569 Title: [china-weather-indicator]reset.applet- position.desktop:10:Nodisplay=trues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1765569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
Thanks Ben for spotting the bug and for the fix, I'm uploading that to Debian right now and will sync it into Ubuntu as soon as it is ready for syncing. Much appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765089] Re: Please sync gnustep-gui 0.26.2-3 from Debian Sid/Buster
This bug was fixed in the package gnustep-gui - 0.26.2-3 Sponsored for Josh Freeman (tedge) --- gnustep-gui (0.26.2-3) unstable; urgency=medium * debian/patches/gsdisplayserver-mainthread.patch: New, cherry-picked from upstream; makes possible drawing from secondary threads which is needed by lynkeos.app/2.10. * debian/patches/gstheme-nssegmentedcontrol.patch: New, cherry-picked from upstream; fixes int/NSInteger mismatch and enables mouse tracking for NSSegmentedCell. * debian/patches/series: Update. * debian/rules: Remove boilerplate dh_make comments. -- Yavor DoganovTue, 06 Mar 2018 19:55:44 +0200 ** Changed in: gnustep-gui (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765089 Title: Please sync gnustep-gui 0.26.2-3 from Debian Sid/Buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnustep-gui/+bug/1765089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737441] Re: /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1 --- unattended-upgrades (1.1ubuntu1) bionic; urgency=medium * Merge from Debian unstable (LP: #1764797) - Remaining changes: - unattended-upgrades: Do not automatically upgrade the development release of Ubuntu unless Unattended-Upgrade::DevRelease is true. - Dropped changes, included in Debian: - Rename d/NEWS.Debian to d/NEWS to have it shipped - Fix typo in NEWS file - d/rules: Exclude mypy cache from source package. unattended-upgrades (1.1) unstable; urgency=medium [ cgail914 ] * Update 50unattended-upgrades.Raspbian added a semi-column sign on line 86 to facilitate uncommenting the line for users and not end up with an error message when running unattended-upgrades. And make the whole file consistent. [ Tobias Bannert ] * completed german translation [ Simon McVittie ] * d/rules: Exclude mypy cache from source package. [ Julian Andres Klode ] * Do not reuse old apt.Version objects after reopening cache (LP: #1737441) [ Balint Reczey ] * Rename d/NEWS.Debian to d/NEWS to have it shipped * Fix typo in NEWS file * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages option * Set UnattendedUpgradesCache.allowed_origins before calling apt.Cache.__init__() * Find package candidates to adjust sweeping through all packages only once. Later reuse the list candidates and filter out packages installed in the meantime. Thanks to Julian Andres Klode for the original patch * Use updated python-apt in upgrade-between-snapshots test * upgrade-between-snapshots: Mount /proc, too, in the chroot. Also clean up chroot properly on exit. * upgrade-between-snapshots: Use http_proxy environment variable in chroot, too * upgrade-between-snapshots: Remove packages installed as the side-effect of updating apt and python-apt * Ignore errors from compiling backported packages * Make is_autoremove_valid() nondestructive. Also fix autoremoval of packages when one package can't be removed and keeps back other package removals due to missing cache.clear() * Fix tracking removed packages * Suggest default-mta | mail-transport-agent to keep Lintian happy [ Michael Vogt ] * unattanded-upgrades: refactor get_candidates_to_adjust() to adjust_candidates() -- Balint ReczeyTue, 17 Apr 2018 16:53:30 +0200 ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737441 Title: /usr/bin/unattended- upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1737441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765565] Re: xfpanel-switch is failing to save panel settings
First a quick description of the panel configuration: Every plugin on every panel is stored in a series of properties. Then, each panel has a list of plugins on that panel, which references the central list. What has happened here is that somehow a panel has been deleted (panel-0), but the plugin settings associated with it have been left behind. However, the .desktop files for the launchers have been deleted. Launchers are not the only type of plugin which has been orphaned in this way, there are a few others. Every plugin with ID > 11 in the xml is an orphan. I'm not sure how this happened. It doesn't seem to happen with the panel in 18.04 if you delete a panel. In order to fix this I think panel-switch will have to check where every plugin exists somewhere on a panel, and if not ignore it (ie don't save it). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765565 Title: xfpanel-switch is failing to save panel settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1765565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764797] Re: [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable (main)
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1 --- unattended-upgrades (1.1ubuntu1) bionic; urgency=medium * Merge from Debian unstable (LP: #1764797) - Remaining changes: - unattended-upgrades: Do not automatically upgrade the development release of Ubuntu unless Unattended-Upgrade::DevRelease is true. - Dropped changes, included in Debian: - Rename d/NEWS.Debian to d/NEWS to have it shipped - Fix typo in NEWS file - d/rules: Exclude mypy cache from source package. unattended-upgrades (1.1) unstable; urgency=medium [ cgail914 ] * Update 50unattended-upgrades.Raspbian added a semi-column sign on line 86 to facilitate uncommenting the line for users and not end up with an error message when running unattended-upgrades. And make the whole file consistent. [ Tobias Bannert ] * completed german translation [ Simon McVittie ] * d/rules: Exclude mypy cache from source package. [ Julian Andres Klode ] * Do not reuse old apt.Version objects after reopening cache (LP: #1737441) [ Balint Reczey ] * Rename d/NEWS.Debian to d/NEWS to have it shipped * Fix typo in NEWS file * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages option * Set UnattendedUpgradesCache.allowed_origins before calling apt.Cache.__init__() * Find package candidates to adjust sweeping through all packages only once. Later reuse the list candidates and filter out packages installed in the meantime. Thanks to Julian Andres Klode for the original patch * Use updated python-apt in upgrade-between-snapshots test * upgrade-between-snapshots: Mount /proc, too, in the chroot. Also clean up chroot properly on exit. * upgrade-between-snapshots: Use http_proxy environment variable in chroot, too * upgrade-between-snapshots: Remove packages installed as the side-effect of updating apt and python-apt * Ignore errors from compiling backported packages * Make is_autoremove_valid() nondestructive. Also fix autoremoval of packages when one package can't be removed and keeps back other package removals due to missing cache.clear() * Fix tracking removed packages * Suggest default-mta | mail-transport-agent to keep Lintian happy [ Michael Vogt ] * unattanded-upgrades: refactor get_candidates_to_adjust() to adjust_candidates() -- Balint ReczeyTue, 17 Apr 2018 16:53:30 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764797 Title: [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1764797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765565] Re: xfpanel-switch is failing to save panel settings
Oh and one other thing: the missing .desktops are dated from 2015 and this is an upgrade. Looks like the default panel configuration? Maybe this is a bug in an old xfce4-panel which is now fixed, but leaves behind broken config artifacts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765565 Title: xfpanel-switch is failing to save panel settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1765565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765569] Re: [china-weather-indicator]reset.applet-position.desktop:10:Nodisplay=trues
** Also affects: indicator-china-weather (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765569 Title: [china-weather-indicator]reset.applet- position.desktop:10:Nodisplay=trues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1765569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759754] Re: Ambiance titlebar gradient doesn't match the Terminal menubar colour
** No longer affects: gnome-terminal (Ubuntu) ** Changed in: ubuntu-themes (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Summary changed: - Ambiance titlebar gradient doesn't match the Terminal menubar colour + Ambiance titlebar gradient doesn't match the menubar colour -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759754 Title: Ambiance titlebar gradient doesn't match the menubar colour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1759754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754936] Re: freeipa client missing
Seems reasonable. I hadn't seen anything in the changelog that made clear why a prerelease was being used. Thanks for the update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754936 Title: freeipa client missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1754936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758428] Re: Subprocesses of StartProgramInGuest fail when creating temporary files
This bug was fixed in the package open-vm-tools - 2:10.2.0-3ubuntu3 --- open-vm-tools (2:10.2.0-3ubuntu3) bionic; urgency=medium * Disable PrivateTmp for the open-vm-tools.service as it triggers issues when triggering processes that need tmp through VMOMI API (LP: #1758428) -- Christian EhrhardtThu, 19 Apr 2018 11:23:58 +0200 ** Changed in: open-vm-tools (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758428 Title: Subprocesses of StartProgramInGuest fail when creating temporary files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1758428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762175] Re: keep java-common pointing to OpenJDK in -proposed
So octave 4.2.2-1build1.1 actually failed to detect java and disabled it completely, looking at the build logs. I think you want to include the attached patch, it should let octave build with java 10 or 11, whichever you land on for bionic. ** Patch added: "octave-configure-java11.patch" https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1762175/+attachment/5123171/+files/octave-configure-java11.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762175 Title: keep java-common pointing to OpenJDK in -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1762175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765400] Re: OEM vendor information set to chassis vendor
This bug was fixed in the package ubuntu-report - 1.0.11 --- ubuntu-report (1.0.11) bionic; urgency=medium * Use sys_vendor to determine vendor (LP: #1765400) After a discussion with Entroware, the SMBIOS spec infer that we should prefer sys_vendor to chassis_vendor for collecting Vendor information. Use that field and update tests thus. Thanks to Michael Wilson for pointing it out. -- Didier RocheThu, 19 Apr 2018 15:00:16 +0200 ** Changed in: ubuntu-report (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765400 Title: OEM vendor information set to chassis vendor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1765400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764355] Re: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login
This bug was fixed in the package gnome-session - 3.28.1-0ubuntu2 --- gnome-session (3.28.1-0ubuntu2) bionic; urgency=medium * debian/xdg_dirs_desktop_session.sh, debian/55gnome-session_gnomerc: - protect against multiple additions of the same paths to XDG_CONFIG_DIRS and XDG_DATA_DIRS, resulting to duplication on consecutive logout/logins due to older session hanging in and env being reused. Some consequences is that electron application crashes (LP: #1764355) -- Didier RocheThu, 19 Apr 2018 16:43:50 +0200 ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764355 Title: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1764355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765565] Re: xfpanel-switch is failing to save panel settings
** Attachment added: "xfce4-panel.xml" https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1765565/+attachment/5123170/+files/xfce4-panel.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765565 Title: xfpanel-switch is failing to save panel settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1765565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765565] [NEW] xfpanel-switch is failing to save panel settings
Public bug reported: When I try to save the actual xfce4-panel settings the save fails. When opening xfpanel-switch terminal, the following message appears when clicking to save: Traceback (most recent call last): File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 221, in on_save_clicked self.save_configuration(name) File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 209, in save_configuration PanelConfig.from_xfconf(self.xfconf).to_file(filename) File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 64, in from_xfconf pc.find_desktops() File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 114, in find_desktops if self.check_desktop(desktop_path): File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 88, in check_desktop bytes = self.get_desktop_source_file(path).read() File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 129, in get_desktop_source_file return open(path, 'rb') FileNotFoundError: [Errno 2] Arquivo ou diretório inexistente: '/home/usuario/.config/xfce4/panel/launcher-21/14294989537.desktop' And the panel setting is not saved. When this happens, the buttons to save and close have no action when clicked. Here is a image with the panel: https://i.imgur.com/7kuhAr5.png Here is the output from ls -lR ~/.config/xfce4/panel /home/usuario/.config/xfce4/panel: total 24 -rw-rw-r-- 1 usuario usuario 145 abr 19 21:26 genmon-10.rc -rw-rw-r-- 1 usuario usuario 99 fev 9 2017 genmon-16.rc drwx-- 2 usuario usuario 4096 abr 19 20:08 launcher-1 drwx-- 2 usuario usuario 4096 abr 19 20:08 launcher-8 -rw-rw-r-- 1 usuario usuario 1739 ago 27 2017 whiskermenu-1.rc -rw-rw-r-- 1 usuario usuario 1959 abr 19 20:40 whiskermenu-2.rc /home/usuario/.config/xfce4/panel/launcher-1: total 4 -rw-rw-r-- 1 usuario usuario 708 abr 19 20:08 15241793011.desktop /home/usuario/.config/xfce4/panel/launcher-8: total 4 -rw-rw-r-- 1 usuario usuario 532 abr 19 20:08 15241793122.desktop ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfpanel-switch 1.0.7-0ubuntu1 Uname: Linux 4.16.3-041603-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 19 21:35:10 2018 InstallationDate: Installed on 2017-06-13 (310 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: xfpanel-switch UpgradeStatus: Upgraded to bionic on 2017-10-20 (182 days ago) ** Affects: xfpanel-switch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765565 Title: xfpanel-switch is failing to save panel settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1765565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760397] Re: gnome-software crashed with SIGSEGV in g_type_check_instance() → g_signal_emit_valist → g_signal_emit → g_closure_invoke
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760397 Title: gnome-software crashed with SIGSEGV in g_type_check_instance() → g_signal_emit_valist → g_signal_emit → g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1760397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs