[Desktop-packages] [Bug 1725659] Re: gnome-terminal-server crashed when I set new shortcuts (ctr+right arrow) and when I use ctrl+N to open new tab
*** This bug is a duplicate of bug 1438014 *** https://bugs.launchpad.net/bugs/1438014 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 #1438014, 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/1725659/+attachment/4981867/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725659/+attachment/4981869/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725659/+attachment/4981873/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725659/+attachment/4981874/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725659/+attachment/4981875/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725659/+attachment/4981876/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725659/+attachment/4981877/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1438014 gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1725659 Title: gnome-terminal-server crashed when I set new shortcuts (ctr+right arrow) and when I use ctrl+N to open new tab Status in gnome-terminal package in Ubuntu: New Bug description: gnome-terminal-server crashed when I set new shortcuts (ctr+right arrow or ctrl+left arrow tab navigation) and when I use ctrl+N to open new tab. This has been bugging me since Ubuntu 17.04 GNOME. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:08:44 2017 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server SegvAnalysis: Segfault happened at: 0x7fca3d40677e: testb $0x4,0x16(%rdx) PC (0x7fca3d40677e) ok source "$0x4" ok destination "0x16(%rdx)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725652] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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 #1505409, 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/1725652/+attachment/4981811/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725652/+attachment/4981813/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725652/+attachment/4981817/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725652/+attachment/4981818/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725652/+attachment/4981819/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725652/+attachment/4981820/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725652/+attachment/4981821/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725652 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: the above error ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Oct 21 05:23:25 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-04-17 (186 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725663] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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 #1505409, 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/1725663/+attachment/4981907/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725663/+attachment/4981909/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725663/+attachment/4981912/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725663/+attachment/4981913/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725663/+attachment/4981914/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725663/+attachment/4981915/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725663/+attachment/4981916/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725663 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: Running Ubuntu 17.10. Fresh install with existing /home folder gnome-shell Installed: 3.26.1-0ubuntu4 Occurred after installing NVIDIA binary driver 384.90 and restarting. (not sure if it is related) System seems to run fine- just the error message. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Oct 20 19:51:54 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717987] Re: gnome-control-center crashed with SIGABRT in mem_error()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1717987 Title: gnome-control-center crashed with SIGABRT in mem_error() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: crashed when adding a network printer ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 18:40:07 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-04-21 (149 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 __nptl_deallocate_tsd () at pthread_create.c:291 Title: gnome-control-center crashed with SIGABRT in __nptl_deallocate_tsd() UpgradeStatus: Upgraded to artful on 2017-09-15 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts
Got this bug on installation of fresh Ubuntu 17.10. I selected Russian keyboard layout on installation. After installation I got bothand convenient keyboard layout switchers. Here is my /etc/default/keyboard : # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="us,ru" XKBVARIANT="," XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" BACKSPACE="guess" I like keyboard layout switcher, it is great. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1242572 Title: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts Status in xkeyboard-config: Fix Released Status in console-setup package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in xkeyboard-config package in Ubuntu: Fix Released Status in console-setup source package in Trusty: Confirmed Status in ubiquity source package in Trusty: Confirmed Status in xkeyboard-config source package in Trusty: In Progress Bug description: Super+Space is default combination for switching keyboard layouts in gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg; console-setup; and ubiquity should also use Super+Space combination for switching keyboard layouts. reading xkeyboard-config sources and documentations i don't see that xkeyboard-config can support grp:lwin_space and i guess that needs to be the first step to properly support super+space. Original bug report below: Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10. I use two keyboard layouts - English and Russian. So I select them on the corresponding screen of ubiquity setup wizard. It quietly set the keyboard switching shortcut to Alt+Shift and wrote this setting to /etc/default/keyboard: # ... XKBMODEL="pc105" XKBLAYOUT="us,ru" XKBVARIANT="," XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" # ... On first boot of installed system the small notification pop-up showed that Ibus will use Super+Space for layout switching. Please fix this configuration inconsistency. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Mon Oct 21 12:16:58 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- InstallationDate: Installed on 2013-10-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 (20131017) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
Hopefully this bug will be fixed eventually, but for now I found an ugly workaround which made my Brother scanner (brscan3 driver) work again. - Installed the equivs package. - Purged libsane1 by 'sudo dpkg --purge --ignore-depends=libsane1 libsane1'. - Installed the zesty versions of libsane, libsane-common and sane-utils by 'sudo dpkg -i' and marked them not to be upgraded by 'sudo apt-mark hold libsane libsane-common sane-utils'. - Created a controlfile 'libsane1' by 'equivs-control libsane1' and edited it so that it looks like this: ### Commented entries have reasonable defaults. ### Uncomment to edit them. # Source: Section: misc Priority: optional # Homepage: Standards-Version: 3.9.2 Package: libsane1 Version: 4:99 # Maintainer: Your Name# Pre-Depends: # Depends: # Recommends: # Suggests: # Provides: # Replaces: # Architecture: all # Multi-Arch: # Copyright: # Changelog: # Readme: # Extra-Files: # Files: # Description: dummy package dummy package for libsane1 - Built a dummy package libsane1_99_all.deb by 'equivs-build libsane1' and installed it by 'sudo dpkg -i' to satisfy dependencies. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Committed Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Impact == The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning. Also the soname change might be justified by the new version breaking most 3rd party plug-ins even if the library version number doesn't any bigger change than any ordinary new version of the library: libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 The breaking of all plug-ins might be an upstream bug - which is allowed in an experimental package, but is unfortunate as in Ubuntu this package went mainstream; The library rename is an additional factor that makes it impossible to install any scanner drivers for libsane that are distributed as a .deb unless the driver distributors recompiles against Ubuntu 17.10+. It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this; Adding a Provides: libsane to the library might therefore make some plug-ins work, perhaps. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725116] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
occurred during upgrade from 17.04 to 17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1725116 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Confirmed Bug description: Update to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Thu Oct 19 21:36:09 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2012-04-02 (2026 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1725116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725675] [NEW] SIM-Card PIN-Code unlock windows spawns in front of login screen
Public bug reported: Sometimes the PIN-Code request window opens over the session unlock screen. The window cannot be moved. Entering PIN-Code is possible but fails. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 21 14:22:26 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2017-08-25 (56 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1725675 Title: SIM-Card PIN-Code unlock windows spawns in front of login screen Status in network-manager package in Ubuntu: New Bug description: Sometimes the PIN-Code request window opens over the session unlock screen. The window cannot be moved. Entering PIN-Code is possible but fails. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 21 14:22:26 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2017-08-25 (56 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725662] Re: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset()
*** This bug is a duplicate of bug 1718477 *** https://bugs.launchpad.net/bugs/1718477 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 #1718477, 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/1725662/+attachment/4981896/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725662/+attachment/4981898/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725662/+attachment/4981902/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725662/+attachment/4981903/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725662/+attachment/4981904/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725662/+attachment/4981905/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725662/+attachment/4981906/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1718477 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725662 Title: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset() Status in gnome-control-center package in Ubuntu: New Bug description: The gnome-control-center stops responding for a long time. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 21 09:48:04 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-06-17 (126 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170615) ProcCmdline: gnome-control-center --overview Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_markup_parse_context_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] Re: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland
I have just made a clean installation of Ubuntu. artful64@artful64:~$ head /etc/apt/sources.list -n2 #deb cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]/ artful main restricted During installation I set Russian keyboard layout. On first login I launched Firefox and accidentally pressed. And it switched the layout. Of course works too. But Firefox distracts me if I press . So you have set as layout switcher quietly in Ubiquity (see bug 1242572). artful64@artful64:~$ cat /etc/os-release NAME="Ubuntu" VERSION="17.10 (Artful Aardvark)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 17.10" VERSION_ID="17.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=artful UBUNTU_CODENAME=artful artful64@artful64:~$ cat /etc/default/keyboard # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="us,ru" XKBVARIANT="," XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" BACKSPACE="guess" artful64@artful64:~$ It seems that this is severe bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982082/+files/PciNetwork.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982080/+files/JournalErrors.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982075/+files/CRDA.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] Re: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland
AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: artful64 1468 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.3.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.3.0/24 dev wlp2s0 proto kernel scope link src 192.168.3.15 metric 600 Locales: extensions.sqlite corrupt or missing Package: firefox 56.0+build6-0ubuntu1 PackageArchitecture: amd64 PrefSources: prefs.js ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RunningIncompatibleAddons: False Tags: wayland-session artful Themes: extensions.sqlite corrupt or missing Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Tags added: apport-collected wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2
[Desktop-packages] [Bug 1712200] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982081/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982079/+files/IwConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982077/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982078/+files/IpAddr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] Prefs.txt
apport information ** Attachment added: "Prefs.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982083/+files/Prefs.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725371] Re: 17.10 nautilus 3.26.0 fails to recognize mouse middle button to lower window
Just to show that middle click is correctly defined as default to lower gsettings get org.gnome.desktop.wm.preferences action-middle-click- titlebar 'lower' to see I am not using wayland loginctl show-session c2 -p Type Type=x11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1725371 Title: 17.10 nautilus 3.26.0 fails to recognize mouse middle button to lower window Status in nautilus package in Ubuntu: New Bug description: It's very handy to send any open Ubuntu application window to below all other open windows (it stays open yet now occluded) by clicking mouse middle button on window title bar (opposite of left mouse click to bring to focus front) ... this works fine on all Ubuntu 17.10 applications except fails on Ubuntu 17.10's file explorer nautilus 3.26.0 which has a non-standard looking title bar. This behavior continues to be OK on all other 17.10 applications... Nautilus worked on previous Ubuntu releases ... I hope other apps refrain from using this new window behavior Any ideas on why nautilus breaks this convention? Or how to fix it? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Oct 20 10:53:51 2017 InstallationDate: Installed on 2017-05-17 (155 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2017-07-30 (81 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725395] Re: screen resolution detected is incompatible with UHD tv
The tv is a 43" 3840x2160 samsung an by chance was misdetected as a 83" one In this event it was working at native resolution and had the login visible. I tried but I'm unable to make this happen at will. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1725395 Title: screen resolution detected is incompatible with UHD tv Status in nautilus package in Ubuntu: New Bug description: It was fine with 17.04 and all latest updates but after upgrade to 17.10 there is an issue. At boot the UHD tv on hdmi is complaining that 720x480 60Hz is unsupported and screen is displaying nothing. With another monitor connected on display port looks like the higher resolutions on hdmi are not handled properly. VGA is an RX480. After setting a viable resolution for the UHD tv 1920x1080 it is usable. After reboot the login screen is still detected at the unworkable 720x480. Blindly doing a login makes the new display setting to get applied and it works. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 19:21:10 2017 ExecutablePath: /usr/bin/nautilus-desktop InstallationDate: Installed on 2017-10-15 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982074/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] Re: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland
** Description changed: - Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with - Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: - * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. + * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. + Notes: + It seems that keyboard layout switcher was quietly set in Ubiquity (see bug 1242572). + + - Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts - and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching
[Desktop-packages] [Bug 1722298] Re: keyboard autorepeat not happening when I hold down any key
I fund a problem with the peaq wmi module. I just executed rmmod peaq_wmi and now it's OK, but I do not know anything about this module. Can you help me? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1722298 Title: keyboard autorepeat not happening when I hold down any key Status in gnome-terminal package in Ubuntu: Confirmed Bug description: The failure to auto repeat happens in all terminal apps I've tried in Artful. If I open a virtual console, it looks like a phantom is typing ^@ about once per second. This prevents successfully typing a password, and is probably what is breaking autorepeat in the GUI terminals, although they don't show the ^@. Gnome terminal and guake also can't stay scrolled up in the buffer for more than a second before popping back down to the bottom. This problem happens in the Ubuntu desktop or Gnome and it doesn't matter if I pick the xorg or default Wayland options. It happens under both the open source and proprietary nvidia drivers. It also happens with a newly created user with no home directory baggage. xev reports a constant stream of the following about the same frequency as the ^@ in console: KeyPress event, serial 62, synthetic NO, window 0x381, root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501), state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False If I boot into a recovery shell, the problem does _not_ appear. My system was built with a fresh install of 17.04, installed my usual packages, then upgrade to 17.10 when the problem began. I'm certain it was not present in 17.04 for the few days before I upgraded. There were similar bugs reported a decade ago, but didn't help me. Expectation: Hold down any key in terminal window. After a moment, the letter should repeat until key is released. Actually: Key will repeat 0 or a few times, but stop repeating before I release the key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 9 10:43:56 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1722298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage
Any workaround to stop this for now? I deleted syslog so it won't fill my disk, but systemd-journal and syslogd eats all my cpu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1723362 Title: gnome-software spams error messages to journald and causes 100% CPU usage Status in gnome-software package in Ubuntu: Confirmed Bug description: gnome-software spams this message to journald: Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 10:58:38 2017 InstallationDate: Installed on 2016-10-25 (352 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-10-04 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713555] Re: System tray (notification area) icons are placed in strange non-intuitive place - left buttom corner of window!
** Tags removed: artful i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1713555 Title: System tray (notification area) icons are placed in strange non- intuitive place - left buttom corner of window! Status in gnome-shell package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu 17.10. 2. Launch Ubuntu GNOME session 3. Install application which places its icon to the system tray (notification area) such as `hplip` or `transmission` 3. Try to find application icon in the system tray (notification area) - right top corner of the screen Expected results: system tray (notification area) is easy to find and placed on right top corner of the screen, does not overlap screen elements and windows Actual results: system tray (notification area) is difficult to find, it is placed on left bottom corner of the screen and automatically hides on start or after inactivity, or overlaps left bottom corner of the screen (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session-bin 3.25.90-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Mon Aug 28 21:25:51 2017 InstallationDate: Installed on 2017-08-26 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723080] Re: Caldav Issues with evolution 3.26
** Tags added: caldav ** Tags added: calendar evolution -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1723080 Title: Caldav Issues with evolution 3.26 Status in evolution package in Ubuntu: New Bug description: I noticed a series of issues with caldav when switching to Ubuntu 17.10. Everthing works fine with Ubuntu GNOME 17.04. Error message during ics import: "Cannot receive calendar objects: Failed to put data: HTTP error code 201 (Created): The server responded with an HTML page, which can mean there’s an error on the server or with the client request." The import successfully finished regardless. It's still a nuisance. Attempts to pick a date (calendar entry and tasks) are followed by the message: "Evolution want to inhibit shortcuts. You can restore shortcuts by pressing Shift-Ctrl-Escape" Creating new tasks: Same error message as for ics import. Tasks are only stored when date *and* time are specified. Error message needs to be ignored and window to be close with 'discard changes'. Update of calender appointments (external): just does not work Could not test handling of confirmations of meeting invites, yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1723080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713551] Re: System tray (notification area) icons are not shown on unity-session and gnome-classic
In final 17.10 bug is fixed. Thank you! ** Tags removed: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1713551 Title: System tray (notification area) icons are not shown on unity-session and gnome-classic Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Install application which places its icon to the system tray (notification area) such as `hplip` or `transmission` 3. Try to find application icon in the system tray (notification area) Expected results: Application icon is placed and shown in the system tray (notification area) Actual results: Application icon is not placed and not shown in the system tray (notification area) Info: $ export | grep "SESSION\|DESK" declare -x DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus" declare -x DESKTOP_AUTOSTART_ID="1017f889114f44fd1415039439458098940102050008" declare -x DESKTOP_SESSION="ubuntu-xorg" declare -x GDMSESSION="ubuntu-xorg" declare -x GNOME_DESKTOP_SESSION_ID="this-is-deprecated" declare -x GNOME_SESSION_XDG_SESSION_PATH="" declare -x GNOME_SHELL_SESSION_MODE="ubuntu" declare -x SESSION_MANAGER="local/artful:@/tmp/.ICE-unix/10205,unix/artful:/tmp/.ICE-unix/10205" declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME" declare -x XDG_SESSION_DESKTOP="ubuntu-xorg" declare -x XDG_SESSION_ID="11" declare -x XDG_SESSION_TYPE="x11" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.25.90-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 21:13:32 2017 InstallationDate: Installed on 2017-08-26 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render
** Changed in: gnome-control-center Status: Unknown => Confirmed ** Changed in: gnome-control-center Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1720400 Title: /usr/bin/gnome-control- center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: In Progress Bug description: 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.26.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1720400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725751] [NEW] file-roller crashed with SIGSEGV
Public bug reported: I dont'know but file roller crash after i'm unzipedd a file, only this. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: file-roller 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 21 18:13:49 2017 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: file-roller /tmp/mozilla_michele0/6852140faa233408de67-b8c19b115859afa9a6831ffd59f1d2e81985ccca.zip ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55d0e0020dc5: repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0x55d0e0020dc5) ok source "%es:(%rdi)" (0x55d0e002cdbf) ok destination "%ds:(%rsi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: file-roller crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1725751 Title: file-roller crashed with SIGSEGV Status in file-roller package in Ubuntu: New Bug description: I dont'know but file roller crash after i'm unzipedd a file, only this. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: file-roller 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 21 18:13:49 2017 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: file-roller /tmp/mozilla_michele0/6852140faa233408de67-b8c19b115859afa9a6831ffd59f1d2e81985ccca.zip ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55d0e0020dc5:repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0x55d0e0020dc5) ok source "%es:(%rdi)" (0x55d0e002cdbf) ok destination "%ds:(%rsi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: file-roller crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1725751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
On Sat, 21 Oct 2017, Norbert wrote: > At least `gparted` and `synaptic` do not run on default fresh clean > installation of Ubuntu 17.10. And as standard software installer does not: a) pass on querries from the package install (so that jackd can be properly installed for example) b) does not alert the user that a package they are installing has to remove another package the user still needs. This can leave the user with a crippled system. I have personally helped a number of people fix botched installs. I have never had complaints after the user installs synaptic. synaptic, though old and worn, is the only GUI installer that is safe to use in my experience. It is also fast and provides package information that allows trouble shooting package problems. These extras may be confusing for a new computer user or someone coming from windows, but points a and b above need to be addressed if new users are to keep using Ubuntu longer than a quick try. -- Len Ovens www.ovenwerks.net -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version:
[Desktop-packages] [Bug 1725653] Re: gnome-calendar crashed with SIGSEGV in g_str_hash()
*** This bug is a duplicate of bug 1724988 *** https://bugs.launchpad.net/bugs/1724988 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 #1724988, 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/1725653/+attachment/4981822/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725653/+attachment/4981824/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725653/+attachment/4981828/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725653/+attachment/4981829/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725653/+attachment/4981830/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725653/+attachment/4981831/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725653/+attachment/4981832/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1724988 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1725653 Title: gnome-calendar crashed with SIGSEGV in g_str_hash() Status in gnome-calendar package in Ubuntu: New Bug description: Random crash while calendar app window was open, but not in focus. I have gnome-calendar synced with my nextcloud installation. - Ubuntu 17.10 - gnome-calendar 3.26.2-1 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-calendar 3.26.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 13:18:34 2017 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2013-03-10 (1685 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f102af4a1f0 : movsbl (%rdi),%edx PC (0x7f102af4a1f0) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_str_hash() UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1725653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725236] Re: vulkaninfo fails with VK_ERROR_INCOMPATIBLE_DRIVER since 17.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1725236 Title: vulkaninfo fails with VK_ERROR_INCOMPATIBLE_DRIVER since 17.10 Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: I'm using a Dell XPS 9560 with a Geforce 1050. Back on 17.04 (libvulkan-dev-1.0.42.0, nvidia-375) I could run vulkaninfo and my own Vulkan applications without a problem but, after switching to 17.10 (libvulkan-dev-1.0.61.1, nvidia-384), running vulkaninfo now results in the error attached. In other words, I cannot run any Vulkan-based application anymore. I have tried using Vulkan's SDK 1.0.42.2 from LunarG's website without success. I have been tempted to try rolling back to nvidia-375 but not being so familiar with Linux, I am a bit worried that things might go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1725236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982076/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
I had similar problem with cursor jumping randomly on my Dell E5570 with Ubuntu 16.04, but the solution posted her by Juan Hernandez did not help. I found out that my Track Stick (stored in the middle of my keyboard) is source of the problem. When I disabled it the problem just disappeared. I guess the problem is with the driver for the track stick as it worked just OK on Windows. The following link was very helpful: https://cederlys.wordpress.com/2010/07/13/disabling-the-track-stick-in-ubuntu/#comment-694 I used the following to list the input devices: xinput list and to disable the track stick: xinput -set-prop "AlpsPS/2 ALPS DualPoint Stick" "Device Enabled" 0 Hovewer after reboot the trackpad is back on, so I added the above command to "Startup Applicationns" Regards -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks 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 Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
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 Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1245473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722298] Re: keyboard autorepeat not happening when I hold down any key
Workaround solution: sudo rmmod peaq_wmi sudo gedit /etc/modprobe.d/blacklist.conf #add at the end: #spams ^@ blacklist peaq_wmi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1722298 Title: keyboard autorepeat not happening when I hold down any key Status in gnome-terminal package in Ubuntu: Confirmed Bug description: The failure to auto repeat happens in all terminal apps I've tried in Artful. If I open a virtual console, it looks like a phantom is typing ^@ about once per second. This prevents successfully typing a password, and is probably what is breaking autorepeat in the GUI terminals, although they don't show the ^@. Gnome terminal and guake also can't stay scrolled up in the buffer for more than a second before popping back down to the bottom. This problem happens in the Ubuntu desktop or Gnome and it doesn't matter if I pick the xorg or default Wayland options. It happens under both the open source and proprietary nvidia drivers. It also happens with a newly created user with no home directory baggage. xev reports a constant stream of the following about the same frequency as the ^@ in console: KeyPress event, serial 62, synthetic NO, window 0x381, root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501), state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False If I boot into a recovery shell, the problem does _not_ appear. My system was built with a fresh install of 17.04, installed my usual packages, then upgrade to 17.10 when the problem began. I'm certain it was not present in 17.04 for the few days before I upgraded. There were similar bugs reported a decade ago, but didn't help me. Expectation: Hold down any key in terminal window. After a moment, the letter should repeat until key is released. Actually: Key will repeat 0 or a few times, but stop repeating before I release the key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 9 10:43:56 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1722298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725708] [NEW] Unable to use window menu in default GNOME applications (such as Gedit) - window minimizes on right click
Public bug reported: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Open Gedit text editor 3. Make right mouse click on its top window bar 4. Window drop-down menu is shown, mouse is over "Minimize" option Expected results: * window drop-down menu is opened, user is able to select option from it (for example move to other workspace or maximize) Actual results: * Gedit window got minimized instantly ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:27:44 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful wayland-session ** Also affects: gedit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725708 Title: Unable to use window menu in default GNOME applications (such as Gedit) - window minimizes on right click Status in gedit package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Open Gedit text editor 3. Make right mouse click on its top window bar 4. Window drop-down menu is shown, mouse is over "Minimize" option Expected results: * window drop-down menu is opened, user is able to select option from it (for example move to other workspace or maximize) Actual results: * Gedit window got minimized instantly ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:27:44 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1725708/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
** Tags removed: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) Status in HPLIP: Invalid Status in hplip package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Install hplip-gui 3. Launch GNOME session. 4. Get error message window with header "HPLIP Status Service" and text "No system tray detected on this system. Unable to start, exiting." Expected results: hp-systray is compatible with modern GNOME Actual results: hp-systray is not compatible with modern GNOME ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 (dbus://) went away, retrying! CurrentDesktop: GNOME Date: Sat Sep 2 14:10:19 2017 InstallationDate: Installed on 2017-08-26 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. UX32A PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697450] Re: Gnome Shell hangs at startup
FTR this still happens with gnome-shell 3.26.1-0ubuntu4 and kernel 4.13.0-16-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1697450 Title: Gnome Shell hangs at startup Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to install from the daily Artful desktop image (20170612). After boot, the gnome session hangs at startup, while the "zoom" animation is being shown. I have an intel card: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f780 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 I'm not sure how to debug this further, but I had similar issues with the installer from Zesty as well (see https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846) With Artful, at least it gets past the splash screen but then it hangs. Note that the system is currently running Yakkety with no issue. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-07-30 (71 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Tags: artful wayland-session Uname: Linux 4.8.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1697450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725667] [NEW] Wacom Intuos comic/draw/photo/art is not detected
Public bug reported: The tablet works but since it's not detected it's not possible to change settings from the control center. However, command-line commands such as ''xsetwacom'' do work to an extent (could map the output to a specific monitor but could not assign a key to all 4 buttons of the tablet, only 2). The configuration is lost each time the pc is restarted or if the tablet is removed and then replugged. (ps. This bug might be related to the fact that this tablet does not have a ''rubber'' on the other end of the pen, but I cannot confirm it). ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: tablet ui wacom -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725667 Title: Wacom Intuos comic/draw/photo/art is not detected Status in gnome-control-center package in Ubuntu: New Bug description: The tablet works but since it's not detected it's not possible to change settings from the control center. However, command-line commands such as ''xsetwacom'' do work to an extent (could map the output to a specific monitor but could not assign a key to all 4 buttons of the tablet, only 2). The configuration is lost each time the pc is restarted or if the tablet is removed and then replugged. (ps. This bug might be related to the fact that this tablet does not have a ''rubber'' on the other end of the pen, but I cannot confirm it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982084/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982085/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982088/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982086/+files/PulseList.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1712200/+attachment/4982087/+files/RfKill.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react on keyboard layout switching Actual results: * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thanos25842 F pulseaudio /dev/snd/controlC0: thanos25842 F pulseaudio /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.2.1 dev wlp4s7 proto static metric 600 169.254.0.0/16 dev wlp4s7 scope link metric 1000 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1712200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712902] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1712902 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: Hello, I do not know what happened Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: ibus 1.5.14-2ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 24 15:59:30 2017 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2017-07-05 (49 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim --address unix:tmpdir=/tmp/ibus Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to artful on 2017-07-05 (49 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1712902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713347] Re: Firefox highligts textarea on mouse click (focus) in orange, it distracts user
** Tags removed: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1713347 Title: Firefox highligts textarea on mouse click (focus) in orange, it distracts user Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu 17.10. 2. Launch Firefox 3. Open website with textarea (for example launchpad). 4. Click on textarea to start typing. 5. Textarea fills with orange background color and it distracts user (see screenshot). Expected results: Textarea has white (or other defined background), which does not change on mouse click. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 50.1.0+build2-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: artful 1762 F pulseaudio BuildID: 20161213224650 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Aug 27 20:29:36 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) IpRoute: default via 192.168.3.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.3.0/24 dev wlp2s0 proto kernel scope link src 192.168.3.15 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: GNOME Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=50.1.0/20161213224650 (In use) RelatedPackageVersions: gnome-shell 3.24.3-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1713347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722298] Re: keyboard autorepeat not happening when I hold down any key
"sudo rmmod peaq_wmi" also fixed the problem for me (thanks Ronaldo!). peaq_wmi was spamming ^@ non stop. It made the system complete nonoperational, insane lag and it crashed after some time when a text input appeared. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1722298 Title: keyboard autorepeat not happening when I hold down any key Status in gnome-terminal package in Ubuntu: Confirmed Bug description: The failure to auto repeat happens in all terminal apps I've tried in Artful. If I open a virtual console, it looks like a phantom is typing ^@ about once per second. This prevents successfully typing a password, and is probably what is breaking autorepeat in the GUI terminals, although they don't show the ^@. Gnome terminal and guake also can't stay scrolled up in the buffer for more than a second before popping back down to the bottom. This problem happens in the Ubuntu desktop or Gnome and it doesn't matter if I pick the xorg or default Wayland options. It happens under both the open source and proprietary nvidia drivers. It also happens with a newly created user with no home directory baggage. xev reports a constant stream of the following about the same frequency as the ^@ in console: KeyPress event, serial 62, synthetic NO, window 0x381, root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501), state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False If I boot into a recovery shell, the problem does _not_ appear. My system was built with a fresh install of 17.04, installed my usual packages, then upgrade to 17.10 when the problem began. I'm certain it was not present in 17.04 for the few days before I upgraded. There were similar bugs reported a decade ago, but didn't help me. Expectation: Hold down any key in terminal window. After a moment, the letter should repeat until key is released. Actually: Key will repeat 0 or a few times, but stop repeating before I release the key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 9 10:43:56 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1722298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725696] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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 #1505409, 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/1725696/+attachment/4982215/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725696/+attachment/4982217/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725696/+attachment/4982220/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725696/+attachment/4982221/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725696/+attachment/498/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725696/+attachment/4982223/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725696/+attachment/4982224/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725696 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: Happend after a fresh boot into the system ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Oct 20 02:25:37 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725712] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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 #1505409, 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/1725712/+attachment/4982327/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725712/+attachment/4982329/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725712/+attachment/4982332/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725712/+attachment/4982333/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725712/+attachment/4982334/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725712/+attachment/4982335/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725712/+attachment/4982336/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725712 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: This is just my take on bug reporting given by an automatic crash report request. But I have a clue on how would this thing be improved. I think the weather applet in the GNOME Shell when I click the time- buttoned notifications button, the weather tends to crash. After recovery, the weather applet in the notifications pane (right side, after the world clocks) delays - could use too much resources. but I think it could have been efficient. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 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.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Oct 21 22:21:22 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
Rebuilding the version for Xenial, 0.17+16.04.20151125-0ubuntu1, for artful 17.10 seems to produce a working signon via KDE's systemsetting See test rebuild in: https://launchpad.net/~rikmills/+archive/ubuntu /kio-grive Rebuilding any later ubuntu published versions fails to produce a working version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1070873 Title: kde-telepathy, impossible to connect to gmail accounts Status in meta-kde-telepathy package in Ubuntu: Confirmed Status in signon-ui package in Ubuntu: Confirmed Bug description: Im running ubuntu 12.10 quantal and i have installed kde, when running kde-telepathy i have added a gmail account, and after entering the password it has revealed impossible to connect to it, it always says that the password is wrong when that is false. When using empathy, i have removed the gmail account and have added it again, now appears a XMLL window asking ubuntu permission to conenct to it, and now i was able to conenct to the gmail account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725720] Re: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()
*** This bug is a duplicate of bug 1724901 *** https://bugs.launchpad.net/bugs/1724901 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 #1724901, 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/1725720/+attachment/4982425/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725720/+attachment/4982428/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725720/+attachment/4982438/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725720/+attachment/4982440/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725720/+attachment/4982441/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725720/+attachment/4982442/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725720/+attachment/4982443/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1724901 Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1725720 Title: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Crashed after logging in loading Ubuntu 17.10 for the first time after upgrade. Loaded GNOME with Xorg interface. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Oct 21 10:38:46 2017 DistUpgraded: 2017-10-21 10:37:03,085 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.10.0-37-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21d0] NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d0] InstallationDate: Installed on 2016-11-15 (340 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 04f2:b221 Chicony Electronics Co., Ltd integrated camera Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 42365H2 ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: RRProviderAutoConfigGpuScreen () InitOutput () ?? () __libc_start_main (main=0x55bba761aaf0, argc=11, argv=0x7ffe0f36a4b8, init=, fini=, rtld_fini=, stack_end=0x7ffe0f36a4a8) at ../csu/libc-start.c:308 _start () Title: Xorg crashed with SIGABRT in
[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
Unable to use Ctrl+Shift+key shortcuts (for example Ctrl+Shift+arrows for selecting text) on fresh clean Ubuntu 17.10 final with all updates installed if keyboard layout switching is set to Ctrl+Shift. Both on Xorg and Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1245473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725416] Re: Elantech touch pad device not detected/working properly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725416 Title: Elantech touch pad device not detected/working properly Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I just upgraded to Ubuntu 17.10 (hooray, GNOME!). But there are some quirks. Under Unity/Ubuntu 17.04 my built-in Touchpad worked flawlessly - especially the "natural scrolling" mode was working well. As I saw under Ubuntu Gnome 17.04, the corresponding setting in gnome- control-center "Natural scrolling" just targets the mouse and has no effect on the touchpad. I can see the touchpad using "xinput list": ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=14 [slave pointer (2)] ⎜ ↳ Logitech Performance MX id=12 [slave pointer (2)] alongside my Logitech mouse on a Unifying receiver. Is there any chance that this touchpad is detected? Or should I forget about that (WONTFIX) as Xorg is already unsupported? ATM I am using the prop. nvidia drivers. Currently uninstalling them to see if Wayland is starting using nouveau... Thanks. What else do you need from me? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 20:20:04 2017 InstallationDate: Installed on 2016-11-27 (327 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725728] [NEW] package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should
Public bug reported: Errors were encountered while processing: libwinpr-library0.1:amd64 libfreerdp-common1.1.0:amd64 libfreerdp-core1.1:amd64 libfreerdp-cache1.1:amd64 libfreerdp-client1.1:amd64 libfreerdp-gdi1.1:amd64 libfreerdp-plugins-standard:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Oct 21 18:13:08 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libwinpr-library0.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ... dpkg: error processing package libwinpr-library0.1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-09-27 (23 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: freerdp Title: package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: freerdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1725728 Title: package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in freerdp package in Ubuntu: New Bug description: Errors were encountered while processing: libwinpr-library0.1:amd64 libfreerdp-common1.1.0:amd64 libfreerdp-core1.1:amd64 libfreerdp-cache1.1:amd64 libfreerdp-client1.1:amd64 libfreerdp-gdi1.1:amd64 libfreerdp-plugins-standard:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Oct 21 18:13:08 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libwinpr-library0.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ... dpkg: error processing package libwinpr-library0.1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-09-27 (23 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: freerdp Title: package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1725728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725416] Re: Elantech touch pad device not detected/working properly
Dell E6540 with AMD graphics, same thing for me. Works fine with 17.04. Also, now I cannot enable both two finger scrolling and edgescrolling. Everything else (mouse, window sidescroll, arrow down) scrolls down when used, but not touchpad. Damn frustrating. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725416 Title: Elantech touch pad device not detected/working properly Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I just upgraded to Ubuntu 17.10 (hooray, GNOME!). But there are some quirks. Under Unity/Ubuntu 17.04 my built-in Touchpad worked flawlessly - especially the "natural scrolling" mode was working well. As I saw under Ubuntu Gnome 17.04, the corresponding setting in gnome- control-center "Natural scrolling" just targets the mouse and has no effect on the touchpad. I can see the touchpad using "xinput list": ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=14 [slave pointer (2)] ⎜ ↳ Logitech Performance MX id=12 [slave pointer (2)] alongside my Logitech mouse on a Unifying receiver. Is there any chance that this touchpad is detected? Or should I forget about that (WONTFIX) as Xorg is already unsupported? ATM I am using the prop. nvidia drivers. Currently uninstalling them to see if Wayland is starting using nouveau... Thanks. What else do you need from me? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 20:20:04 2017 InstallationDate: Installed on 2016-11-27 (327 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683512] Re: No libcuda.so.1 after upgrading to 381-driver
The Nvidia driver 375.66 fixed the window artifact problems, so use that version to avoid the missing link problem. You can use apt-file search libcuda.so.1 to find which nvidia driver packages contain the file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1683512 Title: No libcuda.so.1 after upgrading to 381-driver Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in theano package in Ubuntu: Confirmed Bug description: I had a problem with window edges after waking from suspend - see here: https://askubuntu.com/questions/896221/strange-artifacts-along- window-borders-after-waking-computer-from-sleep-mode/ For this reason I upgraded to the newer driver, from 375.39 to 381.09. I have posted this question on AskUbuntu, with some extra information! https://askubuntu.com/questions/905993/missing-libcuda-so-1-file-after-upgrading-to-newest-nvidia-driver Since upgrading, I have had to reinstall the Cuda Toolkit 8.0 (and CUDNN v5.1), however there seems to be a driver file missing, which prevents me from installing both Tensorflow and the gputools package in R, which build upon the Cuda Toolkit, which in turn needs the missing libcuda.so.1 file. Neither Tensorflow no gputools are able to locate the file: libcuda.so.1. Here is a similar issue, but with older drivers involved: https://github.com/tensorflow/tensorflow/issues/4078 I have read that I could possibly create this file as it is a symlink, however I would prefer not to, as I do not know what other dependencies exist. Example of possible workaround: http://stackoverflow.com/questions/41890549/tensorflow-cannot-open-libcuda-so-1 I am running Ubuntu 16.04. Can somebody see why this file is missing or propose a stable solution? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1683512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725729] Re: Trying to add a google account with the kubuntu online account manager
*** This bug is a duplicate of bug 1723230 *** https://bugs.launchpad.net/bugs/1723230 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 #1723230, 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/1725729/+attachment/4982528/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725729/+attachment/4982530/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725729/+attachment/4982533/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725729/+attachment/4982534/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725729/+attachment/4982535/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725729/+attachment/4982536/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725729/+attachment/4982537/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1723230 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1725729 Title: Trying to add a google account with the kubuntu online account manager Status in signon-ui package in Ubuntu: New Bug description: no account configured fresh kubuntu 17.10 install or live usb. Also seen on kubuntu 17.04 when trying to use the instant messenger embedded with kubuntu, icon on bottom right of the screen, I first need to add an existing google account. In the "online accounts" tab, I click on "create", then select "google". after a few seconds I get the following error: Il y a une eu une erreur durant le traitement de la requête : userActionFinished error: 2 -> there has been an error while processing the request : userActionFinished error: 2 Adding an existing jabber account works fine. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: signon-ui-x11 0.17+17.10.20170606-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Oct 21 17:10:15 2017 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2017-09-23 (28 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/signon-ui ProcEnviron: LANGUAGE=fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f50af6585a0 <_ZN7QWindow11setModalityEN2Qt14WindowModalityE>: mov0x8(%rdi),%rax PC (0x7f50af6585a0) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: signon-ui StacktraceTop: QWindow::setModality(Qt::WindowModality) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () ?? () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1725729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725728] Re: package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should
Help me solve this,it affects installation of packages too in that they are installed half and its also making my machine hung a lot Thank you team,I'm new to linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1725728 Title: package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in freerdp package in Ubuntu: New Bug description: Errors were encountered while processing: libwinpr-library0.1:amd64 libfreerdp-common1.1.0:amd64 libfreerdp-core1.1:amd64 libfreerdp-cache1.1:amd64 libfreerdp-client1.1:amd64 libfreerdp-gdi1.1:amd64 libfreerdp-plugins-standard:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Oct 21 18:13:08 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libwinpr-library0.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ... dpkg: error processing package libwinpr-library0.1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-09-27 (23 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: freerdp Title: package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1725728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725728] Re: package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1725728 Title: package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in freerdp package in Ubuntu: New Bug description: Errors were encountered while processing: libwinpr-library0.1:amd64 libfreerdp-common1.1.0:amd64 libfreerdp-core1.1:amd64 libfreerdp-cache1.1:amd64 libfreerdp-client1.1:amd64 libfreerdp-gdi1.1:amd64 libfreerdp-plugins-standard:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Oct 21 18:13:08 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libwinpr-library0.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ... dpkg: error processing package libwinpr-library0.1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-09-27 (23 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: freerdp Title: package libwinpr-library0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1725728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1718717 Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() Status in CUPS: Fix Released Status in cups package in Ubuntu: Confirmed Bug description: after updates of cups-filter and reboot ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Thu Sep 21 17:43:42 2017 ExecutablePath: /usr/sbin/cupsd Lpstat: device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21 device for PDF: cups-pdf:/ MachineType: Dell Inc. OptiPlex 960 Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer (w/ options) HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended) ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f32dc0c7954: cmpq $0x0,(%rdi) PC (0x7f32dc0c7954) ok source "$0x0" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () ?? () ?? () ?? () Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago) UserGroups: dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0Y958C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1718717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725729] Re: Trying to add a google account with the kubuntu online account manager
*** This bug is a duplicate of bug 1723230 *** https://bugs.launchpad.net/bugs/1723230 hi, I can't find bug #1723230. Is there an error in the number ? otherwise, how can I view and follow it ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1725729 Title: Trying to add a google account with the kubuntu online account manager Status in signon-ui package in Ubuntu: New Bug description: no account configured fresh kubuntu 17.10 install or live usb. Also seen on kubuntu 17.04 when trying to use the instant messenger embedded with kubuntu, icon on bottom right of the screen, I first need to add an existing google account. In the "online accounts" tab, I click on "create", then select "google". after a few seconds I get the following error: Il y a une eu une erreur durant le traitement de la requête : userActionFinished error: 2 -> there has been an error while processing the request : userActionFinished error: 2 Adding an existing jabber account works fine. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: signon-ui-x11 0.17+17.10.20170606-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Oct 21 17:10:15 2017 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2017-09-23 (28 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/signon-ui ProcEnviron: LANGUAGE=fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f50af6585a0 <_ZN7QWindow11setModalityEN2Qt14WindowModalityE>: mov0x8(%rdi),%rax PC (0x7f50af6585a0) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: signon-ui StacktraceTop: QWindow::setModality(Qt::WindowModality) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () ?? () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1725729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725734] [NEW] Indicator size is too small
Public bug reported: The indicator size in 17.10 is too small to be comfortable: https://i.stack.imgur.com/r5Eza.png ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:28:50 2017 DisplayManager: lightdm EcryptfsInUse: Yes InstallationDate: Installed on 2012-03-23 (2037 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725734 Title: Indicator size is too small Status in gnome-shell package in Ubuntu: New Bug description: The indicator size in 17.10 is too small to be comfortable: https://i.stack.imgur.com/r5Eza.png ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:28:50 2017 DisplayManager: lightdm EcryptfsInUse: Yes InstallationDate: Installed on 2012-03-23 (2037 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725741] Re: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()
*** This bug is a duplicate of bug 1631434 *** https://bugs.launchpad.net/bugs/1631434 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 #1631434, 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/1725741/+attachment/4982649/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725741/+attachment/4982651/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725741/+attachment/4982654/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725741/+attachment/4982655/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725741/+attachment/4982656/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725741/+attachment/4982657/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725741/+attachment/4982658/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1631434 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725741 Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect() Status in gnome-control-center package in Ubuntu: New Bug description: I don't know what happened ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 13:40:05 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f11c5183b59:mov(%rsi),%rsi PC (0x7f11c5183b59) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725647] Re: gnome-software crashed with SIGSEGV in g_io_channel_shutdown()
*** This bug is a duplicate of bug 1725453 *** https://bugs.launchpad.net/bugs/1725453 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 #1725453, 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/1725647/+attachment/4981762/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725647/+attachment/4981764/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725647/+attachment/4981767/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725647/+attachment/4981768/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725647/+attachment/4981769/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725647/+attachment/4981770/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725647/+attachment/4981771/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1725453 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1725647 Title: gnome-software crashed with SIGSEGV in g_io_channel_shutdown() Status in gnome-software package in Ubuntu: New Bug description: did'nt look closely, sorry:/ but it was on a fresh install of ubuntu, first software manager failed (twice) to install opera deb. then I apt-get update, retried and it worked, but strange debconf windows appeared and timed out. Report button bringed me here. Hope it helps. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 13:01:00 2017 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu2 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb7dc4c252f:cmpq $0x0,0x8(%rdi) PC (0x7fb7dc4c252f) ok source "$0x0" ok destination "0x8(%rdi)" (0xb4df23609be43d2a) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: g_io_channel_shutdown () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-software crashed with SIGSEGV in g_io_channel_shutdown() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1725647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1438014] Re: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()
** Tags added: bugpattern-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1438014 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() Status in gnome-terminal package in Ubuntu: Confirmed Bug description: I put my laptop to sleep for an hour or so; when I restored it, gnome- terminal had crashed. It did not do this the previous time I suspended my laptop today, so I doubt that's immediately related. This crash can be reproduced by setting a shortcut in preferences. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 30 00:19:43 2015 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2014-02-03 (419 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f98e2afbf1f: testb $0x4,0x16(%rax) PC (0x7f98e2afbf1f) ok source "$0x4" ok destination "0x16(%rax)" (0xbcae) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel (widget=0x2580c30) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382 window_group_cleanup_grabs (group=, window=window@entry=0x252a230) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110 gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169 gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1438014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712200] Re: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland
** Description changed: + + Steps to reproduce: + 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation + 3. Boot into installed system and log-in + 4. Try to change keyboard layout - what is interesting both keyboard shortcuts -and switch layouts. + 5. Open Firefox + 6. Change keyboard layout with + + + Expected results: + * keyboard layout is switched, Firefox does not react on keyboard layout switching + + Actual results: + * during switching of keyboard layout (on clicking key) Firefox shows its mnemonics (underlines in menu) and distracts user. After pressing key keyboard layout is switched, but focus is placed on Firefox menubar. So user needs to change the focus with keyboard (for example key) or mouse click. + + + Original bug description below: I'm on Ubuntu 17.10 with artful-proposed enabled. Changing keyboard layout with alt+shift always triggers "show menu"on Wayland, which makes firefox unusable for users who don't know how to disable the value "ui.key.menuAccessKeyFocuses" from about:config. Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses" to false by default? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 54.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: thanos25842 F pulseaudio - /dev/snd/controlC0: thanos25842 F pulseaudio - /dev/snd/controlC1: thanos25842 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: thanos25842 F pulseaudio + /dev/snd/controlC0: thanos25842 F pulseaudio + /dev/snd/controlC1: thanos25842 F pulseaudio BuildID: 20170616154447 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Aug 21 23:42:26 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: - default via 192.168.2.1 dev wlp4s7 proto static metric 600 - 169.254.0.0/16 dev wlp4s7 scope link metric 1000 - 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 + default via 192.168.2.1 dev wlp4s7 proto static metric 600 + 169.254.0.0/16 dev wlp4s7 scope link metric 1000 + 192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use) RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7d dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1712200 Title: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 from final ISO-image (cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]), select Russian keyboard layout on installation 3. Boot into installed system and log-in 4. Try to change keyboard layout - what is interesting both keyboard shortcuts - and switch layouts. 5. Open Firefox 6. Change keyboard layout with Expected results: * keyboard layout is switched, Firefox does not react
[Desktop-packages] [Bug 1694284] Re: 'Recently used' places is not shown in Firefox dialogs (Open, Save, Save As, downloads save)
Ubuntu 17.10 final with all updates - bug is not fixed. Pressinghelps. What would be more user-friendly? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1694284 Title: 'Recently used' places is not shown in Firefox dialogs (Open, Save, Save As, downloads save) Status in firefox package in Ubuntu: New Bug description: Steps to reproduce: 1. Installed firefox 53.0.3 from Ubuntu Xenial repositories. 2. Tried to Save Link As, or Open File ( ), or download file. Actual results: GtkFileChooserDialog is opened without "Recently used" places zone. Expected results: For usability reasons Firefox should have GtkFileChooserDialog with "Recently used" places enabled. See https://developer.gnome.org/gtk3/stable/filechooser.png or https://developer.gnome.org/gtk2/stable/filechooser.png as examples. User may want so save/open file to/from last used location. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 53.0.3+build1-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nikolay2656 F pulseaudio BuildID: 20170524180630 Channel: Unavailable CurrentDesktop: MATE Date: Mon May 29 18:25:13 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-02-07 (1206 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) IpRoute: default via 192.168.3.1 dev wlan1 proto static metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.3.0/24 dev wlan1 proto kernel scope link src 192.168.3.8 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js [Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js [Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js Profiles: Profile0 (Default) - LastVersion=53.0.3/20170524180630 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2017-04-15 (43 days ago) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694284/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
At least `gparted` and `synaptic` do not run on default fresh clean installation of Ubuntu 17.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage:
[Desktop-packages] [Bug 1725694] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1720768 *** https://bugs.launchpad.net/bugs/1720768 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 #1720768, 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/1725694/+attachment/4982199/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725694/+attachment/4982201/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725694/+attachment/4982204/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725694/+attachment/4982205/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725694/+attachment/4982206/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725694/+attachment/4982207/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725694/+attachment/4982208/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1720768 gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subprocess\n"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725694 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: On start-up using GNOME classic interface, Ubuntu 17.10 64-bit. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Oct 20 16:14:42 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725691] Re: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1724894 *** https://bugs.launchpad.net/bugs/1724894 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 #1724894, 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/1725691/+attachment/4982157/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725691/+attachment/4982159/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725691/+attachment/4982163/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725691/+attachment/4982164/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725691/+attachment/4982165/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725691/+attachment/4982166/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725691/+attachment/4982167/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1724894 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725691 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() Status in gnome-control-center package in Ubuntu: New Bug description: don't work。 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 21:23:03 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-01 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x557a5c3e3a0a:mov(%rax),%rdi PC (0x557a5c3e3a0a) ok source "(%rax)" (0x005f) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () 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 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725691/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725698] [NEW] Size decreases when cycling between full-screen mode using F11
Public bug reported: Launch an gnome-terminal and cycle between full screen and normal by pressing F11 twice. The original size of the terminal is not restored. Doing this multiple times, the window continues to shrink. This did not occur on 17.04 or earlier. I use this regularly as part of my workflow. Obviously, this is a minor issue, but it sure is annoying. This bug does not exist in terminator FWIW. I'd prefer not to switch to terminator, however. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 09:49:18 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (546 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1725698 Title: Size decreases when cycling between full-screen mode using F11 Status in gnome-terminal package in Ubuntu: New Bug description: Launch an gnome-terminal and cycle between full screen and normal by pressing F11 twice. The original size of the terminal is not restored. Doing this multiple times, the window continues to shrink. This did not occur on 17.04 or earlier. I use this regularly as part of my workflow. Obviously, this is a minor issue, but it sure is annoying. This bug does not exist in terminator FWIW. I'd prefer not to switch to terminator, however. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 09:49:18 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (546 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725702] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 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 #1706097, 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/1725702/+attachment/4982246/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725702/+attachment/4982248/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725702/+attachment/4982252/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725702/+attachment/4982253/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725702/+attachment/4982254/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725702/+attachment/4982255/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725702/+attachment/4982256/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1706097 gvfsd-mtp crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1725702 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: 1 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 16:51:53 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.9 /org/gtk/gvfs/exec_spaw/4 SegvAnalysis: Segfault happened at: 0x7fa27870e5a9:mov0x18(%rax),%rax PC (0x7fa27870e5a9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev nopasswdlogin plugdev sambashare scanner sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1725702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725706] [NEW] Unable to change window state with keyboard in gnome shell (such as Always on _Top - <Alt+Space+t>)
Public bug reported: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Open any windowed application such as Nautilus or `gnome-terminal` 3. Clickto show current window settings 4. Try to set "Always on Top" property with keyboard shortcut () Expected results: * window reacts on and set on top as requested Actual results: * window does not react on Notes: "Always on Top" is just an illustration. Mnemonics for other (Minimize, Maximize, Move, Resize, Always on Visible Workspace, Move to workspace down, etc) do not defined and do work too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:18:12 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725706 Title: Unable to change window state with keyboard in gnome shell (such as Always on _Top - ) Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Open any windowed application such as Nautilus or `gnome-terminal` 3. Click to show current window settings 4. Try to set "Always on Top" property with keyboard shortcut () Expected results: * window reacts on and set on top as requested Actual results: * window does not react on Notes: "Always on Top" is just an illustration. Mnemonics for other (Minimize, Maximize, Move, Resize, Always on Visible Workspace, Move to workspace down, etc) do not defined and do work too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:18:12 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725721] [NEW] gnome-panel in gnome-flashback-metacity session does not update time, indicators ; unable to click on gear button
Public bug reported: Steps to reproduce: 1. Install Ubuntu 17.10 2. Install `gnome-panel` and `gnome-session-flashback` packages 3. Reboot 4. Login to GNOME FlashBack session 5. Do some work (the last I did was `sudo dpkg-reconfigure keyboard-configuration`) Expected results: * gnome-panel is responsible, updates time, user is able to click on indicators (network, keyboard, bluetooth, battery, clock) and on gear button Actual results: * gnome-panel reacts only in left side (Applications menu and Places menu), but not in the right side (indicators are froze, user is unable to click on gear button) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Sat Oct 21 17:52:54 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 'indicators', 'show-destkop', 'window-list', 'workspace-switcher']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 'bottom-panel']" InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1725721 Title: gnome-panel in gnome-flashback-metacity session does not update time, indicators ; unable to click on gear button Status in gnome-panel package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Install `gnome-panel` and `gnome-session-flashback` packages 3. Reboot 4. Login to GNOME FlashBack session 5. Do some work (the last I did was `sudo dpkg-reconfigure keyboard-configuration`) Expected results: * gnome-panel is responsible, updates time, user is able to click on indicators (network, keyboard, bluetooth, battery, clock) and on gear button Actual results: * gnome-panel reacts only in left side (Applications menu and Places menu), but not in the right side (indicators are froze, user is unable to click on gear button) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Sat Oct 21 17:52:54 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 'indicators', 'show-destkop', 'window-list', 'workspace-switcher']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 'bottom-panel']" InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1725721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1076880] Re: network speed incorrectly reported in System Monitor using VPN
Still happens on 17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1076880 Title: network speed incorrectly reported in System Monitor using VPN Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: looks similar to bug #957617 When using a VPN and monitoring up and download speeds shown in System monitor (ubuntu 12.04), then the indicated speeds are much greater than they apparently should be. When VPN is stoped and normal connection used, then indicate speeds are as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1076880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
I can confirm this problem for a fresh installation of Ubuntu 17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1663528 Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1663528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085706] Re: pam_ecryptfs: seteuid error
i3lock on Ubuntu 17.10 effected Oct 21 11:17:25 Nebula i3lock[4390]: pam_ecryptfs: seteuid error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: pam_ecryptfs: seteuid error Status in eCryptfs: Confirmed Status in GNOME Screensaver: New Status in ecryptfs-utils package in Ubuntu: Triaged Status in gnome-screensaver package in Ubuntu: Triaged Status in kscreenlocker package in Ubuntu: Confirmed Status in plasma-workspace package in Ubuntu: Confirmed Status in gnome-screensaver package in Debian: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1085706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1076880] Re: network speed incorrectly reported in System Monitor using VPN
Still happens on 17.10. Reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=789303 ** Bug watch added: GNOME Bug Tracker #789303 https://bugzilla.gnome.org/show_bug.cgi?id=789303 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1076880 Title: network speed incorrectly reported in System Monitor using VPN Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: looks similar to bug #957617 When using a VPN and monitoring up and download speeds shown in System monitor (ubuntu 12.04), then the indicated speeds are much greater than they apparently should be. When VPN is stoped and normal connection used, then indicate speeds are as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1076880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721189] Re: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
Rachel, I agree. Please subscribe to [1]. Changing this back to "solved". [1] https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1725588 ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1721189 Title: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface Status in thunderbird package in Ubuntu: Fix Released Bug description: Just received the update 1:52.4.0+build1-0ubuntu1 which has a broken user interface. See attached screenshot. Downgraded to thunderbird_52.3.0+build1-0ubuntu0.17.04.1_amd64.deb which solved the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725588] [NEW] Thunderbird: tab borders Preferences > Security missing
Public bug reported: Potentially related with [1]. Reproducible in TB 1:52.4.0+build1-0ubuntu2 with default theme for both TB and Ubuntu. Screenshot attached. [1] https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189 ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Attachment added: "missing tab borders.png" https://bugs.launchpad.net/bugs/1725588/+attachment/4981185/+files/missing%20tab%20borders.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1725588 Title: Thunderbird: tab borders Preferences > Security missing Status in thunderbird package in Ubuntu: New Bug description: Potentially related with [1]. Reproducible in TB 1:52.4.0+build1-0ubuntu2 with default theme for both TB and Ubuntu. Screenshot attached. [1] https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1725588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725593] [NEW] 17.10 putty and synaptic Could not open X display Erreur de segmentation (core dumped)
Public bug reported: these two apps don t show up putty No protocol specified ** (putty:19873): WARNING **: Could not open X display Erreur de segmentation (core dumped) synaptic No protocol specified ** (synaptic:19979): WARNING **: Could not open X display Erreur de segmentation (core dumped) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1725593 Title: 17.10 putty and synaptic Could not open X display Erreur de segmentation (core dumped) Status in network-manager package in Ubuntu: New Bug description: these two apps don t show up putty No protocol specified ** (putty:19873): WARNING **: Could not open X display Erreur de segmentation (core dumped) synaptic No protocol specified ** (synaptic:19979): WARNING **: Could not open X display Erreur de segmentation (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725590] Re: gvfsd-smb-browse crashed with SIGABRT in _talloc_pooled_object()
*** This bug is a duplicate of bug 1541335 *** https://bugs.launchpad.net/bugs/1541335 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 #1541335, 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/1725590/+attachment/4981199/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725590/+attachment/4981201/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725590/+attachment/4981204/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725590/+attachment/4981205/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725590/+attachment/4981206/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725590/+attachment/4981207/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725590/+attachment/4981208/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1541335 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1725590 Title: gvfsd-smb-browse crashed with SIGABRT in _talloc_pooled_object() Status in gvfs package in Ubuntu: New Bug description: I don't know what type of bug it is, I can't write something about it ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 09:34:54 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gvfs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2 _talloc_pooled_object () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2 _tevent_req_create () from /usr/lib/x86_64-linux-gnu/libtevent.so.0 ?? () from /usr/lib/x86_64-linux-gnu/samba/libgse.so.0 node_status_query_send () from /usr/lib/x86_64-linux-gnu/samba/libgse.so.0 Title: gvfsd-smb-browse crashed with SIGABRT in _talloc_pooled_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1725590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720768] Re: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subpr
yes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1720768 Title: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subprocess\n"] Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/bcc0785597c2485f446db82f8dfa08eb7dd972a5 --- Logged in with one new user, switched to login under another account. Was logged in for a few moments then got kicked out - session crashed. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Oct 2 10:39:27 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-08-02 (60 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725597] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1631434 *** https://bugs.launchpad.net/bugs/1631434 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 #1631434, 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/1725597/+attachment/4981261/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725597/+attachment/4981263/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725597/+attachment/4981267/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725597/+attachment/4981268/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725597/+attachment/4981269/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725597/+attachment/4981270/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725597/+attachment/4981271/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1631434 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725597 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: After reboot gnome-control-center crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 09:49:17 2017 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center display SegvAnalysis: Segfault happened at: 0x7f8df2012b59:mov(%rsi),%rsi PC (0x7f8df2012b59) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_renderer_connect () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-09-19 (31 days ago) UserGroups: adm audio cdrom dip fax lp lpadmin lxd plugdev pulse sambashare sudo video www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
On the Skull Canyon NUC I'm currently at the versions are: libmutter 3.26.1-2ubuntu1 and gnome-shell 3.26.1-0ubuntu4. I have a _usr_bin_gnome-shell.1001.crash, but it's quite large even after compressing it. I'll see if launchpad will accept the file. ** Attachment added: "Freshly generated gnome-shell crash file after switching screen off and on" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/+attachment/4981367/+files/_usr_bin_gnome-shell.1001.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi all, Originally I was reporting bug 1717170, about session crash after monitor disconnect/switch-off/input change on desktop PC and the bug was fixed according to bug tracker. But now, after gnome-shell and mutter update, the crash goes worse. Now it is not just session kick-out but complete crash. Same events can be used to reproduce the crash. This time also crash files was created. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 13:52:07 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-09-11 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f475acbac30 : movss 0x38(%rdi),%xmm0 PC (0x7f475acbac30) ok source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_logical_monitor_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_sync_state () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725626] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1556601 *** https://bugs.launchpad.net/bugs/1556601 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 #1556601, 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/1725626/+attachment/4981503/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725626/+attachment/4981505/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725626/+attachment/4981508/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725626/+attachment/4981509/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725626/+attachment/4981510/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725626/+attachment/4981511/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725626/+attachment/4981512/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1556601 gnome-shell crashed with signal 5 in _XIOError() from _XReply() from XSync() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725626 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: I did start firefox, nothing else ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Oct 21 11:40:07 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=de_DE:de:en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 XSync () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725588] Re: Thunderbird: tab borders Preferences > Security missing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1725588 Title: Thunderbird: tab borders Preferences > Security missing Status in thunderbird package in Ubuntu: Confirmed Bug description: Potentially related with [1]. Reproducible in TB 1:52.4.0+build1-0ubuntu2 with default theme for both TB and Ubuntu. Screenshot attached. [1] https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1725588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723130] Re: totem crashed with SIGSEGV in wl_proxy_add_listener()
** Changed in: totem (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1723130 Title: totem crashed with SIGSEGV in wl_proxy_add_listener() Status in totem package in Ubuntu: New Bug description: I just opened the video from nautilus with double click ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 16:06:22 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-09-17 (24 days ago) InstallationMedia: It ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=es_ES.UTF-8 SegvAnalysis: Segfault happened at: 0x7f368b77c77c: testb $0x4,0x28(%rdi) PC (0x7f368b77c77c) ok source "$0x4" ok destination "0x28(%rdi)" (0x0028) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: wl_proxy_add_listener () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_onscreen_swap_buffers_with_damage () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 Title: totem crashed with SIGSEGV in wl_proxy_add_listener() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1723130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725611] Re: gimp-2.8 crashed with SIGSEGV in pango_ot_info_list_scripts()
*** This bug is a duplicate of bug 1694977 *** https://bugs.launchpad.net/bugs/1694977 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 #1694977, 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/1725611/+attachment/4981401/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725611/+attachment/4981403/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725611/+attachment/4981406/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725611/+attachment/4981407/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725611/+attachment/4981408/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725611/+attachment/4981409/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725611/+attachment/4981410/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1694977 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1725611 Title: gimp-2.8 crashed with SIGSEGV in pango_ot_info_list_scripts() Status in gimp package in Ubuntu: New Bug description: gimp crash was also using chrome and clementine at the time ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gimp 2.8.20-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 21 04:18:41 2017 ExecutablePath: /usr/bin/gimp-2.8 ProcCmdline: gimp-2.8 /home/username/Downloads/str/yttwi4b.png ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f67087b734f: mov0x20(%r12),%rdi PC (0x7f67087b734f) ok source "0x20(%r12)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gimp StacktraceTop: pango_ot_info_list_scripts () from /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 ?? () gimp_viewable_get_preview () ?? () gimp_viewable_get_pixbuf () Title: gimp-2.8 crashed with SIGSEGV in pango_ot_info_list_scripts() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1725611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 960096] hey really great stuff
Hey friend, There is something I needed showing you, it's a few really great products! Simply take a look http://www.manygayvideo.com/engine/classes/highslide/graphics/kind.php?UE85NjAwOTZAYnVncy5sYXVuY2hwYWQubmV0 Faithfully, Stian Sigbjornsen - Neither we nor any third parties provide any warranty or guarantee as to the accuracy, timeliness, performance, completeness or suitability of the information and materials found or offered on this website for any particular purpose. You acknowledge that such information and materials may contain inaccuracies or errors and we expressly exclude liability for any such inaccuracies or errors to the fullest extent permitted by law. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxklavier in Ubuntu. https://bugs.launchpad.net/bugs/960096 Title: Live session started with wrong layout Status in libxklavier: Confirmed Status in libxklavier package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Bug description: Hello TESTCASE - Boot a usb with persistence live session - Select italian and set the network manager, everythings is OK. - Select -Prova Ubuntu- let it load - The session will be started with the english layout. **WORKAROUND** -System Settings -> keyboard layout -> click reset to defaults see attached screenshot, the language is italian (installa ubuntu) but the layout is wrong ProblemType: BugDistroRelease: Ubuntu 12.04 Package: casper 1.312 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.312 Date: Tue Mar 20 11:00:47 2012LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120320) ProcEnviron: TERM=xterm LANG=it_IT.UTF-8 SHELL=/bin/bashSourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libxklavier/+bug/960096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724102] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from logical_monitor_has_monitor()
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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724102 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from logical_monitor_has_monitor() Status in gnome-shell package in Ubuntu: Confirmed Bug description: 17.10 Beta Fully Updated and re-installed in a fresh partition for best results. When screen went blank at time out, returning it from "its' hibernation state" screws up "workspace to Dock" So Alt+F2 and "r" brought it back but other things like terminal stopped working. Trying to help, Mark ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Oct 16 16:12:44 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fbbde5c8543: jmpq *0x88(%rax) PC (0x7fbbde5c8543) ok source "*0x88(%rax)" ok SP (0x7fff9bbdef08) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_get_main_output () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725528] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cracklib2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1725528 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Confirmed Bug description: Trying to upgrade to 17.10, on 21 Oct 2017. I experienced this error on both my machines - a 2007 intel iMac & a 2016 Zenbook. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 10:46:50 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-10-09 (11 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1725528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725501] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cracklib2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1725501 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Confirmed Bug description: I'm new to this, but my Ubuntu MATE upgrade from 17.04 to 17.10 had Cracklib configuration crash out and it made a long mess on the terminal. My system told me I should report this. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 18:10:21 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-08-06 (75 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.4.6~17.04.1 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1725501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725010] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1681231 *** https://bugs.launchpad.net/bugs/1681231 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cracklib2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1725010 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Confirmed Bug description: i ordered an update from 17.04 mate ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Thu Oct 19 23:25:58 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-11-25 (328 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1725010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725314] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: проблемы зависимостей — оставляем триггеры не обработанными
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cracklib2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1725314 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: проблемы зависимостей — оставляем триггеры не обработанными Status in cracklib2 package in Ubuntu: Confirmed Bug description: While upgrade from Xubuntu 17.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 16:54:42 2017 ErrorMessage: проблемы зависимостей — оставляем триггеры не обработанными InstallationDate: Installed on 2017-05-10 (162 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.4.6~17.04.1 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: проблемы зависимостей — оставляем триггеры не обработанными UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1725314/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717286] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: problemas de dependencias - no se procesarán los disparadores
*** This bug is a duplicate of bug 1681231 *** https://bugs.launchpad.net/bugs/1681231 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cracklib2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1717286 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: problemas de dependencias - no se procesarán los disparadores Status in cracklib2 package in Ubuntu: Confirmed Bug description: It ocurred when a was installing Ubuntu Mate 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Thu Sep 14 10:56:01 2017 ErrorMessage: problemas de dependencias - no se procesarán los disparadores InstallationDate: Installed on 2017-09-13 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.4 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: problemas de dependencias - no se procesarán los disparadores UpgradeStatus: Upgraded to artful on 2017-09-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1717286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725432] Re: Restore failed due to missing source option
** Changed in: deja-dup (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: deja-dup (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1725432 Title: Restore failed due to missing source option Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Fix Committed Bug description: [ Impact ] Users can't restore a backup on a fresh install from the deja-dup UI. [ Test Case ] Open "Backups" (or run 'deja-dup') and click the "Restore..." button. You should see a dropdown with options for a location, but instead with this bug, you see an empty dialog. [ Regression Potential ] Pretty small. The proposed patch just moves some widget initialization earlier. [ Original Bug Description ] Installed a new Ubuntu 17.10, created my user and tried to restore the backups from the server. Pressed Overview, Restore and get an empty dialog. From screen shots I found I assume there should be some drop downs or buttons etc. but my dialog is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1725432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp