[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
I understand why /usr/lib64/ doesn't work right now on Ubuntu (that's a directory commonly used by Fedora and Red Hat distros). I don't understand why /usr/lib/sane/ doesn't work according to the comments here. When sane-backends was converted to multiarch, a patch was added that I think was supposed to enable /usr/lib/sane/ to still be supported. https://jff.email/cgit/sane-backends.git/commit/?id=ac1cb335be https://jff.email/cgit/sane-backends.git/tree/debian/patches/0125-multiarch_dll_search_path.patch If that patch worked, then maybe it makes sense to just add /usr/lib64/ there too. I don't have a scanner myself to test any of this. -- 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/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1794213] Re: Crash on Upgrade to 18.10 from 18.04 Network Not Available
I ran sudo apt-get autoclean, and other command line clean up tools and tried again. I was able to upgrade then. Not sure why just running some cleaning programs worked but did and now I have 18.10 running. Thank you You can marked this solved. Scott Stehno On 09/25/2018 08:46 AM, Colin Watson wrote: > ** Project changed: launchpad => appstream (Ubuntu) > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade to 18.10 from 18.04 Network Not Available Status in appstream package in Ubuntu: New Bug description: E:Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi', E:Sub-process returned an error code The above error is in the small box. The information below is in the terminal window that I thought might give clues on what happened on disto upgrade to 18.10 from command line. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXT_EXEC '/usr/bin/firefox' from launcher. kdeinit5: preparing to launch '/usr/bin/firefox' kdeinit5: PID 5799 terminated. (appstreamcli:6926): GLib-CRITICAL **: 21:59:50.626: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:6926): GLib-CRITICAL **: 21:59:50.626: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:6926): GLib-ERROR **: 21:59:50.626: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) QXcbConnection: XCB error: 3 (BadWindow), sequence: 792, resource id: 39845978, major code: 40 (TranslateCoords), minor code: 0 (appstreamcli:8091): GLib-CRITICAL **: 22:00:11.961: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:8091): GLib-CRITICAL **: 22:00:11.961: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:8091): GLib-ERROR **: 22:00:11.961: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) (appstreamcli:8899): GLib-CRITICAL **: 22:00:17.376: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:8899): GLib-CRITICAL **: 22:00:17.376: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:8899): GLib-ERROR **: 22:00:17.376: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) (appstreamcli:9701): GLib-CRITICAL **: 22:00:21.530: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:9701): GLib-CRITICAL **: 22:00:21.530: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:9701): GLib-ERROR **: 22:00:21.530: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) kdeinit5: PID 6868 terminated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+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 1772191] Re: GNOME Mines desktop file icon too small
** Also affects: gnome-mines (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-mines (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-mines (Ubuntu Bionic) Status: New => Triaged ** Changed in: gnome-mines (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: gnome-mines (Ubuntu) Importance: Undecided => Low ** Tags added: cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mines in Ubuntu. https://bugs.launchpad.net/bugs/1772191 Title: GNOME Mines desktop file icon too small Status in gnome-mines package in Ubuntu: Fix Committed Status in gnome-mines source package in Bionic: Triaged Bug description: The icon of GNOME Mines in GNOME Shell Overview in Ubuntu 18.04 is blurred. This is because the icon resolution is too low. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1772191/+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 1794408] [NEW] package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
Public bug reported: Error during installation of python3 idle in ubuntu 18.04 LTS Errors were encountered while processing: gdm3 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_24_26_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 26 07:56:39 2018 DpkgHistoryLog: Start-Date: 2018-09-26 07:56:34 Commandline: apt-get install idle-python3.6 Requested-By: nikhil (1000) Install: libtcl8.6:amd64 (8.6.8+dfsg-3, automatic), blt:amd64 (2.5.3+dfsg-4, automatic), idle-python3.6:amd64 (3.6.6-1~18.04), tk8.6-blt2.5:amd64 (2.5.3+dfsg-4, automatic), python3-tk:amd64 (3.6.5-3, automatic), libtk8.6:amd64 (8.6.8-4, automatic) DuplicateSignature: package:gdm3:3.28.2-0ubuntu1.2 Setting up gdm3 (3.28.2-0ubuntu1.2) ... dpkg: error processing package gdm3 (--configure): installed gdm3 package post-installation script subprocess returned error exit status 10 ErrorMessage: installed gdm3 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-05-27 (121 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gdm3 Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1794408 Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 Status in gdm3 package in Ubuntu: New Bug description: Error during installation of python3 idle in ubuntu 18.04 LTS Errors were encountered while processing: gdm3 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_24_26_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 26 07:56:39 2018 DpkgHistoryLog: Start-Date: 2018-09-26 07:56:34 Commandline: apt-get install idle-python3.6 Requested-By: nikhil (1000) Install: libtcl8.6:amd64 (8.6.8+dfsg-3, automatic), blt:amd64 (2.5.3+dfsg-4, automatic), idle-python3.6:amd64 (3.6.6-1~18.04), tk8.6-blt2.5:amd64 (2.5.3+dfsg-4, automatic), python3-tk:amd64 (3.6.5-3, automatic), libtk8.6:amd64 (8.6.8-4, automatic) DuplicateSignature: package:gdm3:3.28.2-0ubuntu1.2 Setting up gdm3 (3.28.2-0ubuntu1.2) ... dpkg: error processing package gdm3 (--configure): installed gdm3 package post-installation script subprocess returned error exit status 10 ErrorMessage: installed gdm3 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-05-27 (121 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gdm3 Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794408/+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 1794377] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libglvnd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1794377 Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Status in libglvnd package in Ubuntu: Confirmed Bug description: keeps crashing ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Sep 25 16:20:21 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-MFEi2z/076-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2017-10-27 (333 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-06-14 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794377/+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 1794191] Re: Snap Store fails to return to main page after package installation
The back button on top doesn't respond, but the snap store reverts back to the main page after reboot and did work properly for one installation before getting stuck on the application installation page again. -- 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/1794191 Title: Snap Store fails to return to main page after package installation Status in gnome-software package in Ubuntu: Confirmed Bug description: Version 3.29.1+git218.7e7e8cd After installing an application the snap store stayed on the application installation page and wont return to the main page where one can browse or install other applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1794191/+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 1755503] Re: Xorg crashed with SIGSEGV in miPointerSetPosition()
*** This bug is a duplicate of bug 1681084 *** https://bugs.launchpad.net/bugs/1681084 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- 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/1755503 Title: Xorg crashed with SIGSEGV in miPointerSetPosition() Status in xorg-server package in Ubuntu: Confirmed Bug description: System went to login page saying "account was suspended due to inactivity" But the system was like it restarted. All my sessions were closed. And now my speakers are not working and in output devices list is says "Dummy speakers". ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu2 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' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 13 20:06:43 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:058f] InstallationDate: Installed on 2018-03-10 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) MachineType: Dell Inc. Inspiron 5523 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d0bff72f-b33d-4274-801b-ebaef7525419 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x561c5d7d6fc0:mov0x40(%rbx),%rax PC (0x561c5d7d6fc0) ok source "0x40(%rbx)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: ?? () miPointerSetPosition () ?? () ?? () GetPointerEvents () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0GKGJG dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5523 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 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-server/+bug/1755503/+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 1704893] Re: Writer closes when finished loading without error
** Changed in: libreoffice (Ubuntu) Status: Expired => New -- 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/1704893 Title: Writer closes when finished loading without error Status in libreoffice package in Ubuntu: New Bug description: When I attempt to open a document in LibreOffice Writer, by any method, I am shown a loading dialog with a progress bar. The progress bar advances to about 95%, then disappears, and nothing happens. I have tried launching LibreOffice Writer by several methods: - Start LibreOffice, click "Create/Writer Document" - Open a filetype associated with LibreOffice Writer in a file browser - Launch libreoffice --writer in a terminal (This outputs nothing) I have confirmed via ps -A that LibreOffice is truly closed, and not merely invisible. Things I tried, with no difference: - sudo apt-get install --reinstall libreoffice-writer - rm ~/.config/libreoffice - cp -a /usr/lib/libreoffice/share ~/.config/libreoffice/4/user This is a fresh install of LibreOffice on a fresh install of Lubuntu. Other LibreOffice applications, such as Calc, work fine. I believe the same problem may have been reported at - https://askubuntu.com/questions/129383/libreoffice-not-opening - https://askubuntu.com/questions/697309/unable-to-open-libreoffice-writer?rq=1 Nothing there helped me. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libreoffice-writer 1:5.3.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.4 Architecture: i386 CurrentDesktop: LXDE Date: Mon Jul 17 20:22:50 2017 InstallationDate: Installed on 2017-07-05 (12 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1704893/+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 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1792745 Title: NetworkManager crashed with SIGSEGV in _int_malloc() Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Bug description: I’m seeing NetworkManager crash several times on startup and on resume from suspend. Apport doesn’t catch those for some reason, but this happened when I tried to reproduce by manually running NetworkManager --debug. (Different crash from bug 1792743? Also apport-retrace didn’t seem to like that one.) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Sat Sep 15 14:04:50 2018 EcryptfsInUse: Yes ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. Do not edit. InstallationDate: Installed on 2016-02-19 (939 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false ProcCmdline: NetworkManager --debug SegvAnalysis: Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp %rcx,0x18(%rdx) PC (0x7f79966ea378) ok source "%rcx" ok destination "0x18(%rdx)" (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: _int_malloc (av=av@entry=0x7f799683ac40 , bytes=bytes@entry=4096) at malloc.c:4014 __libc_calloc (n=, elem_size=) at malloc.c:3420 g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314 _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88 Title: NetworkManager crashed with SIGSEGV in _int_malloc() UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1792745/+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 1704893] Re: Writer closes when finished loading without error
@Olivier Tilloy: I continue to experience this problem on various systems. It's been a while since I tested with fresh installations, and I _was_ preserving various ~/.config files between those. I did not, however, preserve anything in ~/.config/libreoffice, and removing this directory has no effect. The gtk theme warnings show up for virtually all GTK apps and have to do with obsolete features of the GTK theme. They don't cause problems for any other app and I don't think they're the problem since I just crashed LibreOffice again using this command: GTK_THEME=adwaita libreoffice testfile.docx with LibreOffice 5.4.6.2 40m0(Build:2) on Lubuntu 17.10. -- 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/1704893 Title: Writer closes when finished loading without error Status in libreoffice package in Ubuntu: Expired Bug description: When I attempt to open a document in LibreOffice Writer, by any method, I am shown a loading dialog with a progress bar. The progress bar advances to about 95%, then disappears, and nothing happens. I have tried launching LibreOffice Writer by several methods: - Start LibreOffice, click "Create/Writer Document" - Open a filetype associated with LibreOffice Writer in a file browser - Launch libreoffice --writer in a terminal (This outputs nothing) I have confirmed via ps -A that LibreOffice is truly closed, and not merely invisible. Things I tried, with no difference: - sudo apt-get install --reinstall libreoffice-writer - rm ~/.config/libreoffice - cp -a /usr/lib/libreoffice/share ~/.config/libreoffice/4/user This is a fresh install of LibreOffice on a fresh install of Lubuntu. Other LibreOffice applications, such as Calc, work fine. I believe the same problem may have been reported at - https://askubuntu.com/questions/129383/libreoffice-not-opening - https://askubuntu.com/questions/697309/unable-to-open-libreoffice-writer?rq=1 Nothing there helped me. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libreoffice-writer 1:5.3.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.4 Architecture: i386 CurrentDesktop: LXDE Date: Mon Jul 17 20:22:50 2017 InstallationDate: Installed on 2017-07-05 (12 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1704893/+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 1724919] Re: Bluetooth headphones only use A2DP when connected manually
Same as you, Ubuntu 18.04 Sony mdr-zx220bt. If i want to have "good" sound i have to disconnect and connect manually... -- 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/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Confirmed Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1794377] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1794377 Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Status in libglvnd package in Ubuntu: New Bug description: keeps crashing ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Sep 25 16:20:21 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-MFEi2z/076-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2017-10-27 (333 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-06-14 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794377/+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 1794377] [NEW] package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-34
Public bug reported: keeps crashing ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Sep 25 16:20:21 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-MFEi2z/076-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2017-10-27 (333 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-06-14 (103 days ago) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1794377 Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Status in libglvnd package in Ubuntu: New Bug description: keeps crashing ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Sep 25 16:20:21 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-MFEi2z/076-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2017-10-27 (333 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-06-14 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794377/+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 1794317] Re: Scale of screensaver login box is far too large on 3000x2000 display when GUI scale is set to 200%
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screensaver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1794317 Title: Scale of screensaver login box is far too large on 3000x2000 display when GUI scale is set to 200% Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: When locking the desktop, the gnome-screensaver login/password prompt box is not properly scaled. My display is 13.9" with a resolution of 3000x2000. This happens when the scale of the GUI in Budgie settings is set to 200%, but the box appears to scale relatively well when the scale of the GUI is set to 100% (while considering everything is much smaller at that scale). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Sep 25 11:25:29 2018 InstallationDate: Installed on 2018-09-18 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1794317/+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 1794365] [NEW] gnome-sudoku not showing in HUD for "sudoku"
Public bug reported: When I open the HUD in bionic unity and type "sudoku" nothing is shown even though gnome-sudoku is installed. ** Affects: gnome-sudoku (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1794365 Title: gnome-sudoku not showing in HUD for "sudoku" Status in gnome-sudoku package in Ubuntu: New Bug description: When I open the HUD in bionic unity and type "sudoku" nothing is shown even though gnome-sudoku is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1794365/+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 1794355] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340
*** This bug is a duplicate of bug 1791542 *** https://bugs.launchpad.net/bugs/1791542 ** This bug has been marked a duplicate of bug 1791542 package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1794355 Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Status in libglvnd package in Ubuntu: New Bug description: Error occured when upgrading packages with software updater. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Sep 25 22:21:38 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Y1jaYH/32-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-05-04 (143 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794355/+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 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.
Title of this bug is: [QUOTE] Two Wi-Fi network applets appear after logging back into live- usb Lubuntu 18.04 session. [/QUOTE] However, this also affects Lubuntu 18.04.1 installed to my HDD; not just live-usb. -- 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/1761606 Title: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session. Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Lubuntu 18.04 ISO version: 20180404 network-manager-applet version: 1.8.10-2ubuntu1 After logging into my Wi-Fi network then logging out then logging back into the Live-USB session Two Wi-Fi network applets appeared where One would be the expected outcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CasperVersion: 1.392 CurrentDesktop: LXDE Date: Thu Apr 5 21:06:24 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 600 LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134 wifi 1522962221 Thu Apr 5 21:03:41 2018 yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 472b45a7-c95b-3638-b452-3f6720688df8 ethernet 1522961321 Thu Apr 5 20:48:41 2018 yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134 /org/freedesktop/NetworkManager/ActiveConnection/2 enp0s25 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.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1761606/+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 1794355] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1794355 Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Status in libglvnd package in Ubuntu: New Bug description: Error occured when upgrading packages with software updater. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Sep 25 22:21:38 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Y1jaYH/32-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-05-04 (143 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794355/+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 1794354] [NEW] [snap] emoji show as black and white if fonts-symbola is installed
Public bug reported: I'm using the Chromium Snap from the Beta channel. Test Case = 0. Be sure you don't have the Chromium deb running. 1. Visit https://launchpad.net/bugs/1779569 The rainbow emoji should show in color 2. sudo apt install fonts-symbola 3. Close Chromium. Wait a few moments to make sure it closes then open it and repeat step 1 4. The rainbow emoji shows in black and white Other Info == Firefox and GTK apps like gedit correctly show in color as long as fonts-noto-color-emoji is installed, regardless of whether fonts-symbola is also installed. I also was unable to duplicate this bug with the Firefox Snap [edge channel 63.0b9-1 (134)]. System Info === Ubuntu 18.10 fonts-noto-color-emoji 0~20180810-1 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://forum.snapcraft.io/ license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refresh-date: 8 days ago, at 13:41 EDT channels: stable:69.0.3497.100 (494) 141MB - candidate: 69.0.3497.100 (494) 141MB - beta: 70.0.3538.16 (487) 142MB - edge: 70.0.3538.9 (472) 142MB - installed: 70.0.3538.16 (487) 142MB - ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1794354 Title: [snap] emoji show as black and white if fonts-symbola is installed Status in chromium-browser package in Ubuntu: New Bug description: I'm using the Chromium Snap from the Beta channel. Test Case = 0. Be sure you don't have the Chromium deb running. 1. Visit https://launchpad.net/bugs/1779569 The rainbow emoji should show in color 2. sudo apt install fonts-symbola 3. Close Chromium. Wait a few moments to make sure it closes then open it and repeat step 1 4. The rainbow emoji shows in black and white Other Info == Firefox and GTK apps like gedit correctly show in color as long as fonts-noto-color-emoji is installed, regardless of whether fonts-symbola is also installed. I also was unable to duplicate this bug with the Firefox Snap [edge channel 63.0b9-1 (134)]. System Info === Ubuntu 18.10 fonts-noto-color-emoji 0~20180810-1 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://forum.snapcraft.io/ license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refresh-date: 8 days ago, at 13:41 EDT channels: stable:69.0.3497.100 (494) 141MB - candidate: 69.0.3497.100 (494) 141MB - beta: 70.0.3538.16 (487) 142MB - edge: 70.0.3538.9 (472) 142MB - installed: 70.0.3538.16 (487) 142MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1794354/+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 1794354] Re: emoji show as black and white if fonts-symbola is installed
What distro version are you building the Snap from? Maybe you need fontconfig from bionic? ** Summary changed: - emoji show as black and white if fonts-symbola is installed + [snap] emoji show as black and white if fonts-symbola is installed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1794354 Title: [snap] emoji show as black and white if fonts-symbola is installed Status in chromium-browser package in Ubuntu: New Bug description: I'm using the Chromium Snap from the Beta channel. Test Case = 0. Be sure you don't have the Chromium deb running. 1. Visit https://launchpad.net/bugs/1779569 The rainbow emoji should show in color 2. sudo apt install fonts-symbola 3. Close Chromium. Wait a few moments to make sure it closes then open it and repeat step 1 4. The rainbow emoji shows in black and white Other Info == Firefox and GTK apps like gedit correctly show in color as long as fonts-noto-color-emoji is installed, regardless of whether fonts-symbola is also installed. I also was unable to duplicate this bug with the Firefox Snap [edge channel 63.0b9-1 (134)]. System Info === Ubuntu 18.10 fonts-noto-color-emoji 0~20180810-1 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://forum.snapcraft.io/ license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refresh-date: 8 days ago, at 13:41 EDT channels: stable:69.0.3497.100 (494) 141MB - candidate: 69.0.3497.100 (494) 141MB - beta: 70.0.3538.16 (487) 142MB - edge: 70.0.3538.9 (472) 142MB - installed: 70.0.3538.16 (487) 142MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1794354/+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 1794355] [NEW] package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-34
Public bug reported: Error occured when upgrading packages with software updater. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Sep 25 22:21:38 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Y1jaYH/32-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-05-04 (143 days ago) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1794355 Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Status in libglvnd package in Ubuntu: New Bug description: Error occured when upgrading packages with software updater. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Sep 25 22:21:38 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Y1jaYH/32-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-05-04 (143 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794355/+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 1779569] Re: looks odd in thunderbird, chrome/chromium, okish in firefox
*** This bug is a duplicate of bug 1761844 *** https://bugs.launchpad.net/bugs/1761844 This is fixed in Thunderbird 60 which will be in Ubuntu soon. I'm marking this a duplicate of bug 1761844. ** This bug has been marked a duplicate of bug 1761844 Very large emojis displayed in subject line and in the email list -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1779569 Title: looks odd in thunderbird, chrome/chromium, okish in firefox Status in Mozilla Thunderbird: Unknown Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: New install of 18.04 and thunderbird is showing weird images in odd places for some email. See screen shot for example. In this case it is a weird rainbow, but I have also seen other things like a big stop sign and other strange stuff. Emoji support is inconsistent: - google chrome title is good - firefox title is good - google chrome contents, is bad, black ascii icon - fiefox contents, is ok, not the same icon as in the title - thunderbird content is ok, but too huge To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1779569/+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 1791378] Re: Try install option from EFI boot displays login screen not the live session
closing - works on final beta isos for UM and UB ** Changed in: lightdm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1791378 Title: Try install option from EFI boot displays login screen not the live session Status in lightdm package in Ubuntu: Invalid Bug description: Testing todays (7th Sept 2018) of cosmic. Using virtualbox. Set to boot the ISO using EFI option. Select Try Ubuntu option from ISO Grub. Expected to see the live session. Instead saw the login window. I had to login using ubuntu-budgie / ubuntu-mate to see the live session. Tested both Ubuntu Mate and Ubuntu Budgie Apologies if I raised this against the wrong package! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CasperVersion: 1.395 CurrentDesktop: Budgie:GNOME Date: Fri Sep 7 21:02:15 2018 LightdmConfig: [SeatDefaults] allow-guest=false autologin-guest=false autologin-user=ubuntu-budgie autologin-user-timeout=0 LiveMediaBuild: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180907) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1791378/+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 1771149] Re: Mouse cursor size changes based on what's under it
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1771149 Title: Mouse cursor size changes based on what's under it Status in xorg package in Ubuntu: Confirmed Bug description: I have a Lenovo P51 with Nvidia card. 4k display in the laptop and 2 2560x1440 external monitors. The mouse cursor changes between a normal size and a much much larger size when it is over the background and over some application's title bars. Other times it is normal size. I have wiped my gnome 3 settings and re-set all the cursor size settings to default but nothing helps. I assume it's HiDPI related. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon May 14 09:08:47 2018 DistUpgraded: 2018-05-13 09:36:57,549 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.03.00, 4.13.0-41-generic, x86_64: installed fwts-efi-runtime-dkms, 18.03.00, 4.15.0-20-generic, x86_64: installed nvidia, 390.48, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:224d] Subsystem: Lenovo GM107GLM [Quadro M1200 Mobile] [17aa:224d] InstallationDate: Installed on 2017-12-29 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20HHCTO1WW 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.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi= SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-05-13 (0 days ago) dmi.bios.date: 02/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET46W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HHCTO1WW 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:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HHCTO1WW dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 N/A xserver.bootTime: Mon May 14 08:17:52 2018 xserver.configfile: default xserver.errors: Failed to load module "nouveau" (module does not exist, 0) Failed to load module "nouveau" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771149/+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 1644021] Re: Firefox doesn't include EmojiOne font
This is fixed in Thunderbird 60 which will be released to Ubuntu soon. ** Changed in: thunderbird (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1644021 Title: Firefox doesn't include EmojiOne font Status in firefox package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Committed Status in thunderbird package in Debian: Fix Released Bug description: Firefox has shipped with an emoji font since version 50.0, but Ubuntu doesn't include it in their Firefox packages. Therefore, when opening a page in Firefox containing emoji characters, the black and white glyphs from DejaVu are displayed instead of the glyphs from the EmojiOneMozilla font. According to http://packages.ubuntu.com/xenial- updates/amd64/firefox/filelist, EmojiOneMozilla.ttf is not included in the Firefox package in Ubuntu's repositories. Manual installing this font and verifying that it works: 1) Download Firefox tarball from Firefox website 2) Extract EmojiOneMozilla.ttf from /firefox/fonts/ 3) Copy EmojiOneMozilla.ttf to /usr/lib/firefox/fonts/ 4) Quit Ubuntu session and launch a new one 5) Launch Firefox and go to a page containing emoji characters, such as http://getemoji.com/ or https://eosrei.github.io/emojione-color-font/full-demo.html 6) Now, instead of using glyphs from DejaVu, the majority of emoji on the page are taken from EmojiOneMozilla.ttf ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 50.0+build2-0ubuntu0.12.04.2 ProcVersionSignature: Ubuntu 3.13.0-101.148~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-101-generic. ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gris 2087 F pulseaudio BuildID: 20161114145344 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf880 irq 42' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:10ec0272,15580771,0011 HDA:80862804,80860101,0010' Controls : 52 Simple ctrls : 16 Channel: Unavailable Date: Tue Nov 22 22:31:27 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.14 metric 2 Locales: extensions.sqlite corrupt or missing MarkForUpload: True MostRecentCrashID: bp-bc8d2df2-4862-40a6-987d-4234e2160922 Plugins: Windows Media Player Plug-in 10 (compatible; Totem) - /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla) VLC Multimedia Plugin (compatible Totem 3.0.1) - /usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla) DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so (totem-mozilla) QuickTime Plug-in 7.6.6 - /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) PrefErrors: 'utf8' codec can't decode byte 0xe9 in position 14394: invalid continuation byte Profiles: Profile0 (Default) - LastVersion=50.0/20161114145344 (In use) RelatedPackageVersions: totem-mozilla 3.0.1-0ubuntu21.1 rhythmbox-mozilla 2.96-0ubuntu4.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-bc8d2df2-4862-40a6-987d-4234e2160922 bp-8d5e91df-7bcf-4edb-8642-657f92160922 bp-fc7bab24-1a1a-4a80-9d5f-f86852160922 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: CALPELLACRB.86C..X.00 dmi.board.asset.tag: Tag 12345 dmi.board.name: W760C dmi.board.vendor: CLEVO Co. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO dmi.chassis.version: N/A dmi.modalias:
[Desktop-packages] [Bug 1761844] Re: Very large emojis displayed in subject line and in the email list
This is fixed in Thunderbird 60 which will be released to Ubuntu soon. ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Fix Committed -- 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/1761844 Title: Very large emojis displayed in subject line and in the email list Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Committed Bug description: The list of emails received from Thunderbird shows emojis. This does not happen with all accounts. It appears to be with the last email address added. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:52.6.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: diego 1607 F...m pulseaudio /dev/snd/controlC0: diego 1607 F pulseaudio /dev/snd/controlC1: diego 1607 F pulseaudio BuildID: 20180131200234 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 15:58:17 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-05 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IpRoute: default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100 IwConfig: lono wireless extensions. enp2s0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-78LMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1761844/+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 976638] Re: pkexec does not find any authentication agent
Marcus Naeher has the solution in #17 above For LXDE it is true as well that the PolicyKit Autostart has been unchecked by default in the latest version of Ubuntu/Lubuntu If you check this box and restart, Synaptic package manager will start from the launchpad menu and will ask for Authentication and all is well. Here is his answer quoted below: "I have found the solution by happenstance: (I am using XFCE in German, so maybe the wording I describe here is not 100% accurate) In the XFCE settings menu -> Session management -> Automatically started applications, there is an Item "Policykit Authentication Agent". This was unchecked. Re-check, reboot (probably logout and login is sufficient), and it is back working. But: I am absolutely sure I did not remove the check. On one of the affected computers, I have never been in this dialog before." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in PolicyKit: Unknown Status in policykit-1 package in Ubuntu: Triaged Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+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 1792112] Re: 18.10 Cosmic default wallpapers
Just uploaded (to the queue), but I forgot to reference this bug - sorry! ** Changed in: ubuntu-wallpapers (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1792112 Title: 18.10 Cosmic default wallpapers Status in ubuntu-wallpapers package in Ubuntu: Fix Committed Bug description: Attached will be the Cosmic default wallpapers. One in colour, one in black & white. Both 4096 x 2304. I have both the PNGs and JPEGs. The colour PNG is coming in at nearly 8 meg, so I'm working with the design team to try and get this size down. If it can't be done (PNGcrush was unable to save the day) then we might have to go with the JPEG version which is a svelte 700k. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1792112/+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 1792873] Re: FFE: 18.2.x for cosmic
Duh, I blame the source naming change (previously it was llvm- toolchain-6.0, now it's just -7 instead of -7.0, ugh). Anyway, nevermind me! I think I'm fine with the changes introduced and the testing so far. It's always better to have a more up-to-date stack. I also confirmed with Adam that we're ok with it. So: approving the FFe. ** Changed in: mesa (Ubuntu) Status: New => Triaged -- 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/1792873 Title: FFE: 18.2.x for cosmic Status in mesa package in Ubuntu: Triaged Bug description: Mesa 18.2.0 was recently released after several delays, but at least it doesn't have any known regressions on Intel hw. We tend to get the latest major version in the devel series ~2 weeks after FF, but since a month has passed now I thought it would be best to file an actual FFE request. We'd also build it against LLVM 7, which is about to be released. Together these provide support for AMD Vega20 (kernel support still needed) among other things. New features from mesa upstream reldocs: OpenGL 4.3 on virgl OpenGL 4.4 Compatibility profile on radeonsi OpenGL ES 3.2 on radeonsi and virgl GL_ARB_ES3_2_compatibility on radeonsi GL_ARB_fragment_shader_interlock on i965 GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+) GL_ANDROID_extension_pack_es31a on radeonsi. GL_KHR_texture_compression_astc_ldr on radeonsi GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 (GM200+) GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+) multisampled images on nvc0 (GM107+) (now supported on GF100+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1792873/+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 1786948] Re: Some shell extensions fail to load with gnome-shell 3.29
https://launchpad.net/ubuntu/+source/gnome-shell-extension-multi- monitors/0.00~git20180920.1.0ca053f-1 ** Changed in: gnome-shell-extension-multi-monitors (Ubuntu) Status: Confirmed => Fix Released -- 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/1786948 Title: Some shell extensions fail to load with gnome-shell 3.29 Status in gnome-shell package in Ubuntu: Won't Fix Status in gnome-shell-extension-autohidetopbar package in Ubuntu: Fix Released Status in gnome-shell-extension-caffeine package in Ubuntu: Fix Released Status in gnome-shell-extension-dash-to-panel package in Ubuntu: Fix Released Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-multi-monitors package in Ubuntu: Fix Released Status in gnome-shell-extension-pixelsaver package in Ubuntu: Fix Released Status in gnome-shell-extension-taskbar package in Ubuntu: Confirmed Status in gnome-shell-extension-top-icons-plus package in Ubuntu: Fix Released Status in gnome-shell-extension-workspaces-to-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-autohidetopbar package in Debian: Fix Released Status in gnome-shell-extension-caffeine package in Debian: Fix Released Status in gnome-shell-extension-dash-to-panel package in Debian: Fix Released Status in gnome-shell-extension-dashtodock package in Debian: Fix Released Status in gnome-shell-extension-multi-monitors package in Debian: Confirmed Status in gnome-shell-extension-pixelsaver package in Debian: Fix Released Status in gnome-shell-extension-taskbar package in Debian: Confirmed Status in gnome-shell-extension-top-icons-plus package in Debian: Fix Released Status in gnome-shell-extension-workspaces-to-dock package in Debian: Fix Released Bug description: The title says it all at this point. Happy to gather additional logs. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) Package: gnome-shell 3.29.90-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Tags: wayland-session cosmic Uname: Linux 4.17.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786948/+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 1794317] [NEW] Scale of screensaver login box is far too large on 3000x2000 display when GUI scale is set to 200%
Public bug reported: When locking the desktop, the gnome-screensaver login/password prompt box is not properly scaled. My display is 13.9" with a resolution of 3000x2000. This happens when the scale of the GUI in Budgie settings is set to 200%, but the box appears to scale relatively well when the scale of the GUI is set to 100% (while considering everything is much smaller at that scale). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Sep 25 11:25:29 2018 InstallationDate: Installed on 2018-09-18 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Image of login box" https://bugs.launchpad.net/bugs/1794317/+attachment/5192816/+files/nW9XY.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1794317 Title: Scale of screensaver login box is far too large on 3000x2000 display when GUI scale is set to 200% Status in gnome-screensaver package in Ubuntu: New Bug description: When locking the desktop, the gnome-screensaver login/password prompt box is not properly scaled. My display is 13.9" with a resolution of 3000x2000. This happens when the scale of the GUI in Budgie settings is set to 200%, but the box appears to scale relatively well when the scale of the GUI is set to 100% (while considering everything is much smaller at that scale). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Sep 25 11:25:29 2018 InstallationDate: Installed on 2018-09-18 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1794317/+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 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
marco's going to look at this for what it's worth, I tried with today's daily and didn't manage to reproduce (virt-manager/qemu, cosmic host, qxl) ** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gdm3 (Ubuntu Cosmic) Importance: Undecided Assignee: Marco Trevisan (Treviño) (3v1n0) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: New Status in gdm3 source package in Cosmic: New Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1793742] Re: xdvi stops showing emedded figures after updating ghostscript
Hi! Any chance you could send me the problematic dvi file? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1793742 Title: xdvi stops showing emedded figures after updating ghostscript Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Status in ghostscript source package in Cosmic: Fix Released Bug description: I like to report a problem with using xdvi after upgrading ghostscript (and libgs9) in Trusty Tahr from version 9.10~dfsg-0ubuntu10.12 to version 9.10~dfsg-0ubuntu10.13. The error message after invoking xdvi looks as below. $ xdvi scaling.dvi gs: Error: /undefined in flushpage gs: Operand stack: gs: gs: Execution stack: gs:%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- gs:2 %stopped_push --nostringval-- --nostringval-- --nostringval-- fals gs: e 1 %stopped_push 1916 1 3 %oparray_pop 1915 1 3 %oparray_pop gs:1899 1 3 %oparray_pop 1787 1 3 %oparray_pop --nostringval-- gs: %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- gs: 2 %stopped_push --nostringval-- --nostringval-- %loop_continue --nost gs: ringval-- gs: Dictionary stack: gs:--dict:957/1684(ro)(G)-- --dict:0/20(G)-- --dict:81/200(L)-- gs: Current allocation mode is local gs: Last OS error: No such file or directory gs: GPL Ghostscript 9.10: Unrecoverable error, exit code 1 xdvi.bin: Warning: Read_from_gs returned 0 bytes For the (unlikely) possibility that this error could be due to the update of some other package I also include the full list of the packages that were installed at the same time. Setting up libglib2.0-data (2.40.2-0ubuntu1.1) ... Setting up libglib2.0-0:amd64 (2.40.2-0ubuntu1.1) ... Setting up libglib2.0-bin (2.40.2-0ubuntu1.1) ... Setting up libglib2.0-dev (2.40.2-0ubuntu1.1) ... Setting up liblcms2-2:amd64 (2.5-0ubuntu4.2) ... Setting up libopencv-core2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-flann2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-imgproc2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-features2d2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-calib3d2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-highgui2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-ml2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-video2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-legacy2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-objdetect2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libopencv-contrib2.4:amd64 (2.4.8+dfsg1-2ubuntu1.2) ... Setting up libisc95 (1:9.9.5.dfsg-3ubuntu0.18) ... Setting up libdns100 (1:9.9.5.dfsg-3ubuntu0.18) ... Setting up libisccc90 (1:9.9.5.dfsg-3ubuntu0.18) ... Setting up libisccfg90 (1:9.9.5.dfsg-3ubuntu0.18) ... Setting up libbind9-90 (1:9.9.5.dfsg-3ubuntu0.18) ... Setting up liblwres90 (1:9.9.5.dfsg-3ubuntu0.18) ... Setting up bind9-host (1:9.9.5.dfsg-3ubuntu0.18) ... Setting up dnsutils (1:9.9.5.dfsg-3ubuntu0.18) ... Setting up libgs9-common (9.10~dfsg-0ubuntu10.13) ... Setting up libgs9 (9.10~dfsg-0ubuntu10.13) ... Setting up ghostscript (9.10~dfsg-0ubuntu10.13) ... Setting up ghostscript-x (9.10~dfsg-0ubuntu10.13) ... Description:Ubuntu 14.04.5 LTS Release:14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1793742/+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 1787730] Re: gnome-control-center crashed with SIGABRT
** Description changed: - Hello, - - I do not know why this happened... - - Regards, - -- - Cristian Aravena Romero (caravena) + 1. Open the command line + 2. $ gnome-control-center wifi + 3. close gnoe-control-center + 4. $ gnome-control-center power -- https://gitlab.gnome.org/GNOME/gnome-control-center/issues/158 ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.29.90-1~ubuntu1 Uname: Linux 4.18.1-041801-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 17 19:54:55 2018 ExecutablePath: /usr/bin/gnome-control-center ExecutableTimestamp: 1533292497 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: gnome-control-center bluetooth ProcCwd: /home/caravena Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_create_dbus_proxy_finish () () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo ** Summary changed: - gnome-control-center crashed with SIGABRT + gnome-control-center crashed with SIGABRT in rfkill_proxy_acquired_cb -- 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/1787730 Title: gnome-control-center crashed with SIGABRT in rfkill_proxy_acquired_cb Status in gnome-control-center package in Ubuntu: Confirmed Bug description: 1. Open the command line 2. $ gnome-control-center wifi 3. close gnoe-control-center 4. $ gnome-control-center power -- https://gitlab.gnome.org/GNOME/gnome-control-center/issues/158 ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.29.90-1~ubuntu1 Uname: Linux 4.18.1-041801-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 17 19:54:55 2018 ExecutablePath: /usr/bin/gnome-control-center ExecutableTimestamp: 1533292497 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: gnome-control-center bluetooth ProcCwd: /home/caravena Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_create_dbus_proxy_finish () () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1787730/+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 1787730] Re: gnome-control-center crashed with SIGABRT
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/1787730 Title: gnome-control-center crashed with SIGABRT in rfkill_proxy_acquired_cb Status in gnome-control-center package in Ubuntu: Confirmed Bug description: 1. Open the command line 2. $ gnome-control-center wifi 3. close gnoe-control-center 4. $ gnome-control-center power -- https://gitlab.gnome.org/GNOME/gnome-control-center/issues/158 ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.29.90-1~ubuntu1 Uname: Linux 4.18.1-041801-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 17 19:54:55 2018 ExecutablePath: /usr/bin/gnome-control-center ExecutableTimestamp: 1533292497 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: gnome-control-center bluetooth ProcCwd: /home/caravena Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_create_dbus_proxy_finish () () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1787730/+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 1794276] Re: /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:cc_object_storage_create_dbus_proxy_finish:rfkill_proxy_acquired_cb:g_task_return_now
*** This bug is a duplicate of bug 1787730 *** https://bugs.launchpad.net/bugs/1787730 ** This bug has been marked a duplicate of bug 1787730 gnome-control-center crashed with SIGABRT -- 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/1794276 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:cc_object_storage_create_dbus_proxy_finish:rfkill_proxy_acquired_cb:g_task_return_now Status in gnome-control-center package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1d0831f87572e3c49ba93ce2bef3f96b4feae743 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/. [How to reproduce] 1. Open the command line 2. $ gnome-control-center wifi 3. close gnoe-control-center 4. $ gnome-control-center power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1794276/+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 1794191] Re: Snap Store fails to return to main page after package installation
That's the upstream behavior of gnome-software. You have the click on back button up top. If we want to consider changing that we'll need some design work and review. -- 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/1794191 Title: Snap Store fails to return to main page after package installation Status in gnome-software package in Ubuntu: Confirmed Bug description: Version 3.29.1+git218.7e7e8cd After installing an application the snap store stayed on the application installation page and wont return to the main page where one can browse or install other applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1794191/+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 1675547] Re: bg_BG uses wrong encoding
solved upstream in https://bugs.documentfoundation.org/show_bug.cgi?id=117392 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-dictionaries in Ubuntu. https://bugs.launchpad.net/bugs/1675547 Title: bg_BG uses wrong encoding Status in libreoffice-dictionaries package in Ubuntu: Triaged Bug description: for the Bulgarian Dictionary, SET microsoft-cp1251 needs to be changed to: SET cp1251 Unless you want to use UTF-8? https://github.com/hunspell/hunspell/issues/458#issuecomment-288843786 any other (upstream) packages where a bug needs to be filed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1675547/+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 1432137] Re: Xorg crashed due to assertion failure "!global_keys[type].created" in dixRegisterPrivateKey
** Also affects: xorg-server (Ubuntu Cosmic) Importance: Medium Status: Confirmed ** Tags removed: rls-cc-incoming ** Tags added: rls-cc-tracking ** Changed in: xorg-server (Ubuntu Cosmic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1432137 Title: Xorg crashed due to assertion failure "!global_keys[type].created" in dixRegisterPrivateKey Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Cosmic: Confirmed Bug description: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Boot leads to blank white screen. Mouse click brings in log in screen. At log in this problem is detected. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: xserver-xorg-core 2:1.17.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AssertionMessage: X: ../../dix/privates.c:385: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CrashCounter: 1 Date: Sat Mar 14 05:18:42 2015 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2015-02-13 (28 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Alpha amd64 (20150213) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: __assert_fail_base (fmt=0x7f5dcf2e0488 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f5dd1655b5d "!global_keys[type].created", file=file@entry=0x7f5dd1655b1e "../../dix/privates.c", line=line@entry=385, function=function@entry=0x7f5dd1655f60 "dixRegisterPrivateKey") at assert.c:92 __GI___assert_fail (assertion=0x7f5dd1655b5d "!global_keys[type].created", file=0x7f5dd1655b1e "../../dix/privates.c", line=385, function=0x7f5dd1655f60 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () glamor_init () from /usr/lib/xorg/modules/libglamoregl.so ?? () from /usr/lib/xorg/modules/drivers/modesetting_drv.so Title: Xorg assert failure: X: ../../dix/privates.c:385: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1432137/+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 1432137] Re: Xorg crashed due to assertion failure "!global_keys[type].created" in dixRegisterPrivateKey
** Tags added: rls-cc-incoming -- 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/1432137 Title: Xorg crashed due to assertion failure "!global_keys[type].created" in dixRegisterPrivateKey Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Cosmic: Confirmed Bug description: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Boot leads to blank white screen. Mouse click brings in log in screen. At log in this problem is detected. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: xserver-xorg-core 2:1.17.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AssertionMessage: X: ../../dix/privates.c:385: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CrashCounter: 1 Date: Sat Mar 14 05:18:42 2015 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2015-02-13 (28 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Alpha amd64 (20150213) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: __assert_fail_base (fmt=0x7f5dcf2e0488 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f5dd1655b5d "!global_keys[type].created", file=file@entry=0x7f5dd1655b1e "../../dix/privates.c", line=line@entry=385, function=function@entry=0x7f5dd1655f60 "dixRegisterPrivateKey") at assert.c:92 __GI___assert_fail (assertion=0x7f5dd1655b5d "!global_keys[type].created", file=0x7f5dd1655b1e "../../dix/privates.c", line=385, function=0x7f5dd1655f60 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () glamor_init () from /usr/lib/xorg/modules/libglamoregl.so ?? () from /usr/lib/xorg/modules/drivers/modesetting_drv.so Title: Xorg assert failure: X: ../../dix/privates.c:385: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1432137/+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 1786344] Re: Default IBus input method ignored in live session
not marking as a release blocker, but andrea is still working on this as assigned ** Tags removed: rls-cc-incoming ** Tags added: rls-cc-notfixing -- 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/1786344 Title: Default IBus input method ignored in live session Status in gnome-settings-daemon package in Ubuntu: In Progress Bug description: Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't input Chinese character. From Settings -> Regions and Languages, selected Intelligent Pinyin, also could not input Chinese. --- 18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and Languages，选择 智能拼音，也无法输入中文。 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1786344/+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 1792648] Re: Can't preview document in evince - Ubuntu 18.10 Failed to execute child process (Permission Denied)
** Also affects: evince (Ubuntu Cosmic) Importance: High Assignee: Olivier Tilloy (osomon) Status: In Progress ** Tags removed: rls-cc-incoming ** Tags added: rls-cc-tracking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1792648 Title: Can't preview document in evince - Ubuntu 18.10 Failed to execute child process (Permission Denied) Status in evince package in Ubuntu: In Progress Status in evince source package in Cosmic: In Progress Bug description: Ubuntu 18.10 Evince of a PDF Clicking PREVIEW I get busy awhile then Failed to print document Failed to execute child process "/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop" (Permissions denied) -- I looked at this only because of https://community.ubuntu.com/t /failed-to-preview-print/7956 where a user "flaviosm" reported the same thing. In `dmesg` I noted the following [43361.474096] audit: type=1400 audit(1536710182.492:65): apparmor=“DENIED” operation=“exec” profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop" pid=11840 comm=“evince” requested_mask=“x” denied_mask=“x” fsuid=1000 ouid=0 I rebooted and tried again, (same result) [ 400.208807] audit: type=1400 audit(1536711261.421:51): apparmor=“DENIED” operation=“exec” profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop" pid=5302 comm=“evince” requested_mask=“x” denied_mask=“x” fsuid=1000 ouid=0 Note: I don't have a printer setup on my box (I don't print from it), so this could be the cause! I don't know if this applies to "flaviosm" too.. I can connect & test after printer is setup if deemed helpful (headcold - so no motivation currently) Filed online as unsuccessful via via `ubuntu-bug` on actual box.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1792648/+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 1743216] Re: perl crashed with SIGABRT in _dbus_abort()
** Changed in: xdg-utils (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) => Iain Lane (laney) ** Also affects: perl (Ubuntu Cosmic) Importance: High Status: Confirmed ** Also affects: xdg-utils (Ubuntu Cosmic) Importance: High Assignee: Iain Lane (laney) Status: Confirmed ** Tags removed: rls-cc-incoming ** Tags added: rls-cc-tracking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1743216 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: Confirmed Status in xdg-utils package in Ubuntu: Confirmed Status in perl source package in Cosmic: Confirmed Status in xdg-utils source package in Cosmic: Confirmed Bug description: Errors Bucket - https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 crashed after launching the software updater ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-4 ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12 Uname: Linux 4.14.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 13:30:52 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2017-12-28 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201) Signal: 6SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1743216/+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 1790146] Re: Update Welcome page for Ubuntu 18.10
** Also affects: gnome-initial-setup (Ubuntu Cosmic) Importance: High Assignee: Andrea Azzarone (azzar1) Status: In Progress ** Tags removed: rls-cc-incoming ** Tags added: rls-cc-tracking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1790146 Title: Update Welcome page for Ubuntu 18.10 Status in gnome-initial-setup package in Ubuntu: In Progress Status in gnome-initial-setup source package in Cosmic: In Progress Bug description: gnome-initial-setup | 3.29.92-1ubuntu1, Ubuntu Cosmic current (20180822) 1. Install Ubuntu and start it for the first time. What happens: A screen appears saying “Ubuntu 18.04 works differently from older versions.” What should happen: This step should no longer appear, because: - you aren’t running 18.04; - if you’ve never used Ubuntu before, what’s different about 18.04+ isn’t relevant anyway; - if you have used Ubuntu before, you’ve probably used 18.04 already, since that’s required to use any of our provided methods for upgrading to 18.10; - if you did somehow upgrade to Cosmic/18.10 while skipping over 18.04 entirely, you almost certainly know enough about Ubuntu that you don’t need this guide in the first place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1790146/+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 1794213] Re: Crash on Upgrade to 18.10 from 18.04 Network Not Available
** Project changed: launchpad => appstream (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade to 18.10 from 18.04 Network Not Available Status in appstream package in Ubuntu: New Bug description: E:Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi', E:Sub-process returned an error code The above error is in the small box. The information below is in the terminal window that I thought might give clues on what happened on disto upgrade to 18.10 from command line. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXT_EXEC '/usr/bin/firefox' from launcher. kdeinit5: preparing to launch '/usr/bin/firefox' kdeinit5: PID 5799 terminated. (appstreamcli:6926): GLib-CRITICAL **: 21:59:50.626: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:6926): GLib-CRITICAL **: 21:59:50.626: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:6926): GLib-ERROR **: 21:59:50.626: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) QXcbConnection: XCB error: 3 (BadWindow), sequence: 792, resource id: 39845978, major code: 40 (TranslateCoords), minor code: 0 (appstreamcli:8091): GLib-CRITICAL **: 22:00:11.961: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:8091): GLib-CRITICAL **: 22:00:11.961: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:8091): GLib-ERROR **: 22:00:11.961: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) (appstreamcli:8899): GLib-CRITICAL **: 22:00:17.376: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:8899): GLib-CRITICAL **: 22:00:17.376: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:8899): GLib-ERROR **: 22:00:17.376: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) (appstreamcli:9701): GLib-CRITICAL **: 22:00:21.530: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:9701): GLib-CRITICAL **: 22:00:21.530: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:9701): GLib-ERROR **: 22:00:21.530: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) kdeinit5: PID 6868 terminated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+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 1794299] Re: libreoffice in Bionic freezes when running libreoffice-librelogo script
This was the script mentioned in my report: ;KOCH C ;Draws a sequence of Koch “C” curves. The size of the curve is determined by n≤256; its position in the sequence by p≥0. ;The embedded, tabbed routine, kc, below is a “daemon”, which actually draws the curve. The daemon draws the p=0 curve directly, and the (p+1)th curve by replacing the line segments of the p=1 curve with scaled-down pth curves ( p≥0). ;The main kcurve-routine, “wrapped around” the daemon, merely positions the drawing-point so that the curve appears in the centre of the page. It also colours the sub-curves of the curve to show how the Koch “C” curve is constructed. ;Run the script in LibreOffice by accessing the LOGO-toolbar and hitting the green triangle button ;lines preceded by a “;” are ignored by logo CLEARSCREEN HOME HIDETURTLE To kcurve :n :p GLOBAL c c=SQRT 2 TO kc :n :p IF :p=0 [ FD :n ] [ LT 45 kc :n/c :p-1 RT 90 kc :n/c :p-1 LT 45 ] END PU BK :n/2 LT 90 BK (3*:n)/8 RT 90 PS 4 PD IF :p=0 [ PC [5] FD :n PC [0] ] [ LT 45 PC [5] kc :n/c :p-1 PC [0] RT 90 PC [8] kc :n/c :p-1 PC [0] LEFT 45 ] PU RT 90 BK (3*:n)/8 LT 90 BK :n/2 PD PS 1 END ;”Groups” the components of the curve drawn by the command ‘kcurve (256, 10)’ “ PICTURE [ kcurve (256, 10) ] ;Exports an .svg-image of the curve (on a white background) to the folder containing the script ;PICTURE “LibreLogoKochCurve.svg” [ PU POS [0, 0] PD POS [PAGESIZE[0], 0] POS [PAGESIZE[0], (SQRT 2)*PAGESIZE[0]] POS [0, (SQRT 2)*PAGESIZE[0]] POS [0,0] PU HOME PD FILLCOLOR [3] FILL kcurve (256, 10) ] ;this .svg-image can be opened in LibreOffice and then “exported” as .png or .jpg -- 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/1794299 Title: libreoffice in Bionic freezes when running libreoffice-librelogo script Status in libreoffice package in Ubuntu: New Bug description: i) azed@azed-H270N:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ii) azed@azed-H270N:~$ apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:6.0.6-0ubuntu0.18.04.1 Version table: 1:6.0.6-0ubuntu0.18.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 1:6.0.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages azed@azed-H270N:~$ iii) - iv) Try the script attached. Works in 16.04 and OS "Tumbleweed", but in Bionic, LO freezes-up. I have to force a quit to get it back. Other logo scripts behave the same. Shame. Being able to run LOGO in LO is really cool. I got an error message when I first tried to report this bug. Take 2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Sep 25 13:56:43 2018 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2018-04-28 (149 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1794299/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
I went through this the other day with a personal profile. We probably
can do something along the lines of:
/{,snap/core/[0-9]*/}usr/bin/snap mrCx -> snap_browser,
profile snap_browser {
#include
/etc/passwd r,
/etc/group r,
/etc/nsswitch.conf r,
/dev/tty rw,
# noisy
deny network inet stream,
deny network inet6 stream,
deny owner /run/user/[0-9]*/gdm/Xauthority r, # not needed on Ubuntu
/{,snap/core/[0-9]*/}usr/bin/snap mrix, # re-exec
/etc/fstab r,
@{PROC}/sys/net/core/somaxconn r,
@{PROC}/sys/kernel/seccomp/actions_avail r,
owner @{PROC}/@{pid}/mountinfo r,
owner @{HOME}/.snap/auth.json r, # if exists, required
/run/snapd.socket rw,
/snap/core/[0-9]*/usr/lib/snapd/info r,
/snap/core/[0-9]*/usr/lib/snapd/snapd r,
/var/lib/snapd/system-key r,
/{,snap/core/*/}usr/lib/snapd/snap-confine Pix,
/sys/kernel/security/apparmor/features/ r,
# allow launching official browser snaps. This could be abstracted into an
#include or tunable
/snap/chromium/*/meta/snap.yaml r,
/snap/firefox/*/meta/snap.yaml r,
# ...
}
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hyperlink in a PDF fails to open it if the default browser
is a snap
Status in evince package in Ubuntu:
New
Bug description:
This is related to bug #1792648. After fixing that one (see discussion
at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
clicking a hyperlink in a PDF opens it correctly if the default
browser is a well-known application (such as /usr/bin/firefox), but it
fails to do so if the default browser is a snap (e.g. the chromium
snap).
This is not a recent regression, it's not working on bionic either.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: evince 3.30.0-2
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 24 12:28:06 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-02 (813 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: evince
UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+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 1794299] [NEW] libreoffice in Bionic freezes when running libreoffice-librelogo script
Public bug reported: i) azed@azed-H270N:~$ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 ii) azed@azed-H270N:~$ apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:6.0.6-0ubuntu0.18.04.1 Version table: 1:6.0.6-0ubuntu0.18.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 1:6.0.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages azed@azed-H270N:~$ iii) - iv) Try the script attached. Works in 16.04 and OS "Tumbleweed", but in Bionic, LO freezes-up. I have to force a quit to get it back. Other logo scripts behave the same. Shame. Being able to run LOGO in LO is really cool. I got an error message when I first tried to report this bug. Take 2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Sep 25 13:56:43 2018 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2018-04-28 (149 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze libreoffice-librelogo -- 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/1794299 Title: libreoffice in Bionic freezes when running libreoffice-librelogo script Status in libreoffice package in Ubuntu: New Bug description: i) azed@azed-H270N:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ii) azed@azed-H270N:~$ apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:6.0.6-0ubuntu0.18.04.1 Version table: 1:6.0.6-0ubuntu0.18.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 1:6.0.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages azed@azed-H270N:~$ iii) - iv) Try the script attached. Works in 16.04 and OS "Tumbleweed", but in Bionic, LO freezes-up. I have to force a quit to get it back. Other logo scripts behave the same. Shame. Being able to run LOGO in LO is really cool. I got an error message when I first tried to report this bug. Take 2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Sep 25 13:56:43 2018 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2018-04-28 (149 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1794299/+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 1794213] [NEW] Crash on Upgrade to 18.10 from 18.04 Network Not Available
You have been subscribed to a public bug: E:Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi', E:Sub-process returned an error code The above error is in the small box. The information below is in the terminal window that I thought might give clues on what happened on disto upgrade to 18.10 from command line. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXT_EXEC '/usr/bin/firefox' from launcher. kdeinit5: preparing to launch '/usr/bin/firefox' kdeinit5: PID 5799 terminated. (appstreamcli:6926): GLib-CRITICAL **: 21:59:50.626: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:6926): GLib-CRITICAL **: 21:59:50.626: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:6926): GLib-ERROR **: 21:59:50.626: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) QXcbConnection: XCB error: 3 (BadWindow), sequence: 792, resource id: 39845978, major code: 40 (TranslateCoords), minor code: 0 (appstreamcli:8091): GLib-CRITICAL **: 22:00:11.961: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:8091): GLib-CRITICAL **: 22:00:11.961: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:8091): GLib-ERROR **: 22:00:11.961: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) (appstreamcli:8899): GLib-CRITICAL **: 22:00:17.376: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:8899): GLib-CRITICAL **: 22:00:17.376: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:8899): GLib-ERROR **: 22:00:17.376: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) (appstreamcli:9701): GLib-CRITICAL **: 22:00:21.530: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:9701): GLib-CRITICAL **: 22:00:21.530: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:9701): GLib-ERROR **: 22:00:21.530: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) kdeinit5: PID 6868 terminated. ** Affects: appstream (Ubuntu) Importance: Undecided Status: New -- Crash on Upgrade to 18.10 from 18.04 Network Not Available https://bugs.launchpad.net/bugs/1794213 You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream 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 1794191] Re: Snap Store fails to return to main page after package installation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1794191 Title: Snap Store fails to return to main page after package installation Status in gnome-software package in Ubuntu: Confirmed Bug description: Version 3.29.1+git218.7e7e8cd After installing an application the snap store stayed on the application installation page and wont return to the main page where one can browse or install other applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1794191/+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 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1
Proposed package 340.107-0ubuntu0.18.04.1 from #7 fixed the problem for me after manual download and install with dpkg. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Status in libglvnd package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in libglvnd source package in Bionic: Confirmed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The new libgles1 conflicts with nvidia-340 which ships it's own copy of libGLESv1_CM.so [Test case] Enable proposed, install libgles1 and nvidia-340, they should install fine. [Regression potential] none, just fixes a file conflict -- Looks like I had a similar problem on 18.04.1 than https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just with nvidia-340 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa . Apt output: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libgles1 The following packages will be upgraded: libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 libopengl0 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 268 kB of archives. After this operation, 66,6 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 amd64 1.0.0-2ubuntu2.2 [17,4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 amd64 1.0.0-2ubuntu2.2 [84,8 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 amd64 1.0.0-2ubuntu2.2 [28,1 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 amd64 1.0.0-2ubuntu2.2 [31,3 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 amd64 1.0.0-2ubuntu2.2 [31,9 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.2 [46,6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 amd64 1.0.0-2ubuntu2.2 [11,2 kB] Fetched 268 kB in 0s (1 575 kB/s) (Reading database ... 141610 files and directories currently installed.) Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Selecting previously unselected package libgles1:amd64. Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Errors were encountered while processing: /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb
[Desktop-packages] [Bug 1794284] [NEW] PCI/internal sound card not detected
Public bug reported: my sound was working in xenial. with internal intel sound. without any change it stopped working, no soundcard found. update to bionic didn't change anything :( ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 14:16:55 2018 InstallationDate: Installed on 2016-03-10 (929 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z270-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. 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 bionic -- 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/1794284 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound was working in xenial. with internal intel sound. without any change it stopped working, no soundcard found. update to bionic didn't change anything :( ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 14:16:55 2018 InstallationDate: Installed on 2016-03-10 (929 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z270-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1794284/+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 263660] Re:
*** This bug is a duplicate of bug 106060 *** https://bugs.launchpad.net/bugs/106060 http://visitor.rollingblockparty.com Greg Clark -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/263660 Title: display on screen'CONSTRUCTING MOLECULES'every thing shuts down all the time,then restart.thanhs gugs.cheers. Status in Launchpad itself: Invalid Status in gnome-screensaver package in Ubuntu: Invalid Bug description: on screen saver for a little while then freeze with display "constructing molecules" comes up; then physical shut down restart.thanks guys To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/263660/+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 1794283] [NEW] nautilus throws error during copying file
Public bug reported: When copying a file from a remote samba resource I get an error "Error when copying ", more information: "Error during file splitting: input/output error". The problem occurs only in the Nautilus file manager, copying by the terminal or by another file manager works properly without error. I use Ubuntu 18, packages associated with nautilus: libnautilus-extension1a:amd64 1:3.26.3-0ubuntu4 nautilus 1:3.26.3-0ubuntu4 amd64 nautilus-data 1:3.26.3-0ubuntu4 all nautilus-extension-gnome-terminal 3.28.2-1ubuntu1~18.04.1 amd64 nautilus-sendto 3.8.6-2 amd64 nautilus-share 0.7.3-2ubuntu3 amd64 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 13:22:22 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'203' b'org.gnome.nautilus.window-state' b'geometry' b"'864x501+2419+288'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-09-03 (21 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) 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/1794283 Title: nautilus throws error during copying file Status in nautilus package in Ubuntu: New Bug description: When copying a file from a remote samba resource I get an error "Error when copying ", more information: "Error during file splitting: input/output error". The problem occurs only in the Nautilus file manager, copying by the terminal or by another file manager works properly without error. I use Ubuntu 18, packages associated with nautilus: libnautilus-extension1a:amd64 1:3.26.3-0ubuntu4 nautilus 1:3.26.3-0ubuntu4 amd64 nautilus-data 1:3.26.3-0ubuntu4 all nautilus-extension-gnome-terminal 3.28.2-1ubuntu1~18.04.1 amd64 nautilus-sendto 3.8.6-2 amd64 nautilus-share 0.7.3-2ubuntu3 amd64 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 13:22:22 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'203' b'org.gnome.nautilus.window-state' b'geometry' b"'864x501+2419+288'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-09-03 (21 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794283/+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 1794280] [NEW] gdm doesn't start on a fresh installation of Cosmic Desktop
Public bug reported: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: New Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1794276] Re: /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:cc_object_storage_create_dbus_proxy_finish:rfkill_proxy_acquired_cb:g_task_return_now
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1d0831f87572e3c49ba93ce2bef3f96b4feae743 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/. + + + [How to reproduce] + 1. Open the command line + 2. $ gnome-control-center wifi + 3. close gnoe-control-center + 4. $ gnome-control-center power -- 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/1794276 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:cc_object_storage_create_dbus_proxy_finish:rfkill_proxy_acquired_cb:g_task_return_now Status in gnome-control-center package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1d0831f87572e3c49ba93ce2bef3f96b4feae743 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/. [How to reproduce] 1. Open the command line 2. $ gnome-control-center wifi 3. close gnoe-control-center 4. $ gnome-control-center power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1794276/+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 1794276] [NEW] /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:cc_object_storage_create_dbus_proxy_finish:rfkill_proxy_acquired_cb:g_task_return_no
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1d0831f87572e3c49ba93ce2bef3f96b4feae743 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/. [How to reproduce] 1. Open the command line 2. $ gnome-control-center wifi 3. close gnoe-control-center 4. $ gnome-control-center power ** Affects: gnome-control-center (Ubuntu) Importance: High Assignee: Andrea Azzarone (azzar1) Status: In Progress ** Tags: cosmic -- 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/1794276 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:cc_object_storage_create_dbus_proxy_finish:rfkill_proxy_acquired_cb:g_task_return_now Status in gnome-control-center package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1d0831f87572e3c49ba93ce2bef3f96b4feae743 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/. [How to reproduce] 1. Open the command line 2. $ gnome-control-center wifi 3. close gnoe-control-center 4. $ gnome-control-center power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1794276/+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 1794191] Re: Snap Store fails to return to main page after package installation
** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** No longer affects: snapstore -- 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/1794191 Title: Snap Store fails to return to main page after package installation Status in gnome-software package in Ubuntu: New Bug description: Version 3.29.1+git218.7e7e8cd After installing an application the snap store stayed on the application installation page and wont return to the main page where one can browse or install other applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1794191/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I m still unable to connect to WPA2 Enterprise Network after installing all the apt updates -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1793801] Re: Super + left/right doesn't expand window to half screen
Apparently it resolved by itself after brand new ubuntu installation (made for other reasons). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1793801 Title: Super + left/right doesn't expand window to half screen Status in evince package in Ubuntu: New Bug description: When I open a PDF only super+up/down (maximize/original size) works. Strangely when I launch evince only thus showing recent files half screen expantion works. Description: Ubuntu 18.04.1 LTS Release: 18.04 evince: Installed: 3.28.2-1 Candidate: 3.28.2-1 Version table: *** 3.28.2-1 500 500 http://it.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/evince/+bug/1793801/+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 1777520] Re: package gnome-software-common 3.28.1-0ubuntu4.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1777520 Title: package gnome-software-common 3.28.1-0ubuntu4.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gnome-software package in Ubuntu: Confirmed Bug description: Dont know. tried to do update and got this automatically ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-software-common 3.28.1-0ubuntu4.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jun 18 14:40:41 2018 Dependencies: DuplicateSignature: package:gnome-software-common:3.28.1-0ubuntu4.18.04.1 Unpacking wireless-regdb (2018.05.09-0ubuntu1~18.04.1) over (2016.06.10-0ubuntu1) ... dpkg: error processing package gnome-software-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-12-14 (1282 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-software Title: package gnome-software-common 3.28.1-0ubuntu4.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to bionic on 2018-05-04 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1777520/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I am glad that I could help somehow. I had the issue with a wifi provided by a Ubiquity AaccessPoint. I am pretty sure that there was no update on that in the meantime as it was a new install and configuration (however I am not the admin on that net and I have no details). In the meantime I got an update on openvpn, bind9, dnsutils, liblwres160, libdns-export1100, libdns1100 - which maybe could have an impact (just wild guessing from the library names). No kernel update in the meantime, I am on 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48. I am pretty sure that in my case it was only because although I tested with a few different settings on my first attempts, the solution was just using the correct settings (fitting the Access Point configuration). -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
@mwildam : Due to your comment on that it might be resolved, I also checked the bug again. For me this issue is now also resolved. I m not sure why this is resolved, but I can think of two reasons: - The wifi I previously attempt to connect to got updated/upgraded and now supports connections from Ubuntu (and this should then also be the case for @mwildam), or - A fix was pushed via the regular Ubuntu updates I install. Either way, I no longer have this previously reported problem. -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 I have this issue too since at least 10 minutes ago. I was fiddling with tmux/byobu at the time - idk if this is relevant. $ lsb_release -d Description:Ubuntu 18.04.1 LTS Sorry for the "me too" comment -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in console-setup package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
In my case I was able to solve the problem by changing some settings: Security: WPA & WPA2 Enterprise * Authentication: Protected EAP (PEAP) * No certificate is required: Checked PEAP version: Automatic * Inner authentication: MSCHAPv2 Now I am not sure, if I am simply not affected by the bug and solely had wrong settings - or if probably this helps also others to solve their wifi issue. -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1794245] [NEW] Attached USB devices are ignored.
Public bug reported: After few suspends or detach-/attachments of USB devices libinput starts ignoring new devices due to too many input devices. Unnecessary to say there is only one device attached. journalctr reports this behavior: /usr/lib/gdm3/gdm-x-session[1407]: (**) PixArt USB Optical Mouse: always reports core events# /usr/lib/gdm3/gdm-x-session[1407]: (**) Option "Device" "/dev/input/event295" /usr/lib/gdm3/gdm-x-session[1407]: (**) Option "_source" "server/udev" /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: is tagged by udev as: Mouse /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: device set to 1000 DPI /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: device is a pointer /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: device removed /usr/lib/gdm3/gdm-x-session[1407]: (EE) Too many input devices. Ignoring PixArt USB Optical Mouse /usr/lib/gdm3/gdm-x-session[1407]: (II) UnloadModule: "libinput" The bug seems related to a known libinput bug 1579567. https://bugzilla.redhat.com/show_bug.cgi?id=1579567 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-libinput 0.27.1-1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 09:11:31 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu MachineType: ASUSTeK COMPUTER INC. UX51VZA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=05aab5a7-bef4-4178-acea-7bebfacf8766 ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX51VZA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX51VZA 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.:bvrUX51VZA.204:bd12/03/2012:svnASUSTeKCOMPUTERINC.:pnUX51VZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX51VZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX51VZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1794245 Title: Attached USB devices are ignored. Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: After few suspends or detach-/attachments of USB devices libinput starts ignoring new devices due to too many input devices. Unnecessary to say there is only one device attached. journalctr reports this behavior: /usr/lib/gdm3/gdm-x-session[1407]: (**) PixArt USB Optical Mouse: always reports core events# /usr/lib/gdm3/gdm-x-session[1407]: (**) Option "Device" "/dev/input/event295" /usr/lib/gdm3/gdm-x-session[1407]: (**) Option "_source" "server/udev" /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: is tagged by udev as: Mouse /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: device set to 1000 DPI /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: device is a pointer /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: device removed /usr/lib/gdm3/gdm-x-session[1407]: (EE) Too many input devices. Ignoring PixArt USB Optical Mouse /usr/lib/gdm3/gdm-x-session[1407]: (II) UnloadModule: "libinput" The bug seems related to a known libinput bug 1579567. https://bugzilla.redhat.com/show_bug.cgi?id=1579567 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-libinput 0.27.1-1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64
[Desktop-packages] [Bug 1794104] Re: Xorg crash on first boot after apt upgrade
install mesa from a ppa: apt-add-repository ppa:canonical-x/x-staging and install updates ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1794104 Title: Xorg crash on first boot after apt upgrade Status in xorg package in Ubuntu: Incomplete Bug description: I installed a daily snapshot of 18.10 in a VM. After removing some unneccessary application, I ran apt update apt upgrade and rebooted. I noticed X crashing after the reboot, taking me back to the login manager. I have the option selected to automatically login without password. X did not crash when coming up the second time, tough. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: CompositorRunning: None Date: Mon Sep 24 15:54:18 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 5.2.18, 4.18.0-7-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-09-14 (10 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180913) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=ecdea6ce-6b53-45e4-ac1e-1caae18058d5 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1794104/+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 1791090] Re: Xorg fails to start with radeon (kernel rejects radeon command stream from Xorg)
This is fixed with x-x-v-ati 1:18.1.0-1 Thanks! ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1791090 Title: Xorg fails to start with radeon (kernel rejects radeon command stream from Xorg) Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: The shell fails to start with latest version of xorg and radeon drivers. From the journal: sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: (II) RADEON(0): Setting screen physical size to 508 x 285 sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: radeon: The kernel rejected CS, see dmesg for more information (-22). sept. 06 08:06:26 sark kernel: radeon :01:00.0: evergreen_cs_track_validate_texture:855 texture bo too small (layer size 8847360, offset 0, max layer 1, depth 1, bo size 4096) (1920 1152) sept. 06 08:06:26 sark kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! The shell starts normally under wayland. Downgrading the following packages fixed the problem: xserver-xorg-video-qxl:amd64 (0.1.5-2build2, 0.1.5-2build1) xserver-xorg-video-vesa:amd64 (1:2.4.0-1, 1:2.3.4-1build3) xserver-xorg-video-amdgpu:amd64 (18.0.1-1build1, 18.0.1-1) xserver-xorg-core:amd64 (2:1.20.1-1ubuntu1, 2:1.19.6-1ubuntu4) xserver-xorg-video-fbdev:amd64 (1:0.5.0-1, 1:0.4.4-1build6) xserver-xorg-video-intel:amd64 (2:2.99.917+git20171229-1build1, 2:2.99.917+git20171229-1) xserver-xorg-video-vmware:amd64 (1:13.3.0-2build1, 1:13.2.1-1build1) xserver-xorg-video-ati:amd64 (1:18.0.1-1build1, 1:18.0.1-1) xserver-xorg-video-radeon:amd64 (1:18.0.1-1build1, 1:18.0.1-1) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xserver-xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 6 15:03:11 2018 DistUpgraded: 2018-03-24 15:02:43,050 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:1482] InstallationDate: Installed on 2014-07-15 (1514 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=0889d734-ea91-4bdb-9d16-2a0a923ad3d1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-03-24 (165 days ago) dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.93-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791090/+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 1794231] [NEW] missing driver
Public bug reported: abc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 10:48:44 2018 InstallationDate: Installed on 2017-07-20 (431 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1794231 Title: missing driver Status in xorg package in Ubuntu: New Bug description: abc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 10:48:44 2018 InstallationDate: Installed on 2017-07-20 (431 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1794231/+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
