Re: [Desktop-packages] [Bug 1756205] Re: Can't input Chinese characters in daily built
Thanks a whole lot Gunnar! Look forward to test it. On Sat, Mar 24, 2018 at 8:27 PM, Launchpad Bug Tracker < 1756...@bugs.launchpad.net> wrote: > This bug was fixed in the package gnome-settings-daemon - > 3.28.0-0ubuntu2 > > --- > gnome-settings-daemon (3.28.0-0ubuntu2) bionic; urgency=medium > > * debian/patches/ubuntu_ibus_configs.patch: > - libpinyin instead of sunpinyin for zh_CN (LP: #1756205) > > -- Gunnar Hjalmarsson Sun, 25 Mar 2018 05:16:00 > +0100 > > ** Changed in: gnome-settings-daemon (Ubuntu) >Status: In Progress => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1756205 > > Title: > Can't input Chinese characters in daily built > > Status in gnome-settings-daemon package in Ubuntu: > Fix Released > > Bug description: > OS: Ubuntu 18.04 Daily Built 2018-03-08. > > As reported in the Ubuntu Chinese forum (in Chinese): > > http://forum.ubuntu.com.cn/viewtopic.php?f=49&t=486823 > > users cannot input Chinese characters. > > It appears the daily built uses sunpinyin as the default Chinese input > method. But sunpinyin is not included in the iso. > > Sunpinyin has not been maintained for at least a couple of years; > several problems have been reported associated therewith but remain > unsolved, and it doesn't appear that the problems will be solved any > time soon. > > Ibus-libpinyin has been working very smoothly inside Bionic. Its > frequency table regarding single words can be improved, but it works > very well for phrases. > > I suggest we change the default Chinese input method from sunpinyin to > libpinyin (i.e., intelligent pinyin). > > This is an urgent matter. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-settings- > daemon/+bug/1756205/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756205 Title: Can't input Chinese characters in daily built Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: OS: Ubuntu 18.04 Daily Built 2018-03-08. As reported in the Ubuntu Chinese forum (in Chinese): http://forum.ubuntu.com.cn/viewtopic.php?f=49&t=486823 users cannot input Chinese characters. It appears the daily built uses sunpinyin as the default Chinese input method. But sunpinyin is not included in the iso. Sunpinyin has not been maintained for at least a couple of years; several problems have been reported associated therewith but remain unsolved, and it doesn't appear that the problems will be solved any time soon. Ibus-libpinyin has been working very smoothly inside Bionic. Its frequency table regarding single words can be improved, but it works very well for phrases. I suggest we change the default Chinese input method from sunpinyin to libpinyin (i.e., intelligent pinyin). This is an urgent matter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756205/+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 1758631] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758631/+attachment/5089793/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758631/+attachment/5089795/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758631/+attachment/5089798/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758631/+attachment/5089799/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758631/+attachment/5089800/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758631/+attachment/5089801/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758631/+attachment/5089802/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1758631 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: the mouse cursor automatically moves while typing on keyboard, it also clicks without even touching it ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 25 10:14:31 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-15 (99 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to bionic on 2018-03-20 (4 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758631/+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 1756205] Re: Can't input Chinese characters in daily built
BTW, do you have any idea when this fix will go into the daily built? Really look forward to testing it! Also, when I click on the "manage installed language" dialog bar, I would be prompted to install "kde-config-fcitx". This is unnecessary and clearly is a bug and should be removed. Thanks again! On Sat, Mar 24, 2018 at 8:27 PM, Launchpad Bug Tracker < 1756...@bugs.launchpad.net> wrote: > This bug was fixed in the package gnome-settings-daemon - > 3.28.0-0ubuntu2 > > --- > gnome-settings-daemon (3.28.0-0ubuntu2) bionic; urgency=medium > > * debian/patches/ubuntu_ibus_configs.patch: > - libpinyin instead of sunpinyin for zh_CN (LP: #1756205) > > -- Gunnar Hjalmarsson Sun, 25 Mar 2018 05:16:00 > +0100 > > ** Changed in: gnome-settings-daemon (Ubuntu) >Status: In Progress => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1756205 > > Title: > Can't input Chinese characters in daily built > > Status in gnome-settings-daemon package in Ubuntu: > Fix Released > > Bug description: > OS: Ubuntu 18.04 Daily Built 2018-03-08. > > As reported in the Ubuntu Chinese forum (in Chinese): > > http://forum.ubuntu.com.cn/viewtopic.php?f=49&t=486823 > > users cannot input Chinese characters. > > It appears the daily built uses sunpinyin as the default Chinese input > method. But sunpinyin is not included in the iso. > > Sunpinyin has not been maintained for at least a couple of years; > several problems have been reported associated therewith but remain > unsolved, and it doesn't appear that the problems will be solved any > time soon. > > Ibus-libpinyin has been working very smoothly inside Bionic. Its > frequency table regarding single words can be improved, but it works > very well for phrases. > > I suggest we change the default Chinese input method from sunpinyin to > libpinyin (i.e., intelligent pinyin). > > This is an urgent matter. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-settings- > daemon/+bug/1756205/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756205 Title: Can't input Chinese characters in daily built Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: OS: Ubuntu 18.04 Daily Built 2018-03-08. As reported in the Ubuntu Chinese forum (in Chinese): http://forum.ubuntu.com.cn/viewtopic.php?f=49&t=486823 users cannot input Chinese characters. It appears the daily built uses sunpinyin as the default Chinese input method. But sunpinyin is not included in the iso. Sunpinyin has not been maintained for at least a couple of years; several problems have been reported associated therewith but remain unsolved, and it doesn't appear that the problems will be solved any time soon. Ibus-libpinyin has been working very smoothly inside Bionic. Its frequency table regarding single words can be improved, but it works very well for phrases. I suggest we change the default Chinese input method from sunpinyin to libpinyin (i.e., intelligent pinyin). This is an urgent matter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756205/+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 1756205] Re: Can't input Chinese characters in daily built
On 2018-03-25 10:39, Ping-Wu wrote: > BTW, do you have any idea when this fix will go into the daily > built? Really look forward to testing it! In a couple of days, I'd guess. > Also, when I click on the "manage installed language" dialog bar, I > would be prompted to install "kde-config-fcitx". This is unnecessary > and clearly is a bug and should be removed. That package is needed for Kubuntu, and is installed only if the kio package was installed previously, which it is not on standard Ubuntu AFAIK. Not a bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756205 Title: Can't input Chinese characters in daily built Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: OS: Ubuntu 18.04 Daily Built 2018-03-08. As reported in the Ubuntu Chinese forum (in Chinese): http://forum.ubuntu.com.cn/viewtopic.php?f=49&t=486823 users cannot input Chinese characters. It appears the daily built uses sunpinyin as the default Chinese input method. But sunpinyin is not included in the iso. Sunpinyin has not been maintained for at least a couple of years; several problems have been reported associated therewith but remain unsolved, and it doesn't appear that the problems will be solved any time soon. Ibus-libpinyin has been working very smoothly inside Bionic. Its frequency table regarding single words can be improved, but it works very well for phrases. I suggest we change the default Chinese input method from sunpinyin to libpinyin (i.e., intelligent pinyin). This is an urgent matter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756205/+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 1758638] [NEW] gnome-calendar crashed with SIGSEGV in g_str_equal()
Public bug reported: Ubuntu-Budgie 18.04 beta 1 Software Version gnome-calendar: Installiert: 3.28.0-1 Installationskandidat: 3.28.0-1 Versionstabelle: *** 3.28.0-1 500 Tried to open gnome calendar program when it´s crashed What i expect ? That gneome-calendar open ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Mar 25 12:07:33 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-11 (13 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7f7037a53102 <__strcmp_sse2_unaligned+658>:movzbl (%rdi,%rdx,1),%eax PC (0x7f7037a53102) ok source "(%rdi,%rdx,1)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_str_equal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () g_cclosure_marshal_VOID__POINTERv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_str_equal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic 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 gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1758638 Title: gnome-calendar crashed with SIGSEGV in g_str_equal() Status in gnome-calendar package in Ubuntu: New Bug description: Ubuntu-Budgie 18.04 beta 1 Software Version gnome-calendar: Installiert: 3.28.0-1 Installationskandidat: 3.28.0-1 Versionstabelle: *** 3.28.0-1 500 Tried to open gnome calendar program when it´s crashed What i expect ? That gneome-calendar open ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Mar 25 12:07:33 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-11 (13 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7f7037a53102 <__strcmp_sse2_unaligned+658>: movzbl (%rdi,%rdx,1),%eax PC (0x7f7037a53102) ok source "(%rdi,%rdx,1)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_str_equal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () g_cclosure_marshal_VOID__POINTERv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_str_equal() 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-calendar/+bug/1758638/+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 1758638] Re: gnome-calendar crashed with SIGSEGV in g_str_equal()
*** This bug is a duplicate of bug 1755960 *** https://bugs.launchpad.net/bugs/1755960 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 #1755960, 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/1758638/+attachment/5089804/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758638/+attachment/5089806/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758638/+attachment/5089809/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758638/+attachment/5089810/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758638/+attachment/5089811/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758638/+attachment/5089812/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758638/+attachment/5089813/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1755960 ** 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/1758638 Title: gnome-calendar crashed with SIGSEGV in g_str_equal() Status in gnome-calendar package in Ubuntu: New Bug description: Ubuntu-Budgie 18.04 beta 1 Software Version gnome-calendar: Installiert: 3.28.0-1 Installationskandidat: 3.28.0-1 Versionstabelle: *** 3.28.0-1 500 Tried to open gnome calendar program when it´s crashed What i expect ? That gneome-calendar open ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Mar 25 12:07:33 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-11 (13 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7f7037a53102 <__strcmp_sse2_unaligned+658>: movzbl (%rdi,%rdx,1),%eax PC (0x7f7037a53102) ok source "(%rdi,%rdx,1)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_str_equal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () g_cclosure_marshal_VOID__POINTERv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_str_equal() 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-calendar/+bug/1758638/+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 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*
Hello. I'm having the same problem with mousepad. Yesterday, I've choosed "menu/logout/halt" option instead of "menu/logout/shutdown". And problems started to happen: I could not even reboot or shutdown computer, because every time when I wanted to do this, there was a window to unblock session (I have had to enter my user password and there was not internet connection - it could not be connected via NetworkManager! etc.) The only one working solution to shutdown computer was: press "RESET" and next "POWER" buttons. I've decided to try shytdown system via shutdown(8) command but it did not work: [~]$ shutdown now Failed to power off system via logind: There's already a shutdown or sleep operation in progress Anyway, there is not LightDM now! I have to login via "unblock" window mentioned above. And when I want to edit some file, there is a WARNING message: [~]$ mousepad /lib/systemd/system/rtkit-daemon.service ** (mousepad:2869): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*: Connection refused It happens with every file, that I want to edit etc. Log files contains many entries related to the 'rtkit-daemon'. For example: rtkit-daemon[1383]: Supervising 0 threads of 0 processes of 1 users. rtkit-daemon[1383]: Failed to look up client: No such file or directory I apologize for such a long comment, but mousepad issues, started to happen after described situation. I have no idea if it's important, but it started to happen when I choosed - by accident - 'halt' option instead of 'shutdown' during logout. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1617630 Title: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -* Status in at-spi2-core package in Ubuntu: Confirmed Bug description: When I start mousepad in a terminal, I have this warning : ** (mousepad:25021): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion refusée When I start it with GKSU, the warning is not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+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 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*
Geez, I forgot to write an informations about system version etc. So: ● Release: 16.04 LTS ● Xfce: 4.12.1-3ubuntu1 ● Mousepad: 0.4.0-3ubuntu1 Thanks, best regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1617630 Title: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -* Status in at-spi2-core package in Ubuntu: Confirmed Bug description: When I start mousepad in a terminal, I have this warning : ** (mousepad:25021): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion refusée When I start it with GKSU, the warning is not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+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 1758644] [NEW] [System Product Name, Realtek ALC1150, Green Headphone Out, Front] Playback problem
Public bug reported: Initially Front audio port was in mute and I installed ALSA Mixer and Unmuted it. Then I'm able to hear background noise and whatever I speak in the front mic. But I'm not able to hear any other sound played using Movie player or Rythmbox. Then I ran "ubuntu-bug -s audio" application. It tried playing beep tone two times. First time I could hear it but second time I couldn't. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: selvariyan 1962 F pulseaudio /dev/snd/controlC1: selvariyan 1962 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 25 16:11:05 2018 InstallationDate: Installed on 2016-08-06 (595 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Only some of outputs are working Title: [System Product Name, Realtek ALC1150, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3501 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3501:bd06/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1758644 Title: [System Product Name, Realtek ALC1150, Green Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Initially Front audio port was in mute and I installed ALSA Mixer and Unmuted it. Then I'm able to hear background noise and whatever I speak in the front mic. But I'm not able to hear any other sound played using Movie player or Rythmbox. Then I ran "ubuntu-bug -s audio" application. It tried playing beep tone two times. First time I could hear it but second time I couldn't. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: selvariyan 1962 F pulseaudio /dev/snd/controlC1: selvariyan 1962 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 25 16:11:05 2018 InstallationDate: Installed on 2016-08-06 (595 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Only some of outputs are working Title: [System Product Name, Realtek ALC1150, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3501 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3501:bd06/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifica
[Desktop-packages] [Bug 1751261] Re: libgweather-locations.pot generation fails with bionic meson
** Changed in: gettext (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1751261 Title: libgweather-locations.pot generation fails with bionic meson Status in libgweather: Unknown Status in Ubuntu Translations: Fix Released Status in gettext package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gettext package in Debian: Fix Released Bug description: From bionic: Change to the libgweather source directory and run sudo apt build-dep libgweather dh_auto_configure dh_auto_build ninja -v -C obj-x86_64-linux-gnu/ libgweather-3.0-pot ninja -v -C obj-x86_64-linux-gnu/ libgweather-locations-pot For reference, the second to last command succeeds with this output: --- ninja -v -C obj-x86_64-linux-gnu/ libgweather-3.0-pot ninja: Entering directory `obj-x86_64-linux-gnu/' [0/1] /usr/bin/python3 /usr/bin/meson --internal commandrunner /home/jeremy/devel/libgweather /home/jeremy/devel/libgweather/obj-x86_64-linux-gnu po /usr/bin/python3 /usr/bin/meson /usr/bin/python3 /usr/bin/meson --internal gettext pot --pkgname=libgweather-3.0 --extra-args=--keyword=_@@--add-comments@@--flag=g_set_error:4:c-format@@--flag=N_:1:pass-c-format@@--flag=g_dngettext:2:pass-c-format@@--keyword=NC_:1c,2@@--flag=g_error_new:3:c-format@@--from-code=UTF-8@@--keyword=g_dpgettext2:2c,3@@--keyword=C_:1c,2@@--keyword=g_dngettext:2,3@@--keyword=N_@@--flag=g_string_printf:2:c-format@@--flag=g_string_append_printf:2:c-format@@--flag=C_:2:pass-c-format@@--keyword=g_dcgettext:2@@--flag=NC_:2:pass-c-format@@--flag=g_strdup_printf:1:c-format The last command fails with this output: --- ninja: Entering directory `obj-x86_64-linux-gnu/' [0/1] /usr/bin/python3 /usr/bin/meson --internal commandrunner /home/jeremy/devel/libgweather /home/jeremy/devel/libgweather/obj-x86_64-linux-gnu po-locations /usr/bin/python3 /usr/bin/meson /usr/bin/python3 /usr/bin/meson --internal gettext pot --pkgname=libgweather-locations --extra-args=--its@@/home/jeremy/devel/libgweather/po-locations/../data/locations.its FAILED: meson-libgweather-locations-pot /usr/bin/python3 /usr/bin/meson --internal commandrunner /home/jeremy/devel/libgweather /home/jeremy/devel/libgweather/obj-x86_64-linux-gnu po-locations /usr/bin/python3 /usr/bin/meson /usr/bin/python3 /usr/bin/meson --internal gettext pot --pkgname=libgweather-locations --extra-args=--its@@/home/jeremy/devel/libgweather/po-locations/../data/locations.its ninja: build stopped: subcommand failed. To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1751261/+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 1547589] Re: rtkit-daemon flooding syslog
Hello. I'm having the same problem with 'rtkit' and log files flooding. Yesterday, I've choosed "menu/logout/halt" option instead of "menu/logout/shutdown". And problems started to happen: I could not even reboot or shutdown computer, because every time when I wanted to do this, there was a window to unblock session (I have had to enter my user password and there was not even internet connection - it could not be connected via NetworkManager! etc.) The only one working solution to shutdown computer was: press "RESET" and next "POWER" buttons. I've decided to try shutdown system via shutdown(8) command but it did not work: [~]$ shutdown now Failed to power off system via logind: There's already a shutdown or sleep operation in progress Anyway, there is not LightDM now! I have to login via "unblock" window mentioned above. And when I want to edit e.g. 'rtkit-daemon.service' file via 'mousepad', there is a WARNING message (** (mousepad:2869): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*: Connection refused). It happens with every file, that I want to edit etc. But this is not important here. Log files contains many entries related to the 'rtkit-daemon'. For example: ✗✗ rtkit-daemon[1383]: Supervising 0 threads of 0 processes of 1 users. ✗✗ rtkit-daemon[1383]: Failed to look up client: No such file or directory ✗✗ rtkit-daemon[1364]: message repeated 10 times: [ Failed to look up client: No such file or directory] There is about 30. such entries in '/var/log/syslog/' file etc. Anyway, here are informations gathered via systemd's systemctl(1) command: [~]$ systemctl status rtkit-daemon.service ● rtkit-daemon.service - RealtimeKit Scheduling Policy Service Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled; vendor preset: enabled) Active: active (running) since sun 2018-03-25 11:44:47 CEST; 1h 26min ago Main PID: 1383 CGroup: /system.slice/rtkit-daemon.service └─1383 n/a mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory I apologize for such a long comment, but 'rtkit' issues, started to happen after described situation. I have no idea if it's important, but it started to happen when I choosed - by accident - 'halt' option instead of 'shutdown' during logout. ● Release: 16.04.4 LTS ● rtkit: 0.11-4 Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1547589 Title: rtkit-daemon flooding syslog Status in rtkit package in Ubuntu: Confirmed Bug description: rtkit is flooding syslog with the following: Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying r
[Desktop-packages] [Bug 1758652] [NEW] gsd-color[1116]: failed to set screen _ICC_PROFILE: Failed to open file “/home/oem/.local/share/icc/edid-***.icc”: Permission denied
Public bug reported: This is logged on that system using a /home partition: gsd-color[1116]: failed to set screen _ICC_PROFILE: Failed to open file “/home/oem/.local/share/icc/edid-.icc”: Permission denied oem@ubuntu:~$ ls -la /home/oem/.local/share/icc/ total 20 drwxrwxr-x 2 oem oem 4096 Feb 27 14:04 . drwxr-xr-x 32 oem oem 4096 Mar 25 10:43 .. -rw-rw-r-- 1 oem oem 1552 Feb 27 14:04 edid-***.icc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 25 14:21:28 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1758652 Title: gsd-color[1116]: failed to set screen _ICC_PROFILE: Failed to open file “/home/oem/.local/share/icc/edid-***.icc”: Permission denied Status in gnome-settings-daemon package in Ubuntu: New Bug description: This is logged on that system using a /home partition: gsd-color[1116]: failed to set screen _ICC_PROFILE: Failed to open file “/home/oem/.local/share/icc/edid-.icc”: Permission denied oem@ubuntu:~$ ls -la /home/oem/.local/share/icc/ total 20 drwxrwxr-x 2 oem oem 4096 Feb 27 14:04 . drwxr-xr-x 32 oem oem 4096 Mar 25 10:43 .. -rw-rw-r-- 1 oem oem 1552 Feb 27 14:04 edid-***.icc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 25 14:21:28 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758652/+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 1758648] Re: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
*** This bug is a duplicate of bug 1754202 *** https://bugs.launchpad.net/bugs/1754202 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 #1754202, 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/1758648/+attachment/5089887/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758648/+attachment/5089889/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758648/+attachment/5089892/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758648/+attachment/5089893/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758648/+attachment/5089894/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758648/+attachment/5089895/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758648/+attachment/5089896/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1754202 gnome-calendar crashed with SIGSEGV in gtk_image_reset() ** 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/1758648 Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear() Status in gnome-calendar package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 apt-cache policy gnome-calendar gnome-calendar: Installed: 3.28.0-1 Candidate: 3.28.0-1 Hello, gnome-calendar 3.28.0 crash on exit (SIGSEGV in gtk_image_clear()). Does not happen everytime. Tested on a clean Ubuntu 18.04 install, nothing stored inside the calendar. Thanks ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 14:03:36 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-24 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324) JournalErrors: -- Logs begin at Sat 2018-03-24 16:57:46 CET, end at Sun 2018-03-25 14:05:45 CEST. -- mars 25 13:48:59 username-VirtualBox kernel: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline mars 25 13:49:02 username-VirtualBox spice-vdagent[903]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 mars 25 13:49:35 username-VirtualBox spice-vdagent[1326]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 mars 25 13:49:59 username-VirtualBox pulseaudio[1211]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f3f184b2517 :mov 0x28(%rdi),%rbp PC (0x7f3f184b2517) ok source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: gtk_image_clear () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear() 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-calendar/+bug/1758648/+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 1758653] [NEW] gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied
Public bug reported: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied /var/cache/ has no 'samba' subdir nor file. oem@ubuntu:~$ ls -la /var/cache/ total 80 drwxr-xr-x 18 root root 4096 Feb 19 18:57 . drwxr-xr-x 14 root root 4096 Dec 1 20:15 .. drwxr-xr-x 2 root root 4096 Sep 15 2017 apparmor drwxr-xr-x 4 root root 4096 Dec 1 20:15 app-info drwxr-xr-x 3 root root 4096 Mar 25 14:11 apt drwxr-xr-x 3 root root 4096 Feb 19 18:00 apt-xapian-index drwxr-xr-x 2 root root 4096 Dec 1 20:15 cracklib drwxrwx--- 3 root lp4096 Mar 25 07:35 cups drwxr-xr-x 2 root root 4096 Mar 23 04:41 debconf drwxr-xr-x 2 root root 4096 Dec 1 18:55 dictionaries-common drwxr-xr-x 2 root root 12288 Mar 19 04:28 fontconfig drwxr-xr-x 2 root root 4096 Oct 9 19:50 gdm drwx-- 2 root root 4096 Mar 25 14:11 ldconfig drwxr-xr-x 2 root root 4096 Dec 1 19:13 localepurge drwxr-xr-x 13 man man 4096 Mar 25 14:11 man -rw-r--r-- 1 root root 0 Mar 25 08:24 motd-news drwxr-xr-x 3 root root 4096 Dec 1 19:57 PackageKit drwxr-xr-x 2 root root 4096 Mar 24 14:56 snapd drwxr-xr-x 2 root root 4096 Feb 20 04:57 ubuntu-advantage-tools ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 25 14:28:21 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1758653 Title: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied Status in gvfs package in Ubuntu: New Bug description: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied /var/cache/ has no 'samba' subdir nor file. oem@ubuntu:~$ ls -la /var/cache/ total 80 drwxr-xr-x 18 root root 4096 Feb 19 18:57 . drwxr-xr-x 14 root root 4096 Dec 1 20:15 .. drwxr-xr-x 2 root root 4096 Sep 15 2017 apparmor drwxr-xr-x 4 root root 4096 Dec 1 20:15 app-info drwxr-xr-x 3 root root 4096 Mar 25 14:11 apt drwxr-xr-x 3 root root 4096 Feb 19 18:00 apt-xapian-index drwxr-xr-x 2 root root 4096 Dec 1 20:15 cracklib drwxrwx--- 3 root lp4096 Mar 25 07:35 cups drwxr-xr-x 2 root root 4096 Mar 23 04:41 debconf drwxr-xr-x 2 root root 4096 Dec 1 18:55 dictionaries-common drwxr-xr-x 2 root root 12288 Mar 19 04:28 fontconfig drwxr-xr-x 2 root root 4096 Oct 9 19:50 gdm drwx-- 2 root root 4096 Mar 25 14:11 ldconfig drwxr-xr-x 2 root root 4096 Dec 1 19:13 localepurge drwxr-xr-x 13 man man 4096 Mar 25 14:11 man -rw-r--r-- 1 root root 0 Mar 25 08:24 motd-news drwxr-xr-x 3 root root 4096 Dec 1 19:57 PackageKit drwxr-xr-x 2 root root 4096 Mar 24 14:56 snapd drwxr-xr-x 2 root root 4096 Feb 20 04:57 ubuntu-advantage-tools ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 25 14:28:21 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1758653/+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 1758655] [NEW] [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all
Public bug reported: like bug https://bugs.launchpad.net/bugs/855567 But with Ubuntu 16.04.3 LTS 64 bit Kernel: 4.13.0-37-generic AMD FX(tm)-6350 Six-Core Processor × 6 GeForce GT 730/PCIe/SSE2 16 GB RAM pulseaudio is used. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bern 5504 F pulseaudio /dev/snd/pcmC1D7p: bern 5504 F...m pulseaudio /dev/snd/controlC1: bern 5504 F pulseaudio /dev/snd/controlC0: bern 5504 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 25 13:37:09 2018 InstallationDate: Installed on 2017-08-13 (224 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U0xccd0x77 failed Symptom_Card: Aureon Dual USB - USB Device 0xccd:0x77 Symptom_Type: No sound at all Title: [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1758655 Title: [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: like bug https://bugs.launchpad.net/bugs/855567 But with Ubuntu 16.04.3 LTS 64 bit Kernel: 4.13.0-37-generic AMD FX(tm)-6350 Six-Core Processor × 6 GeForce GT 730/PCIe/SSE2 16 GB RAM pulseaudio is used. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bern 5504 F pulseaudio /dev/snd/pcmC1D7p: bern 5504 F...m pulseaudio /dev/snd/controlC1: bern 5504 F pulseaudio /dev/snd/controlC0: bern 5504 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 25 13:37:09 2018 InstallationDate: Installed on 2017-08-13 (224 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U0xccd0x77 failed Symptom_Card: Aureon Dual USB - USB Device 0xccd:0x77 Symptom_Type: No sound at all Title: [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1758655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-pa
[Desktop-packages] [Bug 1752083] Re: Name "org.gnome.Mutter.DisplayConfig" does not exist
I can't duplicate this bug with the test case you provided in comment #5. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1752083 Title: Name "org.gnome.Mutter.DisplayConfig" does not exist Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: error logged: gsd-xsettings[1545]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist There is no 'DisplayConfig' setting at 'org.gnome.Mutter.' Maybe this is related to an other package, as gsd only display the existing settings; so please change it if required (possibly mutter, 3.26.2-1built1 now). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 27 13:52:26 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1752083/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
This is an amazing bug trail! A lot has been done and @Timo, thanks for the work so far. I have an update that might help. I have 2 laptops, a ASUS and a Lenovo. They both had the issue. I did a reinstall of Ubuntu 16.04 on the Lenovo keeping the home folder. First I had the "no launcher problem" again but after update and reboot it suddenly worked. The the ASUS laptop got the same issue. I have now 2 laptops one working and one not, with the same software but apparently different settings. I saw the status being set to "Fix released" and assumed that just update+upgrade would bring in the fix. My versions are on both computers: $uname -a 4.4.0-116-generic $apt policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 17.2.8-0ubuntu0~16.04.1 Candidate: 17.2.8-0ubuntu0~16.04.1 $apt policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.4-0ubuntu0.7 Candidate: 2:1.18.4-0ubuntu0.7 The not working laptop (ASUS) was switched from the NVIDIA driver to the X.org X server just before the trouble started. There is an odd way of bypassing this bug: Go to the background image and right click and select: "Change Desktop image" You don't want to do this but select: "All Settings". Select: "User accounts". Create a new user. In my case the guest user. (standard, non admin) At least in my case I can use the newly created user WITHOUT ANY PROBLEMS. The newly created user can see and use the launcher. In this way I can at least use the computer. At least it is a temporary fix. The I started looking for differences between my normal user and the new guest user. It is possible to ctrl-alt to a different tty and log in as a different user. Some config must different and make sense but hard to compare and I do not know where to look. So far I only found that the .Xauthority file of both is different. The have the MIT-MAGIC-COOKIE setting with different settings. Removing the .Xauthority file will have the file recreated but does not help in fixing the problem. Please let me know how I can compare both users and where to look. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Released Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1758659] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758659/+attachment/5089991/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758659/+attachment/5089993/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758659/+attachment/5089997/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758659/+attachment/5089998/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758659/+attachment/508/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758659/+attachment/509/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758659/+attachment/5090001/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private Security to Public Security ** 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/1758659 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: System report bug every time reboot. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 Uname: Linux 4.16.0-041600rc6-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 25 06:58:16 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-06 (19 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() 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/1758659/+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 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
My network consists of: 2: enp8s0: mtu 1500 qdisc mq state UP group default qlen 1000 inet 10.1.1.1/24 brd 10.1.1.255 scope global enp8s0 3: wlp4s0: mtu 1500 qdisc mq state UP group default qlen 1000 inet 192.168.99.2/24 brd 192.168.99.255 scope global wlp4s0 5: ppp0: mtu 1484 qdisc pfifo_fast state UNKNOWN group default qlen 3 inet 220.132.100.42 peer 168.95.98.254/32 scope global ppp0 and it seems all work ok except the service networking status keep showing: Active: failed (Result: exit-code) since Sun 2018-03-25 20:47:42 CST; 53min ago Docs: man:interfaces(5) Process: 953 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Process: 859 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" Main PID: 953 (code=exited, status=1/FAILURE) cant find a fix and lead to also see in service NetworkManager status: NetworkManager[933]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed but the point is the network function normally, are these two issues related and what's the cause ? -- 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/1568560 Title: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3 My WiFi connection is very unstable and I have to often restart NetworkManager service (~ a dozen times every day...): sudo systemctl -l status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago Main PID: 27832 (NetworkManager) Memory: 13.8M CPU: 1.729s CGroup: /system.slice/NetworkManager.service ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d ├─27832 /usr/sbin/NetworkManager --no-daemon └─30448 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: keyfile: add connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0") avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): new Tun device (carrier: OFF, driver: 'tun', ifindex: 34) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1): bridge port virbr1-nic was attached avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): enslaved to virbr1 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Also, each time I restart my desktop, NetworkManager generates a crash report: cf. attached screenshots. I have tried an Ubuntu VM with the same packages related to networking and the exact same releases (same repositories), the crash never happens; the difference appears to be only the type of network connection: WiFi for the desktop vs Ethernet for the VM. Any suggestion? To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1568560/+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 1758665] [NEW] Automatic Wi-Fi login failure on user session startup
Public bug reported: network-manager seems to fail to automatically login into home Wi-Fi network (with WPA2 Security) on user session start (it shows the Wi-Fi symbol with a question mark). Going to Wi-Fi settings and clicking on the settings button for the network seems to solve the problem, without needing to actually change anything. Note that I just upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 14:42:13 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.34 metric 600 192.168.123.0/24 dev virbr0 proto kernel scope link src 192.168.123.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: network-manager seems to fail to automatically login into home Wi-Fi network (with WPA2 Security) on user session start (it shows the Wi-Fi symbol with a question mark). Going to Wi-Fi settings and clicking on the settings button for the network seems to solve the problem, without needing to actually change anything. Note that I just upgraded from 16.04 LTS to 18.04 LTS Beta (1?). - - First time reporting a ubuntu bug, used the recommend tool with this - command "ubuntu-bug network-manager", hope that appends all the - necessary info, if not let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 14:42:13 2018 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 InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: - default via 192.168.1.1 dev wlo1 proto dhcp metric 600 - 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown - 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.34 metric 600 - 192.168.123.0/24 dev virbr0 proto kernel scope link src 192.168.123.1 linkdown + default via 192.168.1.1 dev wlo1 proto dhcp metric 600 + 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown + 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.34 metric 600 + 192.168.123.0/24 dev virbr0 proto kernel scope link src 192.168.123.1 linkdown NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.10.4 connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.10.4 connected started full enabled enabled enabled enabled enabled -- 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/1758665 Title: Automatic Wi-Fi login failure on user session startup Status in network-manager package in Ubuntu: New Bug description: network-manager seems to fail to automatically login into home Wi-Fi network (with WPA2 Security) on user session start (it shows the Wi-Fi symbol with a question mark). Going to Wi-Fi settings and clicking on the settings button for the network seems to solve the problem, without needing to actually change anything. Note that I just upgraded from 16.04 LTS to 18.04 LTS Beta (1?). Problem
[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
I have found a solution that at least worked for me. I do not claim that this is the absolute end-solution for this problem and it would like Timo to have a look on it to confirm that this is the way to go. As I mentioned above is the guest user working without any problems. What differs between my not working user and the guest user might cause the problem. So I started comparing and found that ~/.cache/compizconfig-1/core.pb is only 82 bytes while the same file for guest contains 4237 bytes. My original core.pb is nearly empty. What I did was the following: - first make a backup of ~/.cache/compizconfig-1/core.pb You can now always revert the change - su root - copy core.pb to your own home dir to ~/.cache/compizconfig-1/core.pb - chmod the file to your user - reboot All went working again. I can use the unity launcher again. Perfect! It is clear to me that is not the entire solution. The file might have been corrupted by an update and might be corrupted again. So the fix needs to correct the damaging part and also load the correct config. At least I have found a temporary solution and I'm very happy with it because I can use my computer again. I was forced to use Windows and that was no fun. Cheers, Mark -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Released Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1758673] [NEW] gnome-calculator not resizable, output unrea.....
Public bug reported: xUbuntu 16.04.4 gnome-calculator 3.18.3 gnome-calculator is now covered in pointy popup unitylike skin. must have taken some time. unfortunately it is not resizeable or even useable any more attached is a screenshot of the unreadable output. is this a dpi issue? holy smokes seems like less than 20 spaces before the equals sign and perhaps less than 5 periods might let a user read the output? seriously, what happened here. it's a calculator. please don't mark this low priority, this obviously affects multiple users and honestly, it's a calculator. you shouldn't have to unitybar your calculations to google or whatever is happening in gnome nowadays. sorry for ranting, it's tax season ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-calculator now sucks ** Attachment added: "Screenshot_2018-03-25_06-08-17.gnome-calculator.sucks.now.png" https://bugs.launchpad.net/bugs/1758673/+attachment/5090057/+files/Screenshot_2018-03-25_06-08-17.gnome-calculator.sucks.now.png ** Tags added: gnome-calculator sucks ** Tags added: now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1758673 Title: gnome-calculator not resizable, output unrea. Status in gnome-calculator package in Ubuntu: New Bug description: xUbuntu 16.04.4 gnome-calculator 3.18.3 gnome-calculator is now covered in pointy popup unitylike skin. must have taken some time. unfortunately it is not resizeable or even useable any more attached is a screenshot of the unreadable output. is this a dpi issue? holy smokes seems like less than 20 spaces before the equals sign and perhaps less than 5 periods might let a user read the output? seriously, what happened here. it's a calculator. please don't mark this low priority, this obviously affects multiple users and honestly, it's a calculator. you shouldn't have to unitybar your calculations to google or whatever is happening in gnome nowadays. sorry for ranting, it's tax season To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1758673/+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 1752083] Re: Name "org.gnome.Mutter.DisplayConfig" does not exist
** Tags added: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1752083 Title: Name "org.gnome.Mutter.DisplayConfig" does not exist Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: error logged: gsd-xsettings[1545]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist There is no 'DisplayConfig' setting at 'org.gnome.Mutter.' Maybe this is related to an other package, as gsd only display the existing settings; so please change it if required (possibly mutter, 3.26.2-1built1 now). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 27 13:52:26 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1752083/+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 1758677] [NEW] Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout
Public bug reported: When manually logging out, it often takes over 30 seconds to give me logout dialogue. Been happening for the past week. Additionally When I complete the logout - Mouse or keyboard input isn't registered forcing a hard reboot. Happens in both vanilla-gnome-session and ubuntu-session. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13 Uname: Linux 4.13.0-36201803011620-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 10:32:33 2018 InstallationDate: Installed on 2018-01-19 (65 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic gnome3-ppa third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1758677 Title: Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout Status in gnome-session package in Ubuntu: New Bug description: When manually logging out, it often takes over 30 seconds to give me logout dialogue. Been happening for the past week. Additionally When I complete the logout - Mouse or keyboard input isn't registered forcing a hard reboot. Happens in both vanilla-gnome-session and ubuntu-session. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13 Uname: Linux 4.13.0-36201803011620-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 10:32:33 2018 InstallationDate: Installed on 2018-01-19 (65 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920) 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-session/+bug/1758677/+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 1758678] Re: gnome-software crashed with signal 5 in g_main_context_new()
*** This bug is a duplicate of bug 1753607 *** https://bugs.launchpad.net/bugs/1753607 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 #1753607, 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/1758678/+attachment/5090079/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758678/+attachment/5090081/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758678/+attachment/5090085/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758678/+attachment/5090086/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758678/+attachment/5090087/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758678/+attachment/5090088/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758678/+attachment/5090089/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1753607 ** 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/1758678 Title: gnome-software crashed with signal 5 in g_main_context_new() Status in gnome-software package in Ubuntu: New Bug description: After install of some software vie apt install ... ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 15:55:00 2018 ExecutablePath: /usr/bin/gnome-software InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu7 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service Signal: 5 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/libgio-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: gnome-software crashed with signal 5 in g_main_context_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1758678/+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 1698342] Re: package python-pyatspi 2.18.0+dfsg-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pyatspi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pyatspi in Ubuntu. https://bugs.launchpad.net/bugs/1698342 Title: package python-pyatspi 2.18.0+dfsg-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in pyatspi package in Ubuntu: Confirmed Bug description: The issue has been appeared during today's run of Software Updater. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-pyatspi 2.18.0+dfsg-3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri Jun 16 13:29:23 2017 DuplicateSignature: package:python-pyatspi:2.18.0+dfsg-3 Setting up python-pyatspi (2.18.0+dfsg-3) ... /var/lib/dpkg/info/python-pyatspi.postinst: 6: /var/lib/dpkg/info/python-pyatspi.postinst: pycompile: not found dpkg: error processing package python-pyatspi (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: pyatspi Title: package python-pyatspi 2.18.0+dfsg-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2016-06-03 (377 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyatspi/+bug/1698342/+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 1758689] [NEW] No microcode option present
Public bug reported: Appears to have been removed based on " - Remove the cpu-microcode.py detection plugin (LP: #1738259). Kernel metapackages are going to have a hard dependency on the {intel,amd64}-microcode packages to ensure that all bare-metal installs benefit from microcode updates" However that appears to have never occured in bionic for 4.15.x & to have been reverted in all other linux-meta packages, ex. xenial - * Miscellaneous upstream changes - Revert "UBUNTU: Make kernel image packages depend on cpu microcode updates" -- Marcelo Henrique Cerri Fri, 12 Jan 2018 16:34:13 -0200 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-drivers-common 1:0.5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Mar 25 11:36:27 2018 SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1758689 Title: No microcode option present Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Appears to have been removed based on " - Remove the cpu-microcode.py detection plugin (LP: #1738259). Kernel metapackages are going to have a hard dependency on the {intel,amd64}-microcode packages to ensure that all bare-metal installs benefit from microcode updates" However that appears to have never occured in bionic for 4.15.x & to have been reverted in all other linux-meta packages, ex. xenial - * Miscellaneous upstream changes - Revert "UBUNTU: Make kernel image packages depend on cpu microcode updates" -- Marcelo Henrique Cerri Fri, 12 Jan 2018 16:34:13 -0200 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-drivers-common 1:0.5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Mar 25 11:36:27 2018 SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1758689/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error
** Changed in: ktp-accounts-kcm (Ubuntu) Assignee: (unassigned) => vaibhav singh (rockey1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1451728 Title: [master] kde-config-telepathy-accounts package install error Status in Kubuntu PPA: Fix Released Status in Telepathy KDE: Fix Released Status in kaccounts-integration package in Ubuntu: Fix Committed Status in kaccounts-providers package in Ubuntu: Fix Committed Status in ktp-accounts-kcm package in Ubuntu: Triaged Status in libaccounts-glib package in Ubuntu: Fix Released Status in kaccounts-providers source package in Wily: Triaged Status in ktp-accounts-kcm source package in Wily: Triaged Bug description: Installing from Kubuntu 15.04 backports: Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/facebook-im.service', which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) SRU information === [Impact] It's not possible to install KDE and Unity in co-existence because of several file conflicts: many files under /usr/share/accounts/{providers,services}/ are provided by both the package "kaccounts-providers" and packages build from the "account- plugins" source package, for example 'account-plugin-facebook'. [Test case] Install both kaccounts-providers and account-plugin-facebook: you'll get file conflicts for /usr/share/accounts/services/facebook-im.service and /usr/share/accounts/providers/facebook.provider. You might get other conflicts as well, but those are due to bug 1565772 (also nominated for SRU). [Regression potential] Minimal: the changed packages belong to the default KDE installation, and have already landed in Yakkety. Things appear to be working fine there: account creation is still possible under KDE, even after changing the file paths as per this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1662294] Re: package nvidia-opencl-icd-352-updates 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: няма скрипт в новата версия на пакета - ще се предадете ли
Effect also 17.10 as well. It is a shame that bugs are automatically closed with new releases without having actually been fixed. sudo apt-get dist-upgrade ... The following packages will be upgraded: libcuda1-352 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. 112 not fully installed or removed. Need to get 0 B/4,798 B of archives. After this operation, 3,072 B disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 1135342 files and directories currently installed.) Preparing to unpack .../libcuda1-352_361.45.11-0ubuntu4_amd64.deb ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: warning: subprocess old pre-removal script returned error exit status 5 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/libcuda1-352_361.45.11-0ubuntu4_amd64.deb (--unpack): there is no script in the new version of the package - giving up Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Errors were encountered while processing: /var/cache/apt/archives/libcuda1-352_361.45.11-0ubuntu4_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1662294 Title: package nvidia-opencl-icd-352-updates 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: няма скрипт в новата версия на пакета - ще се предадете ли Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Bug description: $ sudo apt-get upgrade Четене на списъците с пакети... Готово Изграждане на дървото със зависимости Четене на информацията за състоянието... Готово Изчисляване на актуализацията... Готово Следните пакети ще бъдат актуализирани: firefox firefox-locale-bg firefox-locale-en libcuda1-352-updates nvidia-352-updates nvidia-opencl-icd-352-updates 6 актуализирани, 0 нови инсталирани, 0 за премахване и 0 без промяна. Необходимо е да се изтеглят 47,6 MB/47,6 MB архиви. След тази операция ще бъде освободено 12,3 kB дисково пространство. Искате ли да продължите? [Y/n] Изт:1 http://archive.ubuntu.com/ubuntu yakkety-updates/main amd64 firefox amd64 51.0.1+build2-0ubuntu0.16.10.2 [46,5 MB] Изт:2 http://archive.ubuntu.com/ubuntu yakkety-updates/main amd64 firefox-locale-bg amd64 51.0.1+build2-0ubuntu0.16.10.2 [455 kB] Изт:3 http://archive.ubuntu.com/ubuntu yakkety-updates/main amd64 firefox-locale-en amd64 51.0.1+build2-0ubuntu0.16.10.2 [637 kB] Изтеглени 47,6 MB за 4с (9862 kB/сек) (Четене на базата данни ... 328080 файла или папки в момента са инсталирани.) Подготовка за разпакетиране на .../0-firefox_51.0.1+build2-0ubuntu0.16.10.2_amd64.deb ... Разпакетиране на firefox (51.0.1+build2-0ubuntu0.16.10.2) над (51.0.1+build2-0ubuntu0.16.10.1) ... Подготовка за разпакетиране на .../1-firefox-locale-bg_51.0.1+build2-0ubuntu0.16.10.2_amd64.deb ... Разпакетиране на firefox-locale-bg (51.0.1+build2-0ubuntu0.16.10.2) над (51.0.1+build2-0ubuntu0.16.10.1) ... Подготовка за разпакетиране на .../2-firefox-locale-en_51.0.1+build2-0ubuntu0.16.10.2_amd64.deb ... Разпакетиране на firefox-locale-en (51.0.1+build2-0ubuntu0.16.10.2) над (51.0.1+build2-0ubuntu0.16.10.1) ... Подготовка за разпакетиране на .../3-libcuda1-352-updates_361.45.11-0ubuntu4_amd64.deb ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: предупреждение: под процеса стар pre-removal скрипт върна грешка за състояние за излизане от 5 dpkg: trying script from the new package instead ... dpkg: error processing archive /tmp/apt-dpkg-install-n4Y4Db/3-libcuda1-352-updates_361.45.11-0ubuntu4_amd64.deb (--unpack): няма скрипт в новата версия на пакета - ще се предадете ли Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Подготовка за разпакетиране на .../4-nvidia-352-updates_361.45.11-0ubuntu4_amd64.deb ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: предупреждение: под процеса стар pre-removal скрипт върна грешка за състояние за излизане от 5 dpkg: trying script from the new package instead ... dpkg: error processing archive /tmp/apt-dpkg-install-n4Y4Db/4-nvidia-352-updates_361.45.11-0ubuntu4_amd64.deb (--unpack): няма скрипт в новата версия на пакета - ще се предадете ли Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Подготовка
[Desktop-packages] [Bug 1757058] Re: gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → g_closure_invoke → signal_emit_unlocked_R
** Changed in: gnome-calendar (Ubuntu) Status: Confirmed => Fix Released -- 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/1757058 Title: gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → g_closure_invoke → signal_emit_unlocked_R Status in gnome-calendar package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.27.90-1build1, the problem page at https://errors.ubuntu.com/problem/10133d642d3e26786b82ac7e8f7f53f804cf1714 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/ubuntu/+source/gnome-calendar/+bug/1757058/+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 1758693] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758693/+attachment/5090141/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758693/+attachment/5090143/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758693/+attachment/5090146/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758693/+attachment/5090147/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758693/+attachment/5090148/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758693/+attachment/5090149/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758693/+attachment/5090150/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1758693 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Hello, This crash occurred once logged in. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 25 16:51:29 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-24 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324) JournalErrors: -- Logs begin at Sat 2018-03-24 16:57:46 CET, end at Sun 2018-03-25 18:07:13 CEST. -- mars 25 18:05:42 hostname kernel: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline mars 25 18:05:46 hostname spice-vdagent[880]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 mars 25 18:05:57 hostname spice-vdagent[1298]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 mars 25 18:06:10 hostname pulseaudio[1181]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() 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/1758693/+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 1758701] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o
Public bug reported: Installing wine causes this crash report to pop up Running on: Ubuntu 17.10 Release:17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Mar 25 09:17:10 2018 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-13 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.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.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1758701 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: Installing wine causes this crash report to pop up Running on: Ubuntu 17.10 Release: 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Mar 25 09:17:10 2018 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-13 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.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.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 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/1758701/+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 1758700] [NEW] Internal display not working
Public bug reported: My internal display is not working. The internal display works at boot and goes black during ubuntu boot. I am able to use the hdmi monitor but i need my internal screen to work. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 09:35:30 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] InstallationDate: Installed on 2018-02-18 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=cd069400-aa78-43dd-9434-6d260f2c78f1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.06.00 dmi.board.name: 0K99NX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0K99NX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91+git1803221830.bb45ce~oibaf~a version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803241930.d60eaf~oibaf~a version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1803241930.d60eaf~oibaf~a version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1+git1803151933.fdba53~oibaf~a version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1803021934.aa3639~oibaf~a version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1803090733.ac8f7b~oibaf~a ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages ubuntu wayland-session -- 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/1758700 Title: Internal display not working Status in xorg package in Ubuntu: New Bug description: My internal display is not working. The internal display works at boot and goes black during ubuntu boot. I am able to use the hdmi monitor but i need my internal screen to work. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 09:35:30 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] InstallationDate: Installed on 2018-02-18 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=cd069400-aa78-43dd-9434-6d260f2c78f1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.06.00 dmi.board.name: 0K99NX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0K99NX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91+git1803221830.bb45ce~oibaf~a version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803241930.d60eaf~oibaf~a version.libgl1-mesa-g
[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
@Daniel Why was this bug closed? @matt.mahin suggestion doesn't seem to fix this. -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1758706] [NEW] Session logs out after screen turns off
Public bug reported: This is the same bug as #1721428 :/var/crash$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 I am using a NUC7i7BNH connected via HDMI. The screen turns off after 5 minutes of inactivity and automatic screen lock is also turned on to lock the screen after screen turns off. When I resume activity, I am presented with the logon screen, which after entering my password, reloads another logon screen. When I then enter my password the second time, I am logged in, but it is a new session. ** Affects: gnome-shell (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/1758706 Title: Session logs out after screen turns off Status in gnome-shell package in Ubuntu: New Bug description: This is the same bug as #1721428 :/var/crash$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 I am using a NUC7i7BNH connected via HDMI. The screen turns off after 5 minutes of inactivity and automatic screen lock is also turned on to lock the screen after screen turns off. When I resume activity, I am presented with the logon screen, which after entering my password, reloads another logon screen. When I then enter my password the second time, I am logged in, but it is a new session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758706/+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 1750707] Re: LibreOffice says permission was denied to open a file in a NTFS partition, even with it having permission
** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1750707 Title: LibreOffice says permission was denied to open a file in a NTFS partition, even with it having permission Status in libreoffice package in Ubuntu: Fix Released Bug description: I'm trying to open a spreadsheet file located in a NTFS partition, but LibreOffice gives an error saying the permission is denied. I am sure I have permission to edit that file and that partition because I could edit it with Gedit (it does not show Read-Only on the bar) and I copied and created new files (not with LibreOffice) in the same directory the spreadsheet is. The NTFS partition is mounted at boot time using the following on /etc/fstab (redacted): UUID= /mnt/W10 ntfs-3g defaults,windows_names 0 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:5.4.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Feb 20 23:16:05 2018 InstallationDate: Installed on 2017-06-13 (252 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2017-10-20 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750707/+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 1758706] Re: Session logs out after screen turns off
*** This bug is a duplicate of bug 1721428 *** https://bugs.launchpad.net/bugs/1721428 ** This bug has been marked a duplicate of bug 1721428 Artful (17.10) Session logout after screen turned off -- 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/1758706 Title: Session logs out after screen turns off Status in gnome-shell package in Ubuntu: New Bug description: This is the same bug as #1721428 :/var/crash$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 I am using a NUC7i7BNH connected via HDMI. The screen turns off after 5 minutes of inactivity and automatic screen lock is also turned on to lock the screen after screen turns off. When I resume activity, I am presented with the logon screen, which after entering my password, reloads another logon screen. When I then enter my password the second time, I am logged in, but it is a new session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758706/+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 1690192] Re: Unable to configure Gmail account, login window has no functional buttons
Thunderbird was updated soon after I did this report and the bug was corrected. -- 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/1690192 Title: Unable to configure Gmail account, login window has no functional buttons Status in thunderbird package in Ubuntu: New Bug description: Hello I tried to add a Gmail account, after choosing the options on Thunderbird, a window opens requesting the login information. However, the buttons on this window aren't functional, so clicking Next, Help or any other have no effect. I expected the buttons would work and I could log in the account. This bug is reported on https://support.mozilla.org/pt- BR/questions/1157902 and affected me, which was using the Ubuntu version. I was using thunderbird version 45.8.0+build1-0ubuntu0.16.04.1. I have removed the thunderbird installation and I am using the one downloaded from the Thunderbird site (version 52.1) which has the correction. I believe the Thunderbird package should be updated to the newer version to solve this. Thank you. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1690192/+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 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)
** Changed in: mesa Status: Unknown => Fix Released ** Changed in: mesa Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1753776 Title: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only) Status in Mesa: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in wayland package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Invalid Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Invalid Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFille
[Desktop-packages] [Bug 1758706] Re: Session logs out after screen turns off
*** This bug is a duplicate of bug 1721428 *** https://bugs.launchpad.net/bugs/1721428 xwayland crash log ** Attachment added: "_usr_bin_Xwayland.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758706/+attachment/5090250/+files/_usr_bin_Xwayland.1000.crash ** Information type changed from Private Security to Public -- 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/1758706 Title: Session logs out after screen turns off Status in gnome-shell package in Ubuntu: New Bug description: This is the same bug as #1721428 :/var/crash$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 I am using a NUC7i7BNH connected via HDMI. The screen turns off after 5 minutes of inactivity and automatic screen lock is also turned on to lock the screen after screen turns off. When I resume activity, I am presented with the logon screen, which after entering my password, reloads another logon screen. When I then enter my password the second time, I am logged in, but it is a new session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758706/+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 1758713] [NEW] system
Public bug reported: Ubuntu 16.04 LTS system bugs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 25 19:33:39 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: microdia, 2009.01: added v4l2loopback, 0.9.1, 4.13.0-36-generic, i686: installed v4l2loopback, 0.9.1, 4.13.0-37-generic, i686: installed virtualbox, 5.0.40, 4.13.0-36-generic, i686: installed virtualbox, 5.0.40, 4.13.0-37-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 1100/1150] [1458:d000] InstallationDate: Installed on 2018-02-28 (24 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) JournalErrors: -- Logs begin at v 2018-03-25 19:03:19 CEST, end at v 2018-03-25 19:34:01 CEST. -- márc 25 19:28:46 hostname com.canonical.Unity.Scope.Applications[1847]: Error loading package indexes: Couldn't stat '/var/cache/software-center/xapian' márc 25 19:28:46 hostname com.canonical.Unity.Scope.Applications[1847]: (unity-scope-loader:5431): unity-applications-daemon-CRITICAL **: daemon.vala:144: Failed to load Software Center index. 'Apps Available for Download' will not be listed MachineType: FUJITSU SIEMENS GA-K8RS482M ProcEnviron: LANGUAGE=hu PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2005 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: GA-K8RS482M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/27/2005:svnFUJITSUSIEMENS:pnGA-K8RS482M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8RS482M:rvrx.x:cvn:ct3:cvr: dmi.product.name: GA-K8RS482M dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Mar 25 17:47:59 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSIGMACHIP Usb Mouse MOUSE, id 8 inputHID 1267:0103KEYBOARD, id 9 inputHID 1267:0103KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1758713 Title: system Status in xorg package in Ubuntu: New Bug description: Ubuntu 16.04 LTS system bugs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 25 19:33:39 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: microdia, 2009.01: added v4l2loopback, 0.9.1, 4.13.0-36-generic, i686: installed v4l2loopback, 0.9.1, 4.13.0-37-generic, i686: installed virtualbox, 5.0.40, 4.13.0-36-generic, i686: installed virtualbox, 5.0.40, 4.13.0-37-generic, i686: installed ExtraDebuggingInter
[Desktop-packages] [Bug 1758701] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
*** This bug is a duplicate of bug 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files '/lib/udev/hwdb.d/20-sane.hwdb' -- 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/1758701 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: Installing wine causes this crash report to pop up Running on: Ubuntu 17.10 Release: 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Mar 25 09:17:10 2018 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-13 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.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.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 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/1758701/+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 1706488] Re: Snaps without icons not showing
*** This bug is a duplicate of bug 1697565 *** https://bugs.launchpad.net/bugs/1697565 ** This bug has been marked a duplicate of bug 1697565 Snaps without icons don't show as installed -- 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/1706488 Title: Snaps without icons not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Confirmed Status in gnome-software source package in Zesty: Confirmed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] Snaps without an icon (i.e. not provided in snap or in the store) are not shown in GNOME Software. This is because GNOME Software fails to get the "package-x-generic" default icon. [Test Case] 1. Install a snap without an icon, e.g: $ sudo snap install openscad-plars 2. Start GNOME Software 3. Click on installed tab Expected result: The installed snap is show in the list of apps. Observed result: The snap is not shown. [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1706488/+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 1758720] [NEW] not able to open, adapt size and position of application windows
Public bug reported: windows of applications cannot be adapted to screen size or closed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Mar 25 19:56:24 2018 DistUpgraded: 2016-05-01 09:53:49,322 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:5105] InstallationDate: Installed on 2013-10-19 (1617 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 33597FG ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=523d7466-d561-4cde-8664-11fab034ade1 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-05-01 (693 days ago) dmi.bios.date: 12/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: HMET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 33597FG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHMET90WW(2.50):bd12/26/2012:svnLENOVO:pn33597FG:pvrThinkPadEdgeE135:rvnLENOVO:rn33597FG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33597FG dmi.product.version: ThinkPad Edge E135 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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: Sun Mar 25 19:37:11 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1758720 Title: not able to open, adapt size and position of application windows Status in xorg package in Ubuntu: New Bug description: windows of applications cannot be adapted to screen size or closed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Mar 25 19:56:24 2018 DistUpgraded: 2016-05-01 09:53:49,322 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:5105] InstallationDate: Installed on 2013-10-19 (1617 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 33597FG ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=523d7466-d561-4cde-8664-11fab034ade1 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-05-01 (693 days ago) dmi.bios.date: 12/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: HMET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 33597FG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHMET90WW(2.50):bd12/2
[Desktop-packages] [Bug 1758721] [NEW] Screen corruption after suspend
Public bug reported: I consistently get screen corruption after a suspend in the wake-up screen (the one with the arrows you drag) and login screen. Sometimes I have trouble dragging the wake-up screen to get the login screen. Sometimes I am able to get the login screen (although all text is corrupted) and login back into my session. After login screen corruption is inconsistent, at times the whole session is corrupted (see attachment), sometimes only text is corrupted (icons, desktop is okay) and sometimes there is no corruption. One workaround that seems to avoid the situation is to disable all automatic suspend options in the power settings. Note that I have recently upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 19:18:25 2018 DistUpgraded: 2018-03-25 11:25:40,806 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218M [NVS 3100M] [103c:172b] InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=a16d7c26-68e8-4cec-bcdc-c814a96b448d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.22 dmi.board.name: 172B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.33 dmi.chassis.asset.tag: CZC02417F8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.22:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.33:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 23 14:06:10 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption has-workaround reproducible ubuntu ** Attachment added: "TotalScreenCorruptionAfterLogin" https://bugs.launchpad.net/bugs/1758721/+attachment/5090305/+files/Screenshot%20from%202018-03-25%2014-18-58.png -- 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/1758721 Title: Screen corruption after suspend Status in xorg package in Ubuntu: New Bug description: I consistently get screen corruption after a suspend in the wake-up screen (the one with the arrows you drag) and login screen. Sometimes I have trouble dragging the wake-up screen to get the login screen. Sometimes I am able to get the login screen (although all text is corrupted) and login back into my session. After login screen corruption is inconsistent, at times the whole session is corrupted (see attachment), sometimes only text is corrupted (icons, desktop is okay) and sometimes there is no corruption. One workaround that seems to avoid the situation is to disable all automatic suspend options in the power settings. Note that I have recently upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No
[Desktop-packages] [Bug 1758725] [NEW] network-manager applet up/down arrows when connected to wifi only
Public bug reported: I have an issue with the network-manager applet that shows up and down arrows (wired connection?) when connected to wifi only. I still have internet connectivity, but unable to choose a wifi network. The computer: Toshiba Satellite L55W-C5320. The OS: Ubuntu 16.04.4. Thank you, Pavel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 25 11:27:15 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-25 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH shrek4 1 a8c323eb-6312-4287-924a-ce4567222530 802-11-wireless 1522002319 Sun 25 Mar 2018 11:25:19 AM PDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 shrek4 1a8c323eb-6312-4287-924a-ce4567222530 /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.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/1758725 Title: network-manager applet up/down arrows when connected to wifi only Status in network-manager package in Ubuntu: New Bug description: I have an issue with the network-manager applet that shows up and down arrows (wired connection?) when connected to wifi only. I still have internet connectivity, but unable to choose a wifi network. The computer: Toshiba Satellite L55W-C5320. The OS: Ubuntu 16.04.4. Thank you, Pavel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 25 11:27:15 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-25 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH shrek4 1 a8c323eb-6312-4287-924a-ce4567222530 802-11-wireless 1522002319 Sun 25 Mar 2018 11:25:19 AM PDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activ
[Desktop-packages] [Bug 1758724] Re: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset()
*** This bug is a duplicate of bug 1738239 *** https://bugs.launchpad.net/bugs/1738239 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 #1738239, 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/1758724/+attachment/5090346/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758724/+attachment/5090348/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758724/+attachment/5090351/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758724/+attachment/5090352/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758724/+attachment/5090353/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758724/+attachment/5090354/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758724/+attachment/5090355/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1738239 ** 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/1758724 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: I was printing a test page on a printer I had just connected. This all worked, but the window for Devices -> Printers disappeared and then this error message appeared approximately ten seconds later. I anticipated I would close this window and everything to do with setting up the printer once the test page had been successfully printed, which it had anyway. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 19:33:36 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-03-07 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcCmdline: gnome-control-center printers ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 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/1758724/+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 1758731] [NEW] gnome-shell crashed with signal 5 in g_log_default_handler()
Public bug reported: Crash occured after booting, while downloading the updates with Software Updater ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Mar 24 12:01:26 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-22 (93 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1758731 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Crash occured after booting, while downloading the updates with Software Updater ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Mar 24 12:01:26 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-22 (93 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() 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/1758731/+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 1758730] Re: gnome-software crashed with signal 5
*** This bug is a duplicate of bug 1741119 *** https://bugs.launchpad.net/bugs/1741119 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 #1741119, 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/1758730/+attachment/5090388/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758730/+attachment/5090390/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758730/+attachment/5090393/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758730/+attachment/5090394/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758730/+attachment/5090395/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758730/+attachment/5090396/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758730/+attachment/5090397/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1741119 ** 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/1758730 Title: gnome-software crashed with signal 5 Status in gnome-software package in Ubuntu: New Bug description: eu nã sei ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 16:01:36 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-02-23 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1 snapd_client_find_section_sync () at /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1 () at /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so Title: gnome-software crashed with signal 5 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/1758730/+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 1758736] [NEW] [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
Public bug reported: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758737] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'a
Public bug reported: I'm using an Aspire V3-572G-55NR with Ubuntu 17.10 and Windows 10 in dual boot. This PC use an intel I5 with intel GPU in it and a dGPU Nvidia the bug appear at login and indicate a prime-indicator error. Excuse my enlish i'm french. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sat Mar 17 22:44:46 2018 ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 InstallationDate: Installed on 2018-03-16 (9 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) 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.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1758737 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: I'm using an Aspire V3-572G-55NR with Ubuntu 17.10 and Windows 10 in dual boot. This PC use an intel I5 with intel GPU in it and a dGPU Nvidia the bug appear at login and indicate a prime-indicator error. Excuse my enlish i'm french. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sat Mar 17 22:44:46 2018 ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 InstallationDate: Installed on 2018-03-16 (9 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) 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.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 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/1758737/+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 1758731] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758731/+attachment/5090398/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758731/+attachment/5090400/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758731/+attachment/5090404/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758731/+attachment/5090405/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758731/+attachment/5090406/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758731/+attachment/5090407/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758731/+attachment/5090408/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1758731 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Crash occured after booting, while downloading the updates with Software Updater ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Mar 24 12:01:26 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-22 (93 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() 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/1758731/+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 1758732] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1754924 *** https://bugs.launchpad.net/bugs/1754924 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 #1754924, 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/1758732/+attachment/5090409/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758732/+attachment/5090411/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758732/+attachment/5090415/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758732/+attachment/5090416/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758732/+attachment/5090417/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758732/+attachment/5090418/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758732/+attachment/5090419/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1754924 gnome-control-center crashed with SIGSEGV in actualize_printers_list() ** 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/1758732 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() Status in gnome-control-center package in Ubuntu: New Bug description: N/A ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 16:30:33 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-28 (147 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center bluetooth SegvAnalysis: Segfault happened at: 0x5642a78803d1:mov0x90(%rbp),%rsi PC (0x5642a78803d1) ok source "0x90(%rbp)" (0x0090) 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/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to bionic on 2018-03-18 (7 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/1758732/+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 1758745] [NEW] Single click in icon view not working in nautilus
Public bug reported: In icon view single click setting seems not working. I need to double click to open a file or folder. Single click works as expected in details view. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 22:02:25 2018 InstallationDate: Installed on 2017-01-07 (441 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sl_SI.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1758745 Title: Single click in icon view not working in nautilus Status in nautilus package in Ubuntu: New Bug description: In icon view single click setting seems not working. I need to double click to open a file or folder. Single click works as expected in details view. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 22:02:25 2018 InstallationDate: Installed on 2017-01-07 (441 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sl_SI.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1758745/+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 1758739] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758739/+attachment/5090454/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758739/+attachment/5090456/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758739/+attachment/5090460/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758739/+attachment/5090461/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758739/+attachment/5090462/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758739/+attachment/5090463/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758739/+attachment/5090464/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1758739 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 25 21:13:55 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'evolution.desktop', 'empathy.desktop', 'rhythmbox.desktop', 'shotwell.desktop', 'libreoffice-writer.desktop', 'nautilus.desktop', 'yelp.desktop', 'opera-browser.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-09-02 (568 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) LocalLibraries: /usr/local/lib/libgpg-error.so.0.20.0 /usr/local/lib/libgcrypt.so.20.1.3 ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.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/1758739/+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 1758744] [NEW] Crackling audio when '/usr/bin/speech-dispatcher' version 0.8.8-1 is running on 18.04
Public bug reported: Problem occurs shortly after pulse-audio is first used after login. I'm able to reproduce this consistently by trying to play sound through Firefox right after login, although speech-dispatcher eventually exits and audio returns to normal. Only occurs whilst `speech-dispatcher` is visible in `pavucontrol`, killing `speech-dispatcher` solves the problem for me. I was able to grab the exact command and arguments being run from `ps`: `/usr/bin/speech-dispatcher --spawn --communication-method unix_socket --socket-path /run/user/1000/speech-dispatcher/speechd.sock` By running it I'm able to reliably trigger the crackling audio. Other information: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 speech-dispatcher: Installed: 0.8.8-1 Candidate: 0.8.8-1 Version table: *** 0.8.8-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: speech-dispatcher (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1758744 Title: Crackling audio when '/usr/bin/speech-dispatcher' version 0.8.8-1 is running on 18.04 Status in speech-dispatcher package in Ubuntu: New Bug description: Problem occurs shortly after pulse-audio is first used after login. I'm able to reproduce this consistently by trying to play sound through Firefox right after login, although speech-dispatcher eventually exits and audio returns to normal. Only occurs whilst `speech-dispatcher` is visible in `pavucontrol`, killing `speech-dispatcher` solves the problem for me. I was able to grab the exact command and arguments being run from `ps`: `/usr/bin/speech-dispatcher --spawn --communication-method unix_socket --socket-path /run/user/1000/speech-dispatcher/speechd.sock` By running it I'm able to reliably trigger the crackling audio. Other information: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 speech-dispatcher: Installed: 0.8.8-1 Candidate: 0.8.8-1 Version table: *** 0.8.8-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1758744/+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 1568490] Re: Can no longer move windows controls to the right (16.04) - gsettings has no effect now
*** This bug is a duplicate of bug 1309942 *** https://bugs.launchpad.net/bugs/1309942 I'm using Linux Mint 18.3. I cannot move the control buttons to left for applications "Calculator" and "Disks". With other applications it's working fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1568490 Title: Can no longer move windows controls to the right (16.04) - gsettings has no effect now Status in unity-settings-daemon package in Ubuntu: Confirmed Status in unity-tweak-tool package in Ubuntu: Confirmed Bug description: Just installed 16.04 beta2 (plus latest updates), I can no longer move the window controls to the right. On previous ubuntu versions I would use the command # gsettings set org.gnome.desktop.wm.preferences button-layout 'menu:minimize,maximize,close' But this has no effect, neither does 'window controls' section of the unity-tweak-tool any longer - if I choose right nothing happens. If I check the setting with # gsettings list-recursively | grep button-layout I see org.gnome.desktop.wm.preferences button-layout 'menu:minimize,maximize,close' How can I move the window buttons to the right now ? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-settings-daemon 15.04.1+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 10 11:52:21 2016 InstallationDate: Installed on 2016-04-09 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1568490/+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 1758737] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'aut
*** This bug is a duplicate of bug 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files '/lib/udev/hwdb.d/20-sane.hwdb' -- 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/1758737 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: I'm using an Aspire V3-572G-55NR with Ubuntu 17.10 and Windows 10 in dual boot. This PC use an intel I5 with intel GPU in it and a dGPU Nvidia the bug appear at login and indicate a prime-indicator error. Excuse my enlish i'm french. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sat Mar 17 22:44:46 2018 ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 InstallationDate: Installed on 2018-03-16 (9 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) 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.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 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/1758737/+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 1727710] Re: Unable to access more than 20 languages in 1080p
Reopened this for now. Reason: https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/16 ** Changed in: gnome-control-center (Ubuntu Bionic) Status: Fix Released => In Progress -- 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/1727710 Title: Unable to access more than 20 languages in 1080p Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Bug description: There is no scroll bar on the language selection GUI, causing issues if you install more than 20 language selections. The ... button is on the bottom off the screen, meaning you can't access it. On resolutions smaller than 1080p, you could expect the same issues but with less language options. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1727710/+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 1757299] Re: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications
gregrwm: 1) Regarding other reports, as mentioned multiple times previously, those are useless. Hence, if you cannot reproduce a crash, then it is most helpful if you remain focused on this report, and providing previously requested information (see below), and other information requested of you in the future. Otherwise, this will never be root caused, fixed, and backported to prior releases as applicable. 2) Regarding the question previously asked of you in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1757299/comments/6: After reproducing the problem, if you SSH in and only kill processes that are not xorg, which processes do you have to kill until your GUI begins to be responsive again? 3) Regarding your Bug Description, at the point where you "maximize the xterm running tmux, and the GUI immediately becomes unresponsive", is there an amount of time that if you wait the GUI eventually become responsive again, and if so, how long precisely? -- 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/1757299 Title: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications Status in xorg package in Ubuntu: Incomplete Bug description: The problem is that after launching a few applications, the GUI may become unresponsive, although this is not consistently reproducible. When the GUI is unresponsive, it is correlated to high CPU utilization of xorg. An example reproduction scenario is launch the following in order, and quickly: startx xterm via twm another xterm via the first xterm tmux firefox-esr bluetooth-manager pavucontrol While the above are launching, maximize the xterm running tmux, and the GUI immediately becomes unresponsive. For example, Ctrl+Alt+Fn don't respond. After this, I logged in via ssh, attached to tmux, launched htop, copied htop output, which shows xorg at 94.6 CPU%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd * Starting AppArmor profiles [160G [154G[ OK ] * Restoring resolver state... [160G [154G[ OK ] CompositorRunning: None Date: Tue Mar 20 17:15:16 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] JournalErrors: -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 CDT. -- Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon already running. MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-no
[Desktop-packages] [Bug 1406538] Re: Screenshot contains selected area highlight
** Changed in: mate-utils (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1406538 Title: Screenshot contains selected area highlight Status in Linux Mint: Confirmed Status in gnome-screenshot package in Ubuntu: Confirmed Status in mate-utils package in Ubuntu: Fix Released Bug description: mate-utils_1.8.1-0+rebecca_amd64 If i choose "select area to grab" i almost constantly get an annoying green overlay which is what i just used to highlight the area that i wanted to grab. See attached example. I'm using Mint MATE x64 17.1, software compositing window manager enabled, compiz disabled, VGA AMD radeon 6370M, drivers "xserver-xorg-video-ati" 7.3.0-1-ubuntu3.1, kernel 3.13.0-37-generic x86_64. I remember this happening since mint 13 or so. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1406538/+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 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop
Same problem with HP-250-G4-Notebook-PC $ cat /proc/asound/card*/codec* | grep Codec Codec: Realtek ALC3227 Codec: Intel Skylake HDMI $ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP HD Audio Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1737614 Title: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a new laptop HP-15-BS576TX which has this Intel Corporation Sunrise Point-LP HD Audio. 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) The laptop sound works perfectly fine in Windows 10 with realtek drivers. However, in Ubuntu 17.10, the volume is significantly low, that I've to scroll the volume slider above 100% mark in pulseaudio to the maximum to get acceptable level of sound. I suspect the sound quality also is low (mono-like), may be not coming from all speakers (perhaps subwoofer exist for this model). Also alsamixer shows the speaker volume at the maximum. Details about the audio hardware are below: :~$ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Hewlett-Packard Company Device 832b Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- /proc/asound/card0/codec#0 <== Codec: Realtek ALC3227 ==> /proc/asound/card0/codec#2 <== Codec: Intel Kabylake HDMI :~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 I have gone through Linux kernel sources ALSA and Snd-HDA lists and unable to find any optimizations for this laptop. Here is the relevant dmesg details: [ 15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 16.310510] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [ 16.310512] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 16.451397] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input9 [ 16.451451] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input12 [ 16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input13 [ 16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input14 [ 16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input15 Any further information needed, please let me know. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: usr/share/alsa-base/alsa-info.sh] ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: ndiswrapper ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin2018 1246 F pulseaudio CurrentDesktop: GNOME Date: Tue Dec 12 00:46:12 2017 InstallationDate: Installed on 2017-11-22 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all Sour
[Desktop-packages] [Bug 1758761] [NEW] In 59.0.1 the Bookmarks button on Customize page raises invisible menu
Public bug reported: When downloading the FF version from "ftp.mozilla.org/pub/firefox/releases/59.0.1/linux-x86_64/en-US/" I get a browser with a normally functioning button. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "attachment.png" https://bugs.launchpad.net/bugs/1758761/+attachment/5090542/+files/attachment.png -- 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/1758761 Title: In 59.0.1 the Bookmarks button on Customize page raises invisible menu Status in firefox package in Ubuntu: New Bug description: When downloading the FF version from "ftp.mozilla.org/pub/firefox/releases/59.0.1/linux-x86_64/en-US/" I get a browser with a normally functioning button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758761/+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 1651396] Re: Backup fails every time after one incremental file is possibly corrupted
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: deja-dup (Ubuntu) Status: New => Confirmed -- 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/1651396 Title: Backup fails every time after one incremental file is possibly corrupted Status in deja-dup package in Ubuntu: Confirmed Bug description: The backup location is on a NAS mounted with NFS. I get this message every time I try to make a new backup: Backup Failed Invalid data - SHA1 hash mismatch for file: duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a439c Manifest hash: b46782fb799c7c5a543ac88d9bfb7cc1df25d38c Can someone recommend a better backup software for personal use? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 20 12:36:15 2016 InstallationDate: Installed on 2014-05-16 (949 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: deja-dup UpgradeStatus: Upgraded to xenial on 2016-08-02 (139 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1651396/+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 1758761] Re: In 59.0.1 the Bookmarks button on Customize page raises invisible menu
TROUBLESHOOTING INFORMATION: Application Basics -- Name: Firefox Version: 59.0.1 Build ID: 20180316021607 User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 OS: Linux 4.13.0-37-generic Multiprocess Windows: 1/1 (Enabled by default) Web Content Processes: 3/4 Stylo: content = true (enabled by default), chrome = false (disabled by default) Google Key: Found Mozilla Location Service Key: Missing Safe Mode: false Firefox Features Name: Activity Stream Version: 2018.02.17.0026-173e2795 ID: activity-str...@mozilla.org Name: Application Update Service Helper Version: 2.0 ID: aushel...@mozilla.org Name: Firefox Screenshots Version: 25.0.0 ID: screensh...@mozilla.org Name: Follow-on Search Telemetry Version: 0.9.6 ID: followonsea...@mozilla.com Name: Form Autofill Version: 1.0 ID: formautof...@mozilla.org Name: Photon onboarding Version: 1.0 ID: onboard...@mozilla.org Name: Pocket Version: 1.0.5 ID: fire...@getpocket.com Name: Shield Recipe Client Version: 80 ID: shield-recipe-cli...@mozilla.org Name: Web Compat Version: 1.1 ID: webcom...@mozilla.org Extensions -- Name: RescueTime for Firefox Version: 3.1.4 Enabled: true ID: rescuetime_fire...@rescuetime.com Name: Video DownloadHelper Version: 7.1.1 Enabled: true ID: {b9db16a4-6edc-47ec-a1f4-b86292ed211d} Security Software - Type: Type: Type: Graphics Features Compositing: Basic Asynchronous Pan/Zoom: wheel input enabled; scrollbar drag enabled; keyboard enabled; autoscroll enabled WebGL 1 Driver WSI Info: GLX 1.4 GLX_VENDOR(client): Mesa Project and SGI GLX_VENDOR(server): SGI Extensions: GLX_ARB_create_context GLX_ARB_create_context_profile GLX_ARB_create_context_robustness GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_get_proc_address GLX_ARB_multisample GLX_EXT_import_context GLX_EXT_visual_info GLX_EXT_visual_rating GLX_EXT_fbconfig_packed_float GLX_EXT_framebuffer_sRGB GLX_EXT_create_context_es2_profile GLX_EXT_create_context_es_profile GLX_MESA_copy_sub_buffer GLX_MESA_multithread_makecurrent GLX_MESA_query_renderer GLX_MESA_swap_control GLX_OML_swap_method GLX_OML_sync_control GLX_SGI_make_current_read GLX_SGI_swap_control GLX_SGI_video_sync GLX_SGIS_multisample GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_SGIX_visual_select_group GLX_EXT_texture_from_pixmap GLX_INTEL_swap_event GLX_EXT_buffer_age WebGL 1 Driver Renderer: X.Org -- AMD Radeon (TM) R9 390 Series (AMD HAWAII / DRM 3.20.0 / 4.13.0-37-generic, LLVM 5.0.1) WebGL 1 Driver Version: 3.0 Mesa 17.2.4-AMD_17.50 WebGL 1 Driver Extensions: GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_texture GL_EXT_polygon_offset GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_ATI_fragment_shader GL_EXT_stencil_two_side GL_EXT_texture_cube_map GL_NV_depth_clamp GL_NV_fog_distance GL_APPLE_packed_pixels GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_shader_objects GL_ARB_vertex_program GL_ARB_vertex_shader GL_ATI_draw_buffers GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_depth_bounds_test GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_MESA_pack_invert GL_NV_primitive_restart GL_ARB_depth_clamp GL_ARB_fragment_program_shadow GL_ARB_half_float_pixel GL_ARB_occlusion_query2 GL_ARB_point_sprite GL_ARB_shading_language_100 GL_ARB_sync GL_ARB_texture_non_power_of_two GL_ARB_vertex_buffer_object GL_ATI_blend_equation_separate GL_EXT_blend_equation_separate GL_OES_read_format GL_ARB_color_buffer_float GL_ARB_pixel_buffer_object GL_ARB_texture_compression_rgtc GL
[Desktop-packages] [Bug 1406538] Re: Screenshot contains selected area highlight
** Changed in: mate-utils (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1406538 Title: Screenshot contains selected area highlight Status in Linux Mint: Confirmed Status in gnome-screenshot package in Ubuntu: Confirmed Status in mate-utils package in Ubuntu: Fix Committed Bug description: mate-utils_1.8.1-0+rebecca_amd64 If i choose "select area to grab" i almost constantly get an annoying green overlay which is what i just used to highlight the area that i wanted to grab. See attached example. I'm using Mint MATE x64 17.1, software compositing window manager enabled, compiz disabled, VGA AMD radeon 6370M, drivers "xserver-xorg-video-ati" 7.3.0-1-ubuntu3.1, kernel 3.13.0-37-generic x86_64. I remember this happening since mint 13 or so. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1406538/+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 1756006] Re: FFe: Support suspend-to-hibernate
>From systemd point of view, the patches are relatively straight forward, and simply add "one more way to sleep/suspend/hybernate/etc" without affecting any other code paths or any other functionality. Thus i see little risk for landing the systemd patches. If this turns out to be bad, only the policy would need to be change to either not offer it by default, or not use by default. Or some such. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-to-hibernate Status in gnome-settings-daemon package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update
I thought it might be useful for you folks who have compiling experience to compare the compiler switches used in the Trusty build for 57.04 with those from Arch 59.0 (from post #90), so I've listed them in columns (attached), after I attempted to pull the switches out of @herrtmison's screenshot (might be a few errors from that though). There are lots more switches in the Arch version... Perhaps a look at what's different may spark some ideas.. ** Attachment added: "Comparison of Trusty 57.04 compile switches w Arch 59.0" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1711337/+attachment/5090543/+files/Book1.html -- 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/1711337 Title: Firefox crashes at start on armv7L after 55.0.1 update Status in Mozilla Firefox: Expired Status in firefox package in Ubuntu: Confirmed Bug description: Firefox always crashes when launched after the 55.0.1 update on an Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi), even in safe mode. I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for ARM single-board computer) on a similar board (Orange Pi Plus 2e), installed Firefox and experienced the same problem--it won't load without crashing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 55.0.1+build2-0ubuntu0.16.04.2 Uname: Linux 3.4.113-sun8i armv7l AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.20.1-0ubuntu2.10 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jim1138 F pulseaudio /dev/snd/controlC0: jim1138 F pulseaudio BuildID: 20170814194718 Card0.Amixer.info: Card hw:0 'audiocodec'/'audiocodec' Mixer name : '' Components : '' Controls : 12 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'sndhdmi'/'sndhdmi' Mixer name : '' Components : '' Controls : 1 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'hdmi audio format Function',0 Capabilities: enum Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO' Item0: 'pcm' Channel: Unavailable CurrentDesktop: XFCE Date: Thu Aug 17 05:37:00 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.10.1 dev eth0 default via 192.168.10.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.107 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.108 metric 600 Locales: extensions.sqlite corrupt or missing PciMultimedia: PciNetwork: Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718 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) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1711337/+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 1758762] [NEW] Dedug
Private bug reported: can't get rid of it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 BootLog: [[0;32m OK [0m] Started Network Manager. Starting Network Manager Wait Online... Starting Network Manager Script Dispatcher Service... [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 25 19:04:53 2018 DistUpgraded: 2016-09-30 19:40:15,256 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:02a0] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:02a0] InstallationDate: Installed on 2015-10-06 (901 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) MachineType: Dell Inc. Studio 1737 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=61766765-04bf-4526-98f7-7c3d69ae38a1 ro nopat drm.debug=0xe vesafb.invalid=1 plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-09-30 (540 days ago) dmi.bios.date: 02/11/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0P792H dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/11/2009:svnDellInc.:pnStudio1737:pvrA05:rvnDellInc.:rn0P792H:rvrA05:cvnDellInc.:ct8:cvrA05: dmi.product.name: Studio 1737 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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: Sat Mar 24 22:59:12 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21570 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1758762 Title: Dedug Status in xorg package in Ubuntu: New Bug description: can't get rid of it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 BootLog: [[0;32m OK [0m] Started Network Manager. Starting Network Manager Wait Online... Starting Network Manager Script Dispatcher Service... [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 25 19:04:53 2018 DistUpgraded: 2016-09-30 19:40:15,256 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:02a0] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:02a0] InstallationDate: Installed on 2015-10-06 (901 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) MachineType: Dell Inc. Studio 1737 ProcEnviron: LANG
[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()
** Tags added: bugpattern-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1707451 Title: udisksd crashed with SIGSEGV in g_mutex_lock() Status in udisks: New Status in glib package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Triaged Bug description: Showed up after login ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udisks2 2.6.5-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sun Jul 30 00:35:31 2017 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2017-06-22 (37 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170622) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/lib/udisks2/udisksd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f4900fb5c65 : lock xadd %eax,(%rdi) PC (0x7f4900fb5c65) ok source "%eax" ok destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 main () Title: udisksd crashed with SIGSEGV in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: Z87 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1707451/+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 1758763] Re: udisksd crashed with SIGSEGV in g_mutex_lock()
*** This bug is a duplicate of bug 1707451 *** https://bugs.launchpad.net/bugs/1707451 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 #1707451, 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/1758763/+attachment/5090564/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758763/+attachment/5090567/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758763/+attachment/5090575/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758763/+attachment/5090577/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758763/+attachment/5090578/+files/Registers.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758763/+attachment/5090579/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1707451 udisksd crashed with SIGSEGV in g_mutex_lock() ** 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 udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1758763 Title: udisksd crashed with SIGSEGV in g_mutex_lock() Status in udisks2 package in Ubuntu: New Bug description: 18.4 bionic beaver ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CustomUdevRuleFiles: 70-snap.pencilsheep.rules 70-snap.gitkraken.rules 70-snap.discord.rules 70-snap.core.rules Date: Sun Mar 25 18:15:50 2018 ExecutablePath: /usr/lib/udisks2/udisksd MachineType: MSI MS-7976 ProcCmdline: /usr/lib/udisks2/udisksd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0084e11e-8e42-4b53-b01f-a38b41b9b1b1 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7fbdb05e0cd5 : lock xadd %eax,(%rdi) PC (0x7fbdb05e0cd5) ok source "%eax" ok destination "(%rdi)" (0x75736f6e2c777220) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: udisks2 Stacktrace: #0 0x7fbdb05e0cd5 in g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fbdb0598520 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x556d0cec0204 in main () StacktraceTop: g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 main () Title: udisksd crashed with SIGSEGV in g_mutex_lock() UpgradeStatus: Upgraded to bionic on 2018-03-20 (5 days ago) UserGroups: dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.I0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M7 (MS-7976) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7976 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1758763/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Hi I have this problem both on 16.04 and 17.10, and it is NOT related to wifi, since on my 16.04 desktop there is no wifi module at all. I tried installing 5.49 blues on 16.04 host, it does not seem to help, but I can not be 100% sure since I did not check whether exact new bt service was operating. 17.10 contrary is macbook laptop with BCM4360 adapter and wl driver, but disabling wifi and removing the module does not help. Rebooting 17.10 with new audio.conf/hcid.conf and using blueman to pair seems to help, but that can be a coincidence. What steps you want me to make to provide more debug information? -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1651396] Re: Backup fails every time after one incremental file is possibly corrupted
Thanks Naël, your suggestion on Comment #6 worked for me on Ubuntu 17.10. -- 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/1651396 Title: Backup fails every time after one incremental file is possibly corrupted Status in deja-dup package in Ubuntu: Confirmed Bug description: The backup location is on a NAS mounted with NFS. I get this message every time I try to make a new backup: Backup Failed Invalid data - SHA1 hash mismatch for file: duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a439c Manifest hash: b46782fb799c7c5a543ac88d9bfb7cc1df25d38c Can someone recommend a better backup software for personal use? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 20 12:36:15 2016 InstallationDate: Installed on 2014-05-16 (949 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: deja-dup UpgradeStatus: Upgraded to xenial on 2016-08-02 (139 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1651396/+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 1758772] [NEW] Upgrade jabref version
Public bug reported: Package version is 3.8.2+ds-2; latest version is 4.1 (.jar file included, also available here: https://www.fosshub.com/JabRef.html) ** Affects: jabref (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Patch added: "Updated .jar file" https://bugs.launchpad.net/bugs/1758772/+attachment/5090613/+files/JabRef-4.1.jar ** Package changed: network-manager-applet (Ubuntu) => jabref (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1758772 Title: Upgrade jabref version Status in jabref package in Ubuntu: New Bug description: Package version is 3.8.2+ds-2; latest version is 4.1 (.jar file included, also available here: https://www.fosshub.com/JabRef.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jabref/+bug/1758772/+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 1758770] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1754954 *** https://bugs.launchpad.net/bugs/1754954 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 #1754954, 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/1758770/+attachment/5090602/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758770/+attachment/5090604/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758770/+attachment/5090607/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758770/+attachment/5090608/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758770/+attachment/5090609/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758770/+attachment/5090610/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758770/+attachment/5090611/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1754954 ** 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/1758770 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: trying to change background came out this error ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 02:43:10 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-03-21 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) ProcCmdline: gnome-control-center background ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe9fc499a1d:mov0x8(%rdi),%eax PC (0x7fe9fc499a1d) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-control-center 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/gnome-control-center/+bug/1758770/+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 1758773] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758773/+attachment/5090614/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758773/+attachment/5090616/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758773/+attachment/5090619/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758773/+attachment/5090620/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758773/+attachment/5090621/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758773/+attachment/5090622/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758773/+attachment/5090623/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1758773 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Error pop-up after logging into Ubuntu 18.04 beta Gnome 3.28 on Xorg ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 Uname: Linux 4.15.12-041512-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Mar 23 20:36:07 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-05 (171 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 /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to bionic on 2018-03-12 (13 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758773/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
** Summary changed: - [USB-Audio - SteelSeries Arctis 7, playback] No sound at all + [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback -- 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/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback Status in pulseaudio package in Ubuntu: New Bug description: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1716159] Re: gdm greeter does not allow non-US characters (like euro character €) when typing password
** Summary changed: - gdm greeter does not allow euro character (€) when typing password + gdm greeter does not allow non-US characters (like euro character €) when typing password -- 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/1716159 Title: gdm greeter does not allow non-US characters (like euro character €) when typing password Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: In latest Artful (2017-09-08 daily), gdm does not allow to enter the euro character (€) when typing the password (be it with the real keyboard or with the visual on screen keyboard). Steps to reproduce: 1. on the gdm login screen, try to type € in the password field 2. the input is ignored (not big dot is added) 3. if your password contains a € symbol (which is allowed, incliding during installation with ubiquity), you cannot login anymore... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716159/+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 1755144] Re: No audio on vlc or videos sound or video files
Yes, I mentioned that 13 days ago back in comment #2 and again in comment #12. In comments #3 and #13 you told us that was not the problem. ** Changed in: ffmpeg (Ubuntu) Status: New => Invalid -- 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/1755144 Title: No audio on vlc or videos sound or video files Status in ffmpeg package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Up until a few weeks ago there was no problem with playing sound from mp3 files. I have a pair of usb speakers. Audio plays Ok on them for video clips using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok using Rhythmbox. I've also tried vlc 3.0 with no success. Interestingly, the standard Videos app (Totem?) also doesn't play sound on these speakers either of an mp4 file (downloaded from YouTube, though it plays Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I first reported this as bug 1752267 as I thought that the problem was with vlc. On that bug, it was suggested that the problem is with Pulseaudio. Just now, I've tried to play sound through my monitor's built in speakers connected by hdmi (though the monitor displays Ok) with no success even though the built-in speakers play sound using pavucontrol when testing is invoked. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: john 2410 F pulseaudio /dev/snd/controlC0: john 2410 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 12 11:06:46 2018 InstallationDate: Installed on 2016-12-08 (458 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Please log a new bug using this command so that we may examine your system in detail: ubuntu-bug bluez -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1716159] Re: gdm greeter does not allow non-US characters (like euro character €) when typing password
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (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/1716159 Title: gdm greeter does not allow non-US characters (like euro character €) when typing password Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: In latest Artful (2017-09-08 daily), gdm does not allow to enter the euro character (€) when typing the password (be it with the real keyboard or with the visual on screen keyboard). Steps to reproduce: 1. on the gdm login screen, try to type € in the password field 2. the input is ignored (not big dot is added) 3. if your password contains a € symbol (which is allowed, incliding during installation with ubiquity), you cannot login anymore... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716159/+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 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Summary changed: - totem crashed with signal 5 + totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() ** Information type changed from Private to Public -- 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/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() Status in totem package in Ubuntu: New Bug description: totem crashed with signal 5 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 11:26:51 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-05-04 (323 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 5 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with signal 5 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/totem/+bug/1758287/+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 1721428] Re: Artful (17.10) Session logout after screen turned off
See comments #52 and #64. -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1758706] Re: Session logs out after screen turns off
Please report crash files using this command only: ubuntu-bug _usr_bin_Xwayland.1000.crash And then let us know the ID of the newly-create bug. ** This bug is no longer a duplicate of bug 1721428 Artful (17.10) Session logout after screen turned off ** Information type changed from Public to Private ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1758706 Title: Session logs out after screen turns off Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is the same bug as #1721428 :/var/crash$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 I am using a NUC7i7BNH connected via HDMI. The screen turns off after 5 minutes of inactivity and automatic screen lock is also turned on to lock the screen after screen turns off. When I resume activity, I am presented with the logon screen, which after entering my password, reloads another logon screen. When I then enter my password the second time, I am logged in, but it is a new session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758706/+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 1758528] Re: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from gbm_get_next_fb_id()
** Summary changed: - gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() + gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from gbm_get_next_fb_id() ** Information type changed from Private to Public -- 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/1758528 Title: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from gbm_get_next_fb_id() Status in gnome-shell package in Ubuntu: New Bug description: Randomly crashes in minutes following a reboot. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Mar 22 21:39:40 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) 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: 0x7fce03ec7c90 : mov (%rdi),%rax PC (0x7fce03ec7c90) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: gbm_bo_get_plane_count () from /usr/lib/x86_64-linux-gnu/libgbm.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 cogl_onscreen_swap_buffers_with_damage () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() 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/1758528/+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 1716159] Re: gdm greeter does not allow non-US characters (like euro character €) when typing password
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/1716159 Title: gdm greeter does not allow non-US characters (like euro character €) when typing password Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: In latest Artful (2017-09-08 daily), gdm does not allow to enter the euro character (€) when typing the password (be it with the real keyboard or with the visual on screen keyboard). Steps to reproduce: 1. on the gdm login screen, try to type € in the password field 2. the input is ignored (not big dot is added) 3. if your password contains a € symbol (which is allowed, incliding during installation with ubiquity), you cannot login anymore... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716159/+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 1756508] Re: Gnome-shell CPU load dramatically high and stuck high with Eclipse
Yes you're right; that is strange. Maybe Eclipse is only the trigger for a gnome-shell bug here. -- 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/1756508 Title: Gnome-shell CPU load dramatically high and stuck high with Eclipse Status in gnome-shell package in Ubuntu: New Bug description: Hello, I recently upgraded Ubuntu from 16.04 to 17.10. Since I did, I cannot use Eclipse any more. I can start Eclipse, but as soon as I try to de-maximize it, gnome-shell CPU load raises to 80%-95% and remains that level. I ¥t sometimes drops a bit down to 70% but still keeps high and blocks everything. Even if by chance and patience I succeed closing Eclipse, the CPU load keeps high. Until now I found no way to recover. Ubuntu 17.10 Gnome 3.26.2 Runs in Virtual box Core i7x2 8 GB RAM Eclipse Photon 4.8 M6 But same happened with Oyxgen 4.7.2 Other info needed, please let me know... not sure how to circle this closer. Once it happens, it's over . --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-02-20 (759 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-37-generic x86_64 UpgradeStatus: Upgraded to artful on 2018-01-18 (60 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756508/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
You should ignore most gnome-shell log messages as they are almost always irrelevant to whatever problem you're trying to diagnose :P -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+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 1757299] Re: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications
just had a lockup watching a youtube video in firefox-esr. i did something extremely simple, i think it was push the pavucontrol window behind the firefox-esr window, which did so, but immediately thereafter the video image froze, the mouse could still move the cursor but the mouse and keyboard were otherwise unable to get any response, not even to ctl-alt-Fn, nothing visible would be expected from ctl-alt- PrintScreen-s, saw no response to ctl-alt-PrintScreen-e either, nor, surprisingly, to ctl-alt-PrintScreen-k. The sound played on via pusleaudio and bluetooth into my headphones for 2 more minutes, then it fell silent. After 10 minutes it all remained thus. i tried to login via ssh but unfortunately my phone was connected to mobile data but not wifi so i presumed ubuntu was not responding via ssh either, heck it likely would have if the phone's wifi radio was enabled. well this occurrence does serve the purpose of verifying that the problem does occur in bionic either while playing video or not playing video. the system did respond to ctl-alt-PrintScreen-b and booted up normally. in /var/crash all i found was a file named .lock, zero length, dated 3-22 12:42:30pm. dunno what that's from, curious, no bash history survived from that day, this is what i found from around then in syslog: Mar 22 12:17:01 op755 CRON[7216]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 22 12:42:28 op755 kernel: [76631.137616] Web Content[4830]: segfault at fffe8 ip 7fc182a1aab1 sp 7ffee816bb10 error 4 in libxul.so[7fc17ee3+4e3] Mar 22 13:01:54 op755 bluetoothd[577]: /org/bluez/hci0/dev_00_0C_8A_AA_FE_70/fd1: fd(36) ready Mar 22 13:01:55 op755 rtkit-daemon[4718]: Supervising 1 threads of 1 processes of 1 users. Mar 22 13:01:55 op755 rtkit-daemon[4718]: Successfully made thread 7434 of process 4717 (n/a) owned by '444' RT at priority 5. Mar 22 13:01:55 op755 rtkit-daemon[4718]: Supervising 2 threads of 1 processes of 1 users. Mar 22 13:01:55 op755 kernel: [77798.576032] input: 00:0C:8A:AA:FE:70 as /devices/virtual/input/input9 Mar 22 13:12:21 op755 kernel: [78424.582540] perf: interrupt took too long (4900 > 4897), lowering kernel.perf_event_max_sample_rate to 40750 Mar 22 13:17:01 op755 CRON[7486]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 22 14:17:01 op755 CRON[7648]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) and found this in apport.log: ERROR: apport (pid 1591) Sat Mar 10 08:04:36 2018: called for pid 1582, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 1591) Sat Mar 10 08:04:36 2018: script: /usr/bin/blueman-manager, interpreted by /usr/bin/python3.6 (command line "/usr/bin/python3 /usr/bin/blueman-manager") ERROR: apport (pid 1591) Sat Mar 10 08:04:36 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 1591) Sat Mar 10 08:04:40 2018: wrote report /var/crash/_usr_bin_blueman-manager.444.crash ERROR: apport (pid 1759) Sun Mar 18 06:47:37 2018: called for pid 1643, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 1759) Sun Mar 18 06:47:37 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f ERROR: apport (pid 1759) Sun Mar 18 06:47:37 2018: executable version is blacklisted, ignoring ERROR: apport (pid 2730) Tue Mar 20 14:19:04 2018: called for pid 1219, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2730) Tue Mar 20 14:19:04 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f ERROR: apport (pid 2730) Tue Mar 20 14:19:04 2018: executable version is blacklisted, ignoring ERROR: apport (pid 2755) Tue Mar 20 14:19:21 2018: called for pid 2732, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2755) Tue Mar 20 14:19:21 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f ERROR: apport (pid 2755) Tue Mar 20 14:19:21 2018: executable version is blacklisted, ignoring ERROR: apport (pid 4370) Tue Mar 20 19:04:53 2018: called for pid 4294, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 4370) Tue Mar 20 19:04:53 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f ERROR: apport (pid 4370) Tue Mar 20 19:04:53 2018: executable version is blacklisted, ignoring ERROR: apport (pid 7315) Thu Mar 22 12:42:30 2018: called for pid 4830, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7315) Thu Mar 22 12:42:30 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f
[Desktop-packages] [Bug 1758569] [NEW] can't switch to bluetooth speakers
You have been subscribed to a public bug: I'm not really sure this problem is with bluez, pulseaudio or firefox. The main symptom is that Firefox refuses to send audio to my AD2P compliant bluetooth speakers. I can select the speakers with the gnome- control-center for bluetooth and play the test sounds (even while FF is playing sound through the computer (DELL N7010 laptop) speakers. Even VLC has the same problem so I suspect this is a system problem and not an application problem. Note - I installed pavucontrol and was able to switch the audio of a playing youtube to the bluetooth speakers. now for your recommended info lsb_release says Ubuntu 17.10 Firefox is Version 59.0.1 dpkg -l | grep -i blue says ii bluez 5.46-0ubuntu3 amd64 Bluetooth tools and daemons ii bluez-cups 5.46-0ubuntu3 amd64 Bluetooth printer driver for CUPS ii bluez-obexd 5.46-0ubuntu3 amd64 bluez obex daemon ii bluez-tools 0.2.0~20140808-5build1 amd64 Set of tools to manage Bluetooth devices for linux ii gir1.2-gnomebluetooth-1.0:amd64 3.26.1-1 amd64 Introspection data for GnomeBluetooth ii gnome-bluetooth 3.26.1-1 amd64 GNOME Bluetooth tools ii libbluetooth3:amd64 5.46-0ubuntu3 amd64 Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.26.1-1 amd64 GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth 1:10.0-2ubuntu3.1 amd64 Bluetooth module for PulseAudio sound server ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 14:10:02 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron N7010 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=94a7c54a-20a6-4bd0-905c-918de9b5ff61 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/31/2011:svnDellInc.:pnInspironN7010:pvrA11:rvnDellInc.:rn08VFX1:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N7010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: C0:CB:38:C2:18:51 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING INQUIRY RX bytes:234685 acl:43 sco:0 events:33407 errors:0 TX bytes:56372584 acl:66043 sco:0 commands:212 errors:0 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- can't switch to bluetooth speakers https://bugs.launchpad.net/bugs/1758569 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. -- 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 444345] Re: URL tooltip does not have a consistent size
** Changed in: epiphany-browser Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/444345 Title: URL tooltip does not have a consistent size Status in Epiphany Browser: Incomplete Status in epiphany-browser package in Ubuntu: Triaged Bug description: Binary package hint: epiphany-browser The URL tooltip (which is only visible with the statusbar disabled) does not use a consistent font size, instead it seems to use one derived from the CSS font-size property of the body element of the currently visible page. To manage notifications about this bug go to: https://bugs.launchpad.net/epiphany-browser/+bug/444345/+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 1758569] Re: can't switch to bluetooth speakers
** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu) ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags added: a2dp -- 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/1758569 Title: can't switch to bluetooth speakers Status in firefox package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I'm not really sure this problem is with bluez, pulseaudio or firefox. The main symptom is that Firefox refuses to send audio to my AD2P compliant bluetooth speakers. I can select the speakers with the gnome-control-center for bluetooth and play the test sounds (even while FF is playing sound through the computer (DELL N7010 laptop) speakers. Even VLC has the same problem so I suspect this is a system problem and not an application problem. Note - I installed pavucontrol and was able to switch the audio of a playing youtube to the bluetooth speakers. now for your recommended info lsb_release says Ubuntu 17.10 Firefox is Version 59.0.1 dpkg -l | grep -i blue says ii bluez 5.46-0ubuntu3 amd64 Bluetooth tools and daemons ii bluez-cups 5.46-0ubuntu3 amd64 Bluetooth printer driver for CUPS ii bluez-obexd 5.46-0ubuntu3 amd64 bluez obex daemon ii bluez-tools 0.2.0~20140808-5build1 amd64 Set of tools to manage Bluetooth devices for linux ii gir1.2-gnomebluetooth-1.0:amd64 3.26.1-1 amd64 Introspection data for GnomeBluetooth ii gnome-bluetooth 3.26.1-1 amd64 GNOME Bluetooth tools ii libbluetooth3:amd64 5.46-0ubuntu3 amd64 Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.26.1-1 amd64 GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth 1:10.0-2ubuntu3.1 amd64 Bluetooth module for PulseAudio sound server ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 14:10:02 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron N7010 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=94a7c54a-20a6-4bd0-905c-918de9b5ff61 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/31/2011:svnDellInc.:pnInspironN7010:pvrA11:rvnDellInc.:rn08VFX1:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N7010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: C0:CB:38:C2:18:51 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING INQUIRY RX bytes:234685 acl:43 sco:0 events:33407 errors:0 TX bytes:56372584 acl:66043 sco:0 commands:212 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758569/+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 1758525] Re: Elantech Touchpad - theres no automatic stop while tipping after changing to xorg
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1758525 Title: Elantech Touchpad - theres no automatic stop while tipping after changing to xorg Status in gnome-shell package in Ubuntu: Incomplete Bug description: Under Wayland Elantech touchpad is working well, not so under change to xorg display server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758525/+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 1758792] Re: Session logs out after screen turns off
*** This bug is a duplicate of bug 1731911 *** https://bugs.launchpad.net/bugs/1731911 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 #1731911, 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/1758792/+attachment/5090639/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758792/+attachment/5090642/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758792/+attachment/5090649/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758792/+attachment/5090651/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758792/+attachment/5090652/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758792/+attachment/5090653/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758792/+attachment/5090654/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1731911 Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() ** 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 xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1758792 Title: Session logs out after screen turns off Status in xorg-server package in Ubuntu: New Bug description: Refer to https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1758706 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 22:22:37 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExecutableTimestamp: 1508068793 GraphicsCard: Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2068] InstallationDate: Installed on 2018-03-24 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7i7BNH ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 ProcCwd: /home/stuart ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/21/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0061.2017.1221.1952 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0061.2017.1221.1952:bd12/21/2017:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xs
[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
@Kir Kolyshkin - did trying the commits on the master branch of mutter after 3.26 fix this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Status in mutter package in Fedora: Fix Committed Bug description: https://errors.ubuntu.com/problem/c27f5c4fef272640ec1027318712f0434c7c8857 --- no idea how to reproduce ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.5-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-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Nov 13 13:55:16 2017 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1507] InstallationDate: Installed on 2013-09-03 (1531 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1731911/+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 1757299] Re: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications
** Changed in: xorg (Ubuntu) Status: Incomplete => New -- 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/1757299 Title: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications Status in xorg package in Ubuntu: New Bug description: The problem is that after launching a few applications, the GUI may become unresponsive, although this is not consistently reproducible. When the GUI is unresponsive, it is correlated to high CPU utilization of xorg. An example reproduction scenario is launch the following in order, and quickly: startx xterm via twm another xterm via the first xterm tmux firefox-esr bluetooth-manager pavucontrol While the above are launching, maximize the xterm running tmux, and the GUI immediately becomes unresponsive. For example, Ctrl+Alt+Fn don't respond. After this, I logged in via ssh, attached to tmux, launched htop, copied htop output, which shows xorg at 94.6 CPU%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd * Starting AppArmor profiles [160G [154G[ OK ] * Restoring resolver state... [160G [154G[ OK ] CompositorRunning: None Date: Tue Mar 20 17:15:16 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] JournalErrors: -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 CDT. -- Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon already running. MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1757299/+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 1744653] Re: gnome-control-center crashed with SIGSEGV in panel_refresh_device_titles()
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1744653 Title: gnome-control-center crashed with SIGSEGV in panel_refresh_device_titles() Status in gnome-control-center package in Ubuntu: Expired Bug description: This error occurred for no apparent reason. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 04:33:40 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-12 (71 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x556a65d4c303:mov0x8(%rax),%edx PC (0x556a65d4c303) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () 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 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_cclosure_marshal_VOID__OBJECTv() 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/1744653/+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 1744511] Re: Keyboard and mouse stop working randomly
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1744511 Title: Keyboard and mouse stop working randomly Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: Lenovo Yogo 300 has a keyboard, touch pad and touch screen. Keyboard and mouse stop working, I am unable to see any pattern to the problem. This affects both Wayland and Xorg sessions, log-in and lock screen and desktop environment. Originally mistaken for a full system freeze, but touch-screen works fine. Putting computer into standby and resuming resolves the issue, but sometimes happens within seconds of resuming, sometimes it works for ages without a problem. Filed against gdm3 due to these events found in the log, but this may be unrelated: Jan 20 23:20:51 phill-Lenovo-YOGA-300-11IBY /usr/lib/gdm3/gdm-x-session[1234]: (II) event8 - (II) PEAQ WMI hotkeys: (II) device removed Jan 20 23:20:51 phill-Lenovo-YOGA-300-11IBY /usr/lib/gdm3/gdm-x-session[1234]: (II) event4 - (II) AT Translated Set 2 keyboard: (II) device removed Problem started immediately after installing 17.10.1, 17.04 had been used flawlessly since it's release on this hardware. Note that "gnome- session" is installed which I normally use, but as the problem occurs on the lock and login screens I guess it's nothing to do with that. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 20 23:31:03 2018 InstallationDate: Installed on 2018-01-18 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1744511/+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 1744511] Re: Keyboard and mouse stop working randomly
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- 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/1744511 Title: Keyboard and mouse stop working randomly Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: Lenovo Yogo 300 has a keyboard, touch pad and touch screen. Keyboard and mouse stop working, I am unable to see any pattern to the problem. This affects both Wayland and Xorg sessions, log-in and lock screen and desktop environment. Originally mistaken for a full system freeze, but touch-screen works fine. Putting computer into standby and resuming resolves the issue, but sometimes happens within seconds of resuming, sometimes it works for ages without a problem. Filed against gdm3 due to these events found in the log, but this may be unrelated: Jan 20 23:20:51 phill-Lenovo-YOGA-300-11IBY /usr/lib/gdm3/gdm-x-session[1234]: (II) event8 - (II) PEAQ WMI hotkeys: (II) device removed Jan 20 23:20:51 phill-Lenovo-YOGA-300-11IBY /usr/lib/gdm3/gdm-x-session[1234]: (II) event4 - (II) AT Translated Set 2 keyboard: (II) device removed Problem started immediately after installing 17.10.1, 17.04 had been used flawlessly since it's release on this hardware. Note that "gnome- session" is installed which I normally use, but as the problem occurs on the lock and login screens I guess it's nothing to do with that. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 20 23:31:03 2018 InstallationDate: Installed on 2018-01-18 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1744511/+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 1758589] Re: The wifi will be disconnected and the only thing I can do is to reboot the laptop
** Also affects: linux (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/1758589 Title: The wifi will be disconnected and the only thing I can do is to reboot the laptop Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: First of all, I am not sure whether it's true that this is a bug of network-manager, but it is true that this should be a bug related with network (wifi connection). Here is the issue: Every time after I login into the account, about 20 minutes later, the wifi will be disconnected automatically. I even cannot reconnect the wifi manually, the only thing that I can do is to reboot the laptop. After login again, wifi can be connected (but through manual way). By the way, during the period of wifi disconnection, I checked the "Wi-Fi Networks" by click "Select Network" in order to try to reconnect it manually. But I found that there is only one SSID which previously the laptop connected to. However, I was definitely sure that there should be more than one SSID being showed in the wifi list. Even for this only one SSID, like I mentioned before, I cannot reconnect manually unless I reboot the system. Finally, I set the wifi to be connected automatically after I login to the system, however, it just can't. I can only connect to the wifi manually after I login to the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 19:02:12 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-15 (68 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH wlp4s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 WolfieNet-Secure eb45c742-ba31-4f31-acf2-13a2768bcc29 /org/freedesktop/NetworkManager/ActiveConnection/5 enp5s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758589/+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