[Bug 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed
** This bug is no longer a duplicate of bug 1801912 ctrl-f doesn't open the search box -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1735071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801912] Re: ctrl-f doesn't open the search box
*** This bug is a duplicate of bug 1735071 *** https://bugs.launchpad.net/bugs/1735071 ** This bug has been marked a duplicate of bug 1735071 Ctrl + F search disengages immediately after CTRL + F pressed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801912 Title: ctrl-f doesn't open the search box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1801912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808237] Re: Ubuntu-Software: CTRL+F does not open search
*** This bug is a duplicate of bug 1735071 *** https://bugs.launchpad.net/bugs/1735071 ** This bug is no longer a duplicate of bug 1801912 ctrl-f doesn't open the search box ** This bug has been marked a duplicate of bug 1735071 Ctrl + F search disengages immediately after CTRL + F pressed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808237 Title: Ubuntu-Software: CTRL+F does not open search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1808237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738675] Re: Deleting every search action in the whisker menu preferences crashes the prefereces
*This previous testing was done in a Virtual Box virtual machine in 18.04.1 LTS with the latest updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738675 Title: Deleting every search action in the whisker menu preferences crashes the prefereces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-whiskermenu-plugin/+bug/1738675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738675] Re: Deleting every search action in the whisker menu preferences crashes the prefereces
I also did some more testing and found that just deleting a last search entry, where all others are deleted, would cause the program to crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738675 Title: Deleting every search action in the whisker menu preferences crashes the prefereces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-whiskermenu-plugin/+bug/1738675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738675] Re: Deleting every search action in the whisker menu preferences crashes the prefereces
Yes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738675 Title: Deleting every search action in the whisker menu preferences crashes the prefereces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-whiskermenu-plugin/+bug/1738675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists
I needed to reinstall Ubuntu and the problems I attached earlier no longer apply. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744214 Title: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists
** Attachment added: "This is the output of apt-get remove --purge linux-image-extra-4.13.0-25-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5042466/+files/P0kVWunc.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744214 Title: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists
** Attachment added: "This is the output when I run dpkg --configure -a" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5042465/+files/zMWvxbzf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744214 Title: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists
** Attachment added: "This is the output I get when I try to install 4.15.0-041500rc9-generic." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5042464/+files/PiJFDc42.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744214 Title: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists
I tried installing and testing the mainline kernel, but I encountered issues with the linux-image not generating. I also tried to install openssh-server and ssh while on 4.10.0-19-generic and I get errors that dpkg failed processing 4.13.0-25 with the new modules. I have tried uninstalling this same kernel and I encounter similar errors by dpkg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744214 Title: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists
** Tags removed: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744214 Title: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744214 Title: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists
I also get the attached screenshot when attempting to boot into recovery mode. ** Description changed: I recently updated Ubuntu 18.04 in a vm have a long dormancy and I found - the issues I had after a reboot. I am currently running - 4.10.0-19-generic. + the issues I had after a reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.13.0.17.18 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: reg1325 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: reg1325 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 18 21:50:54 2018 InstallationDate: Installed on 2017-11-27 (52 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: - lono wireless extensions. - - enp0s3no wireless extensions. + lono wireless extensions. + + enp0s3no wireless extensions. Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=d15b971c-a592-4259-b4fd-b74cf3c4d03c ro quiet splash RelatedPackageVersions: - linux-restricted-modules-4.10.0-19-generic N/A - linux-backports-modules-4.10.0-19-generic N/A - linux-firmware 1.170 + linux-restricted-modules-4.10.0-19-generic N/A + linux-backports-modules-4.10.0-19-generic N/A + linux-firmware 1.170 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-11-27 (52 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Attachment added: "This is a screenshot of the issue that I encounter when booting 4.13.0-17-generic." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5039285/+files/VirtualBox_Ubuntu%2018.04%20%28regular%20user%20view%20point%29_18_01_2018_22_18_56.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744214 Title: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744214] [NEW] Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists
Public bug reported: I recently updated Ubuntu 18.04 in a vm have a long dormancy and I found the issues I had after a reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.13.0.17.18 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reg1325 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 18 21:50:54 2018 InstallationDate: Installed on 2017-11-27 (52 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=d15b971c-a592-4259-b4fd-b74cf3c4d03c ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.170 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-11-27 (52 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744214 Title: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738675] [NEW] Deleting every search action in the whisker menu preferences crashes the prefereces
Public bug reported: Steps to reproduce: 1. Open the Whisker Menu preferences. 2. Go to the Search Actions tab. 3. Delete all the existing entries (I did this in descending order). 4. After deleting the last one, the preference window closes. The expected behavior is that the preference window does not close when deleting the last search action entry. When the window closed, I also lost all changes recently made in the time the window was open. I'm just stating this here just in case the program saves periodically instead after each action. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfce4-whiskermenu-plugin 2.1.3-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 17 16:05:14 2017 InstallationDate: Installed on 2017-01-07 (344 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-whiskermenu-plugin UpgradeStatus: Upgraded to bionic on 2017-11-27 (20 days ago) ** Affects: xfce4-whiskermenu-plugin (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/1738675 Title: Deleting every search action in the whisker menu preferences crashes the prefereces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-whiskermenu-plugin/+bug/1738675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735071] [NEW] Ctrl + F search disengages immediately after CTRL + F pressed
Public bug reported: I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome-software- center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session ** Description changed: I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome-software- center from other distributions and the master branch and this works. I - think this is a theme issue. + think this is a theme issue. I am using the default Ubuntu theme by the + way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: - gnome-software-plugin-flatpak N/A - gnome-software-plugin-limba N/A - gnome-software-plugin-snap3.26.3-2ubuntu1 + gnome-software-plugin-flatpak N/A + gnome-software-plugin-limba N/A + gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1735071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734966] [NEW] gedit crashed with SIGSEGV in g_closure_invoke()
Public bug reported: I accidentally opened a 7.8 MB text file with gedit and closed it. From what I could tell, it looked like it exited fine but evidently it didn't. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gedit 3.22.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 10:01:37 2017 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2017-11-27 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gedit /media/username/VBox_GAs_5.2.0/VBoxLinuxAdditions.run ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f9bace1aea2: mov0x18(%rax),%rdi PC (0x7f9bace1aea2) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to bionic on 2017-11-27 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734966 Title: gedit crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1734966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734472] Re: memcheck-amd64-linux crashed with signal 5
** Description changed: I ran valgrind -v on a freshly built version of dconf-editor and a - minute or two later I got the error message in the summary. + minute or two later I got the error message in the summary. This is + reproducible by running valgrind -v on a freshly built version of dconf- + editor installed in a prefix. I'm not sure if the proper schema files + need to be pointed to or not but when I ran it, the proper schema files + couldn't be found no matter what GSETTINGS_SCHEMA_DIR was pointed to. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: valgrind 1:3.13.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 23:16:23 2017 ExecutablePath: /usr/lib/valgrind/memcheck-amd64-linux InstallationDate: Installed on 2017-07-20 (126 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/valgrind.bin ../a/bin/dconf-editor Signal: 5 SourcePackage: valgrind StacktraceTop: - ?? () - ?? () - ?? () - ?? () - ?? () + ?? () + ?? () + ?? () + ?? () + ?? () Title: memcheck-amd64-linux crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2017-11-23 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734472 Title: memcheck-amd64-linux crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1734472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734472] [NEW] memcheck-amd64-linux crashed with signal 5
Public bug reported: I ran valgrind -v on a freshly built version of dconf-editor and a minute or two later I got the error message in the summary. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: valgrind 1:3.13.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 23:16:23 2017 ExecutablePath: /usr/lib/valgrind/memcheck-amd64-linux InstallationDate: Installed on 2017-07-20 (126 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/valgrind.bin ../a/bin/dconf-editor Signal: 5 SourcePackage: valgrind StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: memcheck-amd64-linux crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2017-11-23 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: valgrind (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734472 Title: memcheck-amd64-linux crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1734472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734267] [NEW] Show Applications context menu item links to shell extensions instead of dock settings
Public bug reported: After right clicking for the context menu on the Show Applications button the context menu option "Dash to Dock Settings" doesn't open up the dock settings in gnome-control-center but the shell extensions menu instead. 1. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2. gnome-shell-extension-ubuntu-dock: Installed: 0.8.1 Candidate: 0.8.1 Version table: *** 0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status 3. I expected the Show Applications button's context menu item, Dash to Dock Settings, to open up gnome-control-center to the Dock settings tab. 4. The Shell Extensions window popped up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.8.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 21:41:06 2017 InstallationDate: Installed on 2017-07-20 (126 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to bionic on 2017-11-23 (1 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session ** Description changed: After right clicking for the context menu on the Show Applications button the context menu option "Dash to Dock Settings" doesn't open up - the dock settings in gnome-control-center but the shell extensions menu. + the dock settings in gnome-control-center but the shell extensions menu + instead. 1. Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. gnome-shell-extension-ubuntu-dock: - Installed: 0.8.1 - Candidate: 0.8.1 - Version table: - *** 0.8.1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 0.8.1 + Candidate: 0.8.1 + Version table: + *** 0.8.1 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages + 100 /var/lib/dpkg/status 3. I expected the Show Applications button's context menu item, Dash to Dock Settings, to open up gnome-control-center to the Dock settings tab. 4. The Shell Extensions window popped up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.8.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 21:41:06 2017 InstallationDate: Installed on 2017-07-20 (126 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to bionic on 2017-11-23 (1 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734267 Title: Show Applications context menu item links to shell extensions instead of dock settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1734267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734201] Re: gdm3 requires a restart to show a change in the list of desktop environments
This isn't a new bug, but it has been fixed in the past. I'm not sure whether to make a new bug or just link to it so it inevitably gets reopened. I'll post the link to the bug here: https://bugzilla.gnome.org/show_bug.cgi?id=746798 ** Bug watch added: GNOME Bug Tracker #746798 https://bugzilla.gnome.org/show_bug.cgi?id=746798 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734201 Title: gdm3 requires a restart to show a change in the list of desktop environments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1734201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734196] Re: gnome-control-center: Ubuntu dock settings is blank
Just to clarify, the Dock item in the gnome-control-center was populated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734196 Title: gnome-control-center: Ubuntu dock settings is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1734196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734196] Re: gnome-control-center: Ubuntu dock settings is blank
Could it be because I'm on the developer's branch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734196 Title: gnome-control-center: Ubuntu dock settings is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1734196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734196] Re: gnome-control-center: Ubuntu dock settings is blank
I got no output when I issue that command. I issued the command "sudo apt-get install gnome-shell-extension-ubuntu-dock" without the quotes and logged out then logged back in and the extension was loaded. Thank you for your help. What are possible reasons why this wasn't installed when I did a do- release-upgrade? Let alone upgrade while I still was using Ubuntu 17.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734196 Title: gnome-control-center: Ubuntu dock settings is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1734196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734201] [NEW] gdm3 requires a restart to show a change in the list of desktop environments
Public bug reported: When installing or deleting desktop environments, gdm3 doesn't update the list of desktop environments when logging out. It requires a reboot in order to show a change. Lightdm requires a simple logout in order to update the list of desktop environments. This is an inconvenience and a nuisance if this were to be default behavior. 1. Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. gdm3: Installed: 3.26.2.1-2ubuntu1 Candidate: 3.26.2.1-2ubuntu1 Version table: *** 3.26.2.1-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected the list of desktop environments in gdm3 to update when logging out. 4. I didn't get an updated list of desktop environments in gdm3 logging out but instead after a reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.26.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 12:25:30 2017 InstallationDate: Installed on 2017-07-20 (126 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2017-11-23 (0 days ago) mtime.conffile..etc.gdm3.custom.conf: 2017-08-14T11:30:53.892633 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734201 Title: gdm3 requires a restart to show a change in the list of desktop environments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1734201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734196] Re: gnome-control-center: Ubuntu dock settings is blank
** Description changed: Upon opening the Dock settings in gnome-control-center, I find that it is blank and devoid from any information or settings. the only thing that is there is a separator line at the very top. Also, I know this should be another bug report, but I want to say that the new gnome-shell for Ubuntu is not showing up for me and instead shows the default gnome- shell. 1. Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. + gnome-control-center: Installed: 1:3.26.2-0ubuntu1 Candidate: 1:3.26.2-0ubuntu1 Version table: *** 1:3.26.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status - 3. I expected to be settings and information to show up in the dock settings. - 4. I got blankness and a separator line in the dock settings. + 3. I expected there to be settings and information to show up in the dock settings. + 4. I got a blank canvas and a separator line in the dock settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 11:40:49 2017 InstallationDate: Installed on 2017-07-20 (126 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2017-11-23 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734196 Title: gnome-control-center: Ubuntu dock settings is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1734196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734196] [NEW] gnome-control-center: Ubuntu dock settings is blank
Public bug reported: Upon opening the Dock settings in gnome-control-center, I find that it is blank and devoid from any information or settings. the only thing that is there is a separator line at the very top. Also, I know this should be another bug report, but I want to say that the new gnome-shell for Ubuntu is not showing up for me and instead shows the default gnome- shell. 1. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2. Installed: 1:3.26.2-0ubuntu1 Candidate: 1:3.26.2-0ubuntu1 Version table: *** 1:3.26.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected to be settings and information to show up in the dock settings. 4. I got blankness and a separator line in the dock settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 11:40:49 2017 InstallationDate: Installed on 2017-07-20 (126 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2017-11-23 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session ** Attachment added: "This is a screenshot displaying my issue." https://bugs.launchpad.net/bugs/1734196/+attachment/5013809/+files/Screenshot%20from%202017-11-23%2012-12-47.png ** Description changed: Upon opening the Dock settings in gnome-control-center, I find that it is blank and devoid from any information or settings. the only thing that is there is a separator line at the very top. Also, I know this should be another bug report, but I want to say that the new gnome-shell for Ubuntu is not showing up for me and instead shows the default gnome- shell. - 1. + 1. Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 - 2. - Installed: 1:3.26.2-0ubuntu1 - Candidate: 1:3.26.2-0ubuntu1 - Version table: - *** 1:3.26.2-0ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 100 /var/lib/dpkg/status - 3. I expected to be settings and information to show up in the dock settings. + 2. + Installed: 1:3.26.2-0ubuntu1 + Candidate: 1:3.26.2-0ubuntu1 + Version table: + *** 1:3.26.2-0ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 100 /var/lib/dpkg/status + 3. I expected to be settings and information to show up in the dock settings. 4. I got blankness and a separator line in the dock settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 11:40:49 2017 InstallationDate: Installed on 2017-07-20 (126 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2017-11-23 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734196 Title: gnome-control-center: Ubuntu dock settings is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1734196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714726] Re: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714726 Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1714726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714726] Re: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
** Description changed: - When I go to resize my VirtualBox window which is running an instance of - Ubuntu 17.10, compiz crashes. This is fairly annoying and has been going - on for a couple of weeks. + When I go to snap my VirtualBox window which is running an instance of + Ubuntu 17.10 to any part of the screen compiz crashes. This is fairly + annoying and has been going on for a couple of weeks. Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 compiz: - Installed: 1:0.9.13.1+17.10.20170720-0ubuntu1 - Candidate: 1:0.9.13.1+17.10.20170720-0ubuntu1 + Installed: 1:0.9.13.1+17.10.20170720-0ubuntu1 + Candidate: 1:0.9.13.1+17.10.20170720-0ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: compiz-core 1:0.9.13.1+17.10.20170720-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 .tmp.unity_support_test.1: - + ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 2 17:23:11 2017 DistUpgraded: 2017-08-11 11:30:39,829 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: tp_smapi, 0.42, 4.11.0-13-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-07-20 (44 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/bin/compiz ProcEnviron: - LANG=en_US.UTF-8 - LANGUAGE=en_US - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + LANGUAGE=en_US + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic root=UUID=24ac11bf-512c-405c-b2b1-f2df7e2283f2 ro quiet splash Renderer: Software Signal: 6 SourcePackage: compiz StacktraceTop: - __gnu_cxx::__verbose_terminate_handler() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 - std::get_terminate() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 - () - std::get_unexpected() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 - () + __gnu_cxx::__verbose_terminate_handler() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 + std::get_terminate() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 + () + std::get_unexpected() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 + () Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to artful on 2017-08-11 (22 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1 version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Sep 2 17:23:22 2017 xserver.configfile: default xserver.errors: - Failed to load module "vboxvideo" (module does not exist, 0) - Failed to load module "vboxvideo" (module does not exist, 0) - modeset(0): glamor initialization failed - AIGLX: reverting to software rendering + Failed to load module "vboxvideo" (module does not exist, 0) + Failed to load module "vboxvideo" (module does not exist, 0) + modeset(0): glamor initialization failed + AIGLX: reverting to software rendering xserver
[Bug 1714726] [NEW] compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
Public bug reported: When I go to snap my VirtualBox window which is running an instance of Ubuntu 17.10 to any part of the screen compiz crashes. This is fairly annoying and has been going on for a couple of weeks. Description:Ubuntu Artful Aardvark (development branch) Release:17.10 compiz: Installed: 1:0.9.13.1+17.10.20170720-0ubuntu1 Candidate: 1:0.9.13.1+17.10.20170720-0ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: compiz-core 1:0.9.13.1+17.10.20170720-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 2 17:23:11 2017 DistUpgraded: 2017-08-11 11:30:39,829 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: tp_smapi, 0.42, 4.11.0-13-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-07-20 (44 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/bin/compiz ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic root=UUID=24ac11bf-512c-405c-b2b1-f2df7e2283f2 ro quiet splash Renderer: Software Signal: 6 SourcePackage: compiz StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::get_terminate() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () std::get_unexpected() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to artful on 2017-08-11 (22 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1 version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Sep 2 17:23:22 2017 xserver.configfile: default xserver.errors: Failed to load module "vboxvideo" (module does not exist, 0) Failed to load module "vboxvideo" (module does not exist, 0) modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu5 xserver.video_driver: modeset ** Affects: compiz (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-crash artful compiz compiz-0.9 reproducible ubuntu ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714726 Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1714726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711780] [NEW] IP stops returning to arp-scan when sshed into
Public bug reported: When I do a scan of my local network via the command arp-scan --localnet, I find that the IP of the machine which has Ubuntu-MATE on it shows up in the list of IPs brought back by arp-scan. But when I ssh to that machine and then issue the command arp-scan --localnet from the machine that I had sshed from, I find that the IP address of the computer with Ubuntu-MATE on it is absent from the list. I expect the IP address with the machine with Ubuntu-MATE to show up. I tested this with other machines and operating systems and those still returned an IP address when issued arp-scan --localnet. The Ubuntu-MATE machine was the only one which didn't. I posted a bug report here and here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1711465 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1711465 These links lead to more thorough data if applicable. Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: arp-scan 1.9-1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 Date: Fri Aug 18 20:59:50 2017 InstallationDate: Installed on 2017-01-07 (223 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: arp-scan UpgradeStatus: Upgraded to artful on 2017-08-11 (7 days ago) ** Affects: arp-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug arp-scan artful ip network stop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711780 Title: IP stops returning to arp-scan when sshed into To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arp-scan/+bug/1711780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711465] [NEW] IP stops returning to arp-scan when sshed into.
Public bug reported: I posted this on the Ubuntu-MATE bug report before this (https://bugs.launchpad.net/ubuntu-mate/+bug/1711460), but I don't know how active that place is so I'm also going to post it here. I also don't know if this is the right package to post this in, but since there is no clear way to post bugs with ambiguous sources of problems, I am posting here. When I do a scan of my local network via the command arp-scan --localnet, I find that the IP of the machine which has Ubuntu-MATE on it shows up in the list of IPs brought back by arp-scan. But when I ssh to that machine and then issue the command arp-scan --localnet from the machine that I had sshed from, I find that the IP address of the computer with Ubuntu-MATE on it is absent from the list. I expect the IP address with the machine with Ubuntu-MATE to show up. I tested this with other machines and operating systems and those still returned an IP address when issued arp-scan --localnet. The Ubuntu-MATE machine was the only one which didn't. Description:Ubuntu Artful Aardvark (development branch) Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 Date: Thu Aug 17 14:19:46 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-07 (222 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp7s0 proto static metric 600 169.254.0.0/16 dev wlp7s0 scope link metric 1000 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.96 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2017-08-11 (6 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH wlp7s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Windows7Family 2 ea6b04bf-6ea5-4250-9783-f8df31fb090a /org/freedesktop/NetworkManager/ActiveConnection/3 enp6s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.2connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug arp-scan artful broadcast network ssh ** Attachment removed: "nmcli-con.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1711465/+attachment/4934447/+files/nmcli-con.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711465 Title: IP stops returning to arp-scan when sshed into. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1711465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
