[Desktop-packages] [Bug 307713] Re: BBC tree UI does not expand
** Changed in: gtk Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/307713 Title: BBC tree UI does not expand Status in GTK+: Expired Status in gtk+2.0 package in Ubuntu: Triaged Bug description: Binary package hint: totem http://uk.youtube.com/watch?v=CrteBR1QOYw I think this might be a general GTK problem. Could not browse the BBC content in the navigation video as the YouTube video demonstrates. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/307713/+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 440520] Re: GTK+ whines when I'm using synergy
** Changed in: gtk Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/440520 Title: GTK+ whines when I'm using synergy Status in GTK+: Expired Status in gtk+2.0 package in Ubuntu: Triaged Bug description: I use two computers next to each other (laptop, desktop), and synergy to share the keyboard and mouse between them. Gtk apps tend to output this whenever I move the mouse from one machine to another: sys:1: GtkWarning: /build/buildd/gtk+2.0-2.18.0/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 39755776 (except they tend to say that or similar things many, many times). As far as I can see, nothing bad happens, it's just a lot of useless warnings. Please turn them off. ProblemType: Bug Architecture: amd64 Date: Fri Oct 2 14:31:28 2009 DistroRelease: Ubuntu 9.10 Package: libgtk2.0-0 2.18.0-1ubuntu2 ProcEnviron: PATH=(custom, user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SourcePackage: gtk+2.0 Uname: Linux 2.6.31-11-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/440520/+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 1738664] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
** Changed in: sane-backends (Debian) Status: Fix Committed => Fix Released -- 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/1738664 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in dpkg package in Ubuntu: Invalid Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends package in Debian: Fix Released Bug description: *** to get a workaround, try: sudo apt-get -o Dpkg::Options::="--force-overwrite" install --reinstall libsane1:i386 (or your real package name) *** An error occured error:broken count>0 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Mon Dec 18 01:06:19 2017 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-baiIM1/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-12-16 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1738664/+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 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Unsubscribing the Ubuntu Sponsors Team for now, due to Sebastien's comment that more work needs to be done. Please resubscribe the Sponsors Team once adequate tests have been added. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Triaged Status in ubuntu-geoip source package in Artful: Triaged Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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 1623666] Re: iOS device contents not displayed in Ubuntu
It appears to me that upon my move this date to iPhone's iOS 11.3 Apple may have finally given us transparent usb file system access to our photos. See Bug # 1718554, no. 8. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Fix Released Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+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 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices
EUREKA (maybe) ! This evening I took the iPhone update to iOS 11.3, and just out of curiosity I decided to check out the iphone as an attached device in the file manager. And I'm in. I don't know why. I did not use idevicepair nor ifuse. If I run ideviceinfo, I still get "ERROR: Could not connect to lockdownd, error code -3". In the file manager I found that clicking on a thumbnail gave me the photo. Messing around in the command line, a call to "df" suggested that I look at "/run/user/1000". Going there I found a current datestamp on its subdirectory "gvfs" and within that a sole item with robotic name "gphoto2:host=%5Busb%3A004%2C023%5D". Inside that there is a single directory "DCIM" (less than I used to see in iOS 10.3), but that has always been the place for photos. Within DCIM there are subdirectories "100CLOUD" and "100APPLE". I'm not sure what that's about, but the photos in the first are older and are all of size 3264x2448. During the time period for the photos in 100CLOUD, I changed to a new phone, but the latest photos in there were taken on the new phone. In 100APPLE the photos are all of size 4032x3024. I'm guessing that usb infra-structure invoked some gphoto infra- structure, and that libimobiledevice is not in the picture, but I don't know. And for the moment I'm guessing that Apple has cleaned up its act with iOS 11.3. My Ubuntu is 16.04.4 LTS, and I'm running the Mate evolute of classic gnome. In the Mate GUI connecting the phone to a usb port causes an icon to appear on my desktop. A right click on that icon gives me an unmount option that I used before disconnecting the phone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1718554 Title: Need updated libimobiledevice to mount IOS 11 devices Status in libimobiledevice package in Ubuntu: Fix Released Bug description: After upgrading to IOS 11, I stopped being able to mount my ipad in ubuntu. The relevant log lines from gvfs-afc are: gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc) gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount) gvfsd[1855]: afc: Lockdown client try #0 gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client' gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown error (-3)) The fix is here in the upstream github: https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1718554/+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 1495826] Re: hpps crashed with BrokenPipeError in __main__: [Errno 32] Broken pipe
The attachment "hpps.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1495826 Title: hpps crashed with BrokenPipeError in __main__: [Errno 32] Broken pipe Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: Got this error after today's updates. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: hplip 3.15.7-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Wed Sep 9 09:07:05 2015 ExecutablePath: /usr/lib/cups/filter/hpps InstallationDate: Installed on 2010-10-25 (1785 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Precision WorkStation T3400 Papersize: letter ProcCmdline: /usr/bin/python3 /usr/lib/cups/filter/hpps 2822 wgarcia printable 1 HPRGBEmulation=DefaultSRGB\ HPGeneralHalftone=Smooth\ HPGraphicsNeutralGrays=Black\ noHPEconoMode\ number-up=1\ HPEdgeControl=Normal\ PageSize=Letter\ InputSlot=Auto\ HPPhotoNeutralGrays=ProcessBlack\ HPTextNeutralGrays=Black\ noHPEasyColor\ MediaType=Unspecified\ HPColorAsGray\ job-uuid=urn:uuid:1c51f32e-7371-3dc7-60eb-e363d3b6af75\ job-originating-host-name=localhost\ date-time-at-creation=\ date-time-at-processing=\ time-at-creation=1441782411\ time-at-processing=1441782411 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=dadc68cb-c217-4aef-a751-ba0b61137c4a ro quiet splash PythonArgs: ['/usr/lib/cups/filter/hpps', '2822', 'wgarcia', 'printable', '1', 'HPRGBEmulation=DefaultSRGB HPGeneralHalftone=Smooth HPGraphicsNeutralGrays=Black noHPEconoMode number-up=1 HPEdgeControl=Normal PageSize=Letter InputSlot=Auto HPPhotoNeutralGrays=ProcessBlack HPTextNeutralGrays=Black noHPEasyColor MediaType=Unspecified HPColorAsGray job-uuid=urn:uuid:1c51f32e-7371-3dc7-60eb-e363d3b6af75 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1441782411 time-at-processing=1441782411'] SourcePackage: hplip Title: hpps crashed with BrokenPipeError in __main__: [Errno 32] Broken pipe Traceback: Traceback (most recent call last): File "/usr/lib/cups/filter/hpps", line 354, in os.write(output_fd, data) BrokenPipeError: [Errno 32] Broken pipe UpgradeStatus: Upgraded to wily on 2015-09-02 (12 days ago) UserGroups: dmi.bios.date: 06/04/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0TP412 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/04/2009:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T3400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1495826/+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 1707632] Re: Connecting HDMI freezes everythin
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1707632 Title: Connecting HDMI freezes everythin Status in xorg package in Ubuntu: Expired Bug description: I ones install some invidia package but I could fix that. Now sometimes if I'm connecting a external display all freezes thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 31 13:24:37 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201707110418~ubuntu16.04.1, 4.4.0-83-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:503e] InstallationDate: Installed on 2015-12-21 (587 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20DKS1TX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=8ccc6327-a7cb-4dd3-848c-4f3b2a9d4707 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET70WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DKS1TX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJEET70WW(1.19):bd08/25/2015:svnLENOVO:pn20DKS1TX00:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DKS1TX00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DKS1TX00 dmi.product.version: ThinkPad S1 Yoga 12 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jul 31 13:21:21 2017 xserver.configfile: default xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12615 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1707632/+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 1705811] Re: ?
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1705811 Title: ? Status in xorg package in Ubuntu: Expired Bug description: Kernel error.. If the driver is missing .. Radeon? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-86.109-generic 4.4.73 Uname: Linux 4.4.0-86-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: Running 0dns-down to make sure resolv.conf is ok...done. * Setting up X socket directories... [240G [234G[ OK ] * Starting devolo Network Service devolonetsvc [240G [234G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jul 22 10:01:42 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/7570] [1002:68d9] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 5570 [174b:e142] InstallationDate: Installed on 2016-01-17 (551 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Veriton M430 ProcEnviron: LANGUAGE=fi_FI PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-86-generic root=UUID=bee4d1dd-f135-42b5-8494-0ca9ad043773 ro plymouth:debug splash drm.debug=0xe quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A2 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: RS880M05 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A2:bd04/21/2010:svnAcer:pnVeritonM430:pvr:rvnAcer:rnRS880M05:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton M430 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jul 22 09:59:46 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705811/+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 1707448] Re: Random freezes.
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1707448 Title: Random freezes. Status in xorg package in Ubuntu: Expired Bug description: Random freezes. It does not generate an error message. It seems to be related to video drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jul 29 18:40:51 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation NV40 [GeForce 6800 XT] [10de:0048] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-07-09 (20 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic root=UUID=aff9cad4-3e7e-4a04-ad79-367d2e8edc1a ro quiet plymouth:debug=1 splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5VDC-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd11/08/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5VDC-X:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Jul 24 13:54:17 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputMicrosoft Basic Optical Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1707448/+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 1706848] Re: This error message appears at startup
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1706848 Title: This error message appears at startup Status in xorg package in Ubuntu: Expired Bug description: [ 2.235485] nouveau :01:00.0: bus: MMIO read of FAULT at 3e6684 [IBUS] Even after the xorg update the error continues. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 27 00:59:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti] [3842:3753] InstallationDate: Installed on 2017-07-21 (5 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=73638941-2a1f-4419-940b-ee07b54dce2b ro locale=pt_BR quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jul 27 00:56:08 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 8 inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1706848/+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 1708520] Re: no hdmi signal
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1708520 Title: no hdmi signal Status in xorg package in Ubuntu: Expired Bug description: i cant connect my laptop to my tv through an hdmi it says no signal ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Aug 3 15:38:45 2017 DistUpgraded: 2017-07-29 00:23:28,354 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:80b0] InstallationDate: Installed on 2017-07-14 (20 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: HP HP Pavilion Notebook ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic root=UUID=5893fc24-8d35-43ea-8baf-d032c38f7919 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-07-29 (5 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B0 dmi.board.vendor: HP dmi.board.version: 81.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.10:bd07/14/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B0:rvr81.27:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Aug 3 15:34:47 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1708520/+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 1748029] Re: Dragging and dropping a window in the top bar causes GNOME shell to become unusable
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1748029 Title: Dragging and dropping a window in the top bar causes GNOME shell to become unusable Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: I have an external monitor in portrait mode, which means that the top of my external monitor is substantially above my laptop monitor (which has the top bar). If I move a window by holding Meta and dragging it from the bottom, and accidentally let go with the window overlapping the top bar, then GNOME Shell becomes effectively unresponsive. My cursor is stuck as the move hand cursor, and I can move it but do nothing else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 7 17:07:38 2018 DistUpgraded: 2018-01-23 11:42:22,182 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.6, 4.13.0-31-generic, x86_64: installed virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T440p [17aa:220e] InstallationDate: Installed on 2017-10-23 (107 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20ANCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-01-23 (15 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GLET70WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 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/gnome-shell/+bug/1748029/+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 1748029] Re: Dragging and dropping a window in the top bar causes GNOME shell to become unusable
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1748029 Title: Dragging and dropping a window in the top bar causes GNOME shell to become unusable Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: I have an external monitor in portrait mode, which means that the top of my external monitor is substantially above my laptop monitor (which has the top bar). If I move a window by holding Meta and dragging it from the bottom, and accidentally let go with the window overlapping the top bar, then GNOME Shell becomes effectively unresponsive. My cursor is stuck as the move hand cursor, and I can move it but do nothing else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 7 17:07:38 2018 DistUpgraded: 2018-01-23 11:42:22,182 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.6, 4.13.0-31-generic, x86_64: installed virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T440p [17aa:220e] InstallationDate: Installed on 2017-10-23 (107 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20ANCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-01-23 (15 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GLET70WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 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/gnome-shell/+bug/1748029/+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 1749106] Re: Intel Graphics Not working
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1749106 Title: Intel Graphics Not working Status in xorg package in Ubuntu: Expired Bug description: Intel(R) UHD Graphics 630 this is my graphics chipset and i have Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 CPUs), ~3.7GHz processor. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Feb 13 14:41:41 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b45] InstallationDate: Installed on 2018-02-07 (6 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=5c03ac25-b804-4a10-836f-d148bb6d592b ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.00 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.00:bd09/01/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.name: MS-7B45 dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.85-5~x~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~x~padoka0 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~x~padoka0 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Feb 13 14:37:17 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: No devices detected. open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749106/+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 1592177] Re: Built-in search almost impossible to use in GTK file chooser
** Changed in: gtk Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1592177 Title: Built-in search almost impossible to use in GTK file chooser Status in GTK+: Expired Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: New Bug description: I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 that the built-in search functionality is almost impossible to use in the GTK file chooser (though it is the same one that allows you to save files as well as choose them). So if one types something into the search, after they have typed the first letter it will immediately select the top search result meaning one has to re-select the search box, this happens for every letter so searching for a long string becomes very annoying. If one carries on typing once it has selected the top result and unselected the search box it will start searching in the other search which only looks at results. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1592177/+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 1749313] Re: Mouse icon flickers when connected to i-tec USB 3.0 Docking Station
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1749313 Title: Mouse icon flickers when connected to i-tec USB 3.0 Docking Station Status in xorg package in Ubuntu: Expired Bug description: I am using the built-in laptop screen, one external monitor connected directly to my laptop via HDMI, and one external monitor connect via a i-tec USB 3.0 Docking Station. What happens is my mouse cursor flickers and is followed by an weird rectangle, in which the screen doesn't update. Deactivating my laptop screen didn't change anything. This is not reproducible if I only use the laptop screen and HDMI connected external monitor. WORKAROUND: Log out and in again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm 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.25 Wed Jan 24 20:02:43 PST 2018 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 23:58:09 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-31-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:071a] NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GK107M [GeForce GT 640M] [1025:071b] InstallationDate: Installed on 2017-12-06 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Acer Aspire M5-581TG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=ac6372c5-a60f-47d5-8eab-91390b01a680 ro noplymouth SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2013 dmi.bios.vendor: Acer dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: MA51_HX dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnAcer:bvrV2.11:bd02/25/2013:svnAcer:pnAspireM5-581TG:pvrV2.11:rvnAcer:rnMA51_HX:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.11: dmi.product.family: Type1Family dmi.product.name: Aspire M5-581TG dmi.product.version: V2.11 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Feb 13 23:14:54 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749313/+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 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff
** Changed in: gtk Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff Status in GTK+: Expired Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Hi, Marmuta wrote a patch for this issue, that I applied to the gtk+3.0 package shipping currently in the development version of Ubuntu zesty. You will find the corresponding debdiff attached to this bug thread. Marmuta performed tests with org.gnome.desktop.interface scaling- factor = 2 , where few issues are left for Onboard on hidpi screens, that are not related to gtk, but rather to unity-greeter or gnome- screensaver. He did not notice any issue with scaling-factor = 1. Can a sponsor please review the debdiff? Thanks in advance. Francesco = Original description: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1572331/+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 1764049] [NEW] [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card
Public bug reported: Audio is very glitchy through speakers while using any application. Have tried a lot of different things, and configured my audio, but still can not get audio to not skip. I'm using Ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: chuck 1786 F...m pulseaudio /dev/snd/controlC0: chuck 1786 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 14 22:31:49 2018 InstallationDate: Installed on 2018-03-12 (33 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2017 dmi.bios.vendor: AMI dmi.bios.version: F.36 dmi.board.asset.tag: 8CC7460L0N dmi.board.name: 81BB dmi.board.vendor: HP dmi.board.version: dmi.chassis.asset.tag: 8CC7460L0N dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.36:bd07/20/2017:svnHP:pn20-c013w:pvr:rvnHP:rn81BB:rvr:cvnHP:ct13:cvr: dmi.product.family: 103C_53316J HP Desktop dmi.product.name: 20-c013w dmi.sys.vendor: HP modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2018-04-04T21:49:05.382211 mtime.conffile..etc.pulse.default.pa: 2018-04-14T20:03:46.503451 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1764049 Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: Audio is very glitchy through speakers while using any application. Have tried a lot of different things, and configured my audio, but still can not get audio to not skip. I'm using Ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: chuck 1786 F...m pulseaudio /dev/snd/controlC0: chuck 1786 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 14 22:31:49 2018 InstallationDate: Installed on 2018-03-12 (33 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2017 dmi.bios.vendor: AMI dmi.bios.version: F.36 dmi.board.asset.tag: 8CC7460L0N dmi.board.name: 81BB dmi.board.vendor: HP dmi.board.version: dmi.chassis.asset.tag: 8CC7460L0N dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.36:bd07/20/2017:svnHP:pn20-c013w:pvr:rvnHP:rn81BB:rvr:cvnHP:ct13:cvr: dmi.product.family: 103C_53316J HP Desktop dmi.product.name: 20-c013w dmi.sys.vendor: HP modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2018-04-04T21:49:05.382211 mtime.conffile..etc.pulse.default.pa: 2018-04-14T20:03:46.503451 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1764049/+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 1495826] Re: hpps crashed with BrokenPipeError in __main__: [Errno 32] Broken pipe
This error seems to be in the /prnt/filters/hpps file. The file handle output_fd is never opened. The line opens the file (150) is commented out. The issue is that when the HPPS filter throws an error, it attempts to write to a non-existant temp file. It could be solved by uncommenting line 150, or even better, adding some exception handling. See attached patch. ** Patch added: "hpps.patch" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1495826/+attachment/5116032/+files/hpps.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1495826 Title: hpps crashed with BrokenPipeError in __main__: [Errno 32] Broken pipe Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: Got this error after today's updates. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: hplip 3.15.7-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Wed Sep 9 09:07:05 2015 ExecutablePath: /usr/lib/cups/filter/hpps InstallationDate: Installed on 2010-10-25 (1785 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Precision WorkStation T3400 Papersize: letter ProcCmdline: /usr/bin/python3 /usr/lib/cups/filter/hpps 2822 wgarcia printable 1 HPRGBEmulation=DefaultSRGB\ HPGeneralHalftone=Smooth\ HPGraphicsNeutralGrays=Black\ noHPEconoMode\ number-up=1\ HPEdgeControl=Normal\ PageSize=Letter\ InputSlot=Auto\ HPPhotoNeutralGrays=ProcessBlack\ HPTextNeutralGrays=Black\ noHPEasyColor\ MediaType=Unspecified\ HPColorAsGray\ job-uuid=urn:uuid:1c51f32e-7371-3dc7-60eb-e363d3b6af75\ job-originating-host-name=localhost\ date-time-at-creation=\ date-time-at-processing=\ time-at-creation=1441782411\ time-at-processing=1441782411 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=dadc68cb-c217-4aef-a751-ba0b61137c4a ro quiet splash PythonArgs: ['/usr/lib/cups/filter/hpps', '2822', 'wgarcia', 'printable', '1', 'HPRGBEmulation=DefaultSRGB HPGeneralHalftone=Smooth HPGraphicsNeutralGrays=Black noHPEconoMode number-up=1 HPEdgeControl=Normal PageSize=Letter InputSlot=Auto HPPhotoNeutralGrays=ProcessBlack HPTextNeutralGrays=Black noHPEasyColor MediaType=Unspecified HPColorAsGray job-uuid=urn:uuid:1c51f32e-7371-3dc7-60eb-e363d3b6af75 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1441782411 time-at-processing=1441782411'] SourcePackage: hplip Title: hpps crashed with BrokenPipeError in __main__: [Errno 32] Broken pipe Traceback: Traceback (most recent call last): File "/usr/lib/cups/filter/hpps", line 354, in os.write(output_fd, data) BrokenPipeError: [Errno 32] Broken pipe UpgradeStatus: Upgraded to wily on 2015-09-02 (12 days ago) UserGroups: dmi.bios.date: 06/04/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0TP412 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/04/2009:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T3400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1495826/+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 1764042] [NEW] wifi crashes in ubuntu 16.04 lts xenial
Public bug reported: Good day, I am a new ubuntu user and I've been finding a solution everywhere to this issue: I run ubuntu (studio) 16.04 lts, code name: xenial dual booted with windows 8 on Hp notebook 15. When I first installed ubuntu, hotspot from my BlackBerry q10 connects fine but suddenly it stopped and every time i connect it pops up the dialog box: wifi authentication required by wifi network and expects me to retype a password that is already correct! I have tried reinstalling network manager, adding [device] wifi-rand*... to network*.conf and so on and rebooted over and again. Nothing has changed yet. The same applies to my bluetooth too (it was okay suddenly it changed) I need help quick, I need my pc for an imminent exam. Thank you ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1764042 Title: wifi crashes in ubuntu 16.04 lts xenial Status in network-manager package in Ubuntu: New Bug description: Good day, I am a new ubuntu user and I've been finding a solution everywhere to this issue: I run ubuntu (studio) 16.04 lts, code name: xenial dual booted with windows 8 on Hp notebook 15. When I first installed ubuntu, hotspot from my BlackBerry q10 connects fine but suddenly it stopped and every time i connect it pops up the dialog box: wifi authentication required by wifi network and expects me to retype a password that is already correct! I have tried reinstalling network manager, adding [device] wifi-rand*... to network*.conf and so on and rebooted over and again. Nothing has changed yet. The same applies to my bluetooth too (it was okay suddenly it changed) I need help quick, I need my pc for an imminent exam. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1764042/+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 202210] Re: gcalctool has problem with big sums
** Changed in: gcalctool Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcalctool in Ubuntu. https://bugs.launchpad.net/bugs/202210 Title: gcalctool has problem with big sums Status in GCalctool: Expired Status in gcalctool package in Ubuntu: Fix Released Status in gcalctool source package in Hardy: Fix Released Status in gcalctool source package in Intrepid: Fix Released Bug description: How to reproduce : 1) Open gnome-calculator 2) Type 1+1+1+1+1000+1000 Results: You don't see the result unless you resize the window (make it wider). To manage notifications about this bug go to: https://bugs.launchpad.net/gcalctool/+bug/202210/+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 1764034] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1764034/+attachment/5115980/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1764034/+attachment/5115982/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1764034/+attachment/5115985/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1764034/+attachment/5115986/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1764034/+attachment/5115987/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1764034/+attachment/5115988/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1764034/+attachment/5115989/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1764034 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: error report just popped up everything appears to be working fine. Will reboot and see if error occurs again. If it does will try to gather more information. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: hostname 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 18:51:51 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-01-01 (103 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-04-04 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764034/+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 1379359] Re: Large printers list in print dialog
** Changed in: gtk Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1379359 Title: Large printers list in print dialog Status in GTK+: Expired Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Print dialog show all printers discovered by Avahi, this is a good idea for home usage but very bad idea for large office with many printers, I think this functionality should be configurable Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1379359/+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 1764030] Re: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
*** This bug is a duplicate of bug 1754202 *** https://bugs.launchpad.net/bugs/1754202 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754202, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1764030/+attachment/5115959/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1764030/+attachment/5115961/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1764030/+attachment/5115965/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1764030/+attachment/5115966/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1764030/+attachment/5115967/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1764030/+attachment/5115968/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1764030/+attachment/5115969/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1754202 gnome-calendar crashed with SIGSEGV in gtk_image_reset() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1764030 Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear() Status in gnome-calendar package in Ubuntu: New Bug description: On Quit ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Apr 15 11:06:09 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2017-09-29 (197 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7ff177853667 :mov 0x28(%rdi),%rbp PC (0x7ff177853667) ok source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: gtk_image_clear () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear() UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1764030/+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 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts
*** This bug is a duplicate of bug 1438014 *** https://bugs.launchpad.net/bugs/1438014 Reposted to gnome's gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/180 ** Bug watch removed: GNOME Bug Tracker #607668 https://bugzilla.gnome.org/show_bug.cgi?id=607668 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1667227 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts Status in gnome-terminal package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Invalid Bug description: 1) $ lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 2) $ apt-cache policy mate-terminal mate-terminal: Installed: 1.17.0-0ubuntu1 Candidate: 1.17.0-0ubuntu1 3) Open mate-terminal Select "Edit" -> "Keyboard Shortcuts" Select "Help"->"Contents", click on default shortcut key "F1" to change Try to set it to various key sequences. Sometimes bug is triggered by pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting Ctrl-Shift-W / Crtl-Shift-Alt-W Expected: changed keyboard shortcut for "Help"->"Contents" 4) Abort and closed mate-terminal ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-terminal 1.17.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Feb 23 09:33:19 2017 ExecutablePath: /usr/bin/mate-terminal ExecutableTimestamp: 1484233434 InstallationDate: Installed on 2017-02-22 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-terminal ProcCwd: /home/user SegvAnalysis: Segfault happened at: 0x7f883e41c321 : testb $0x4,0x16(%rax) PC (0x7f883e41c321) ok source "$0x4" ok destination "0x16(%rax)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1667227/+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 78510] Re: filechoosers auto complete selection stolen by clipboard programs
** Changed in: gtk Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/78510 Title: filechoosers auto complete selection stolen by clipboard programs Status in GTK+: Expired Status in One Hundred Papercuts: New Status in firefox-3.0 package in Ubuntu: Invalid Status in gtk+2.0 package in Ubuntu: Triaged Bug description: Steps to reproduce: Enable a clipboard program such as Klipper/Glipper/Parcellite then: 1. Attach a file in gmail by clicking on browse. A file selection dialog (File Upload) appears. 2. Write on location the path to a file which will be auto-completed as you write. Use a filename that shares the beginning of the name with other files in the same directory. For example, foo/barbarbar and foo/barfoobar 3. When the filename you are looking for appears completed in the location bar press enter. 4. The filename selected will be foo/bar which does not correspond to any existing file. Problem (copied from upstream): The problem is that the file chooser's entry uses the selection in GtkEntry to hold state about "this is what will be inserted if the user hits Tab", but klipper steals the selection ownership. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/78510/+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 999978] Re: Keyboard Shortcut input doesn't recognise Alt+Print
** Changed in: gtk Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/78 Title: Keyboard Shortcut input doesn't recognise Alt+Print Status in GTK+: Expired Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When inputting a shortcut in the Keyboard Shortcuts menu, pressing Alt+Print is not recognised. Instead, "Alt L" is shown as the input. To Repeat: Open Keyboard Shortcuts menu. Double click to change a shortcut, press Alt+Print. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Tue May 15 23:41:23 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/78/+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 1764025] [NEW] Network manager doesn't work with option: dns=dnsmasq
Public bug reported: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Bionic Beaver (development branch) Release:18.04 Codename: bionic $ uname -a Linux alex-VirtualBox2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy network-manager network-manager: Installed: 1.10.6-2ubuntu1 Candidate: 1.10.6-2ubuntu1 Version table: *** 1.10.6-2ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy dnsmasq dnsmasq: Installed: (none) Candidate: 2.79-1 Version table: 2.79-1 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu bionic/universe i386 Packages Once I set: [main] plugins=ifupdown,keyfile dns=dnsmasq # <- this line was added ... DNS resolving stops to work. $ ping google.com.au ping: google.com.au: Temporary failure in name resolution $ nslookup google.com.au Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find google.com.au: SERVFAIL it's only one setting I changed. /etc/NetworkManager/dnsmasq.d folder is empty. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1764025 Title: Network manager doesn't work with option: dns=dnsmasq Status in network-manager package in Ubuntu: New Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic $ uname -a Linux alex-VirtualBox2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy network-manager network-manager: Installed: 1.10.6-2ubuntu1 Candidate: 1.10.6-2ubuntu1 Version table: *** 1.10.6-2ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy dnsmasq dnsmasq: Installed: (none) Candidate: 2.79-1 Version table: 2.79-1 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu bionic/universe i386 Packages Once I set: [main] plugins=ifupdown,keyfile dns=dnsmasq # <- this line was added ... DNS resolving stops to work. $ ping google.com.au ping: google.com.au: Temporary failure in name resolution $ nslookup google.com.au Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find google.com.au: SERVFAIL it's only one setting I changed. /etc/NetworkManager/dnsmasq.d folder is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1764025/+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 1763996] Re: Screen dims when wireless device has low battery
** Summary changed: - Screen dims when wireless devices have low battery levels + Screen dims when wireless device has low battery -- 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/1763996 Title: Screen dims when wireless device has low battery Status in gnome-settings-daemon package in Ubuntu: New Bug description: I have noticed this happening on my Thinkpad x230, but I have also seen this in other laptops. The laptop with adequate (above 40%) battery charge suddenly dims the screen after displaying a notification about my logitech performance mx having low battery. I expect the battery levels on my wireless peripherals having no effect over my laptop's power settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 20:15:55 2018 InstallationDate: Installed on 2018-04-08 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1763996/+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 1504404] Re: Imported image got black
Filed against the wrong package, thus nobody found it. ** Package changed: liborcus (Ubuntu) => libreoffice (Ubuntu) -- 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/1504404 Title: Imported image got black Status in libreoffice package in Ubuntu: New Bug description: Mint 17.2 LibO 5.0.2 from PPA When I try to Insert -> Image, select a file, (if activated Preview it shows correctly) and then Insert, I only get a Black Box in big images (2.9 mb) It also happens if I try to Copy & Paste or Dragging I tried with LibO 4.4.3 rc2 from Mint 17.2 and I got the same results inserting, copying or dragging: a Black Box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1504404/+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 1758067] Re: OpenType font variation not working correctly
Support is not implemented yet. ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Wishlist -- 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/1758067 Title: OpenType font variation not working correctly Status in libreoffice package in Ubuntu: New Bug description: I tried to open an OpenDocument presentation with text formatted in Adobe Source Sans (OpenType version installed). But LibreOffice did not recognise the latest version of this font despite refreshing font cache several times. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: InstallationMedia: Package: libreoffice 1:6.0.2-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1758067/+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 1764008] Re: Installing 32-bit Kubuntu 18.04 encrypted LVM fails
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1764008 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1764008 Title: Installing 32-bit Kubuntu 18.04 encrypted LVM fails Status in udisks2 package in Ubuntu: New Bug description: Using daily build from http://cdimage.ubuntu.com/kubuntu/daily- live/20180414/bionic-desktop-i386.iso Installing on ThinkPad X41 with two drives. Seemed to install, on reboot got black screen with blinking cursor top left. Did not ask for encryption password when finishing. Installing on same system with only one drive worked correctly. There, ending installation asked for encryption password to finish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1764008/+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 1764010] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung »hash_table->live
*** This bug is a duplicate of bug 1763909 *** https://bugs.launchpad.net/bugs/1763909 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1763909, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1764010/+attachment/5115832/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1764010/+attachment/5115834/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1764010/+attachment/5115838/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1764010/+attachment/5115839/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1764010/+attachment/5115840/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1764010/+attachment/5115841/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1764010/+attachment/5115842/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1763909 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1764010 Title: gnome-shell-extension-prefs assert failure: gnome-shell-extension- prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung »hash_table->live_entries == 0« nicht erfüllt. Status in gnome-shell package in Ubuntu: New Bug description: Crash happened after changing settings of Gnome Shell Extension Topicons Plus. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AssertionMessage: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung »hash_table->live_entries == 0« nicht erfüllt. CurrentDesktop: GNOME Date: Sat Apr 14 23:36:30 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell-extension-prefs InstallationDate: Installed on 2017-11-13 (152 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) ProcCmdline: gnome-shell-extension-prefs topic...@phocean.net ProcEnviron: LANGUAGE=de_DE: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: __assert_fail_base (fmt=0x7f45a0919195 , assertion=assertion@entry=0x7f45b170bd05 "hash_table->live_entries == 0", file=file@entry=0x7f45b170bce8 "../../../../src/cairo-hash.c", line=line@entry=217, function=function@entry=0x7f45b170be90 "_cairo_hash_table_destroy") at assert.c:92 __GI___assert_fail (assertion=0x7f45b170bd05 "hash_table->live_entries == 0", file=0x7f45b170bce8 "../../../../src/cairo-hash.c", line=217, function=0x7f45b170be90 "_cairo_hash_table_destroy") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung »hash_table->live_entries == 0« nicht erfüllt. UpgradeStatus: Upgraded to bionic on 2018-04-12 (2 days ago) UserGroups: adm libvirtd lxd sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764010/+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 1763662] Re: H264 missing from WebRTC (regression)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1763662 Title: H264 missing from WebRTC (regression) Status in chromium-browser package in Ubuntu: Confirmed Bug description: H264 is missing from WebRTC in Chromium 65.0.3325.181. This is a regression. It worked in Chromium 64.0.3282.167. According to the webrtc team it might be because of a missing flag [1]. Steps to reproduce: 1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser chromium-codecs-ffmpeg-extra 2. open a tab with chrome://webrtc-internals 3. Create a room in https://appr.tc and join the room. 3. Check the SDP offer in webrtc-internals. Select the https://appr.tc/r/ tab and click on the createOfferOnSuccess event. We should have H264 in the SDP offer but it's missing: a=rtpmap:100 H264/9 [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=9096 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1763662/+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 1763662] Re: H264 missing from WebRTC (regression)
Same issue here. But I don't read the webrtc team description as a missing flag. Even with the flag I think it still does not work. -- 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/1763662 Title: H264 missing from WebRTC (regression) Status in chromium-browser package in Ubuntu: Confirmed Bug description: H264 is missing from WebRTC in Chromium 65.0.3325.181. This is a regression. It worked in Chromium 64.0.3282.167. According to the webrtc team it might be because of a missing flag [1]. Steps to reproduce: 1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser chromium-codecs-ffmpeg-extra 2. open a tab with chrome://webrtc-internals 3. Create a room in https://appr.tc and join the room. 3. Check the SDP offer in webrtc-internals. Select the https://appr.tc/r/ tab and click on the createOfferOnSuccess event. We should have H264 in the SDP offer but it's missing: a=rtpmap:100 H264/9 [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=9096 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1763662/+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 1764008] Re: Installing 32-bit Kubuntu 18.04 encrypted LVM fails
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1764008/+attachment/5115797/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1764008 Title: Installing 32-bit Kubuntu 18.04 encrypted LVM fails Status in udisks2 package in Ubuntu: New Bug description: Using daily build from http://cdimage.ubuntu.com/kubuntu/daily- live/20180414/bionic-desktop-i386.iso Installing on ThinkPad X41 with two drives. Seemed to install, on reboot got black screen with blinking cursor top left. Did not ask for encryption password when finishing. Installing on same system with only one drive worked correctly. There, ending installation asked for encryption password to finish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1764008/+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 1764008] [NEW] Installing 32-bit Kubuntu 18.04 encrypted LVM fails
Public bug reported: Using daily build from http://cdimage.ubuntu.com/kubuntu/daily- live/20180414/bionic-desktop-i386.iso Installing on ThinkPad X41 with two drives. Seemed to install, on reboot got black screen with blinking cursor top left. Did not ask for encryption password when finishing. Installing on same system with only one drive worked correctly. There, ending installation asked for encryption password to finish. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "partman" https://bugs.launchpad.net/bugs/1764008/+attachment/5115796/+files/partman -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1764008 Title: Installing 32-bit Kubuntu 18.04 encrypted LVM fails Status in udisks2 package in Ubuntu: New Bug description: Using daily build from http://cdimage.ubuntu.com/kubuntu/daily- live/20180414/bionic-desktop-i386.iso Installing on ThinkPad X41 with two drives. Seemed to install, on reboot got black screen with blinking cursor top left. Did not ask for encryption password when finishing. Installing on same system with only one drive worked correctly. There, ending installation asked for encryption password to finish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1764008/+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 1764002] Re: chromium-browser crashed with SIGILL
*** This bug is a duplicate of bug 1763765 *** https://bugs.launchpad.net/bugs/1763765 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1763765, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1764002/+attachment/5115752/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1764002/+attachment/5115755/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1764002/+attachment/5115764/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1764002/+attachment/5115766/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1764002/+attachment/5115767/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1764002/+attachment/5115770/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1764002/+attachment/5115771/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1763765 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1764002 Title: chromium-browser crashed with SIGILL Status in chromium-browser package in Ubuntu: New Bug description: I'm reporting this as a new bug as it's the only way I can send this report into you. Even to this electronic tech, I'm being asked to understand how many holes there are in Blackpool, Lancashire. Browsers are buggy on Ubuntu 18.04. Firefox is almost impossible to keep loaded without crashing, for Chrome, there's a lot more stability, but certain actions make it crash also, mostly when booting it up after a software update. It has to be booted twice, the second time quite to very stable. First time not. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: chromium-browser 65.0.3325.181-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA4o+hlrBUAADAMAQMOJB147gololdLmSQYUFS/74AxWUVZYVmBgAEBAQEBAQEBvDQAmFEAKkAQkBMAZx8RAAAe/QA3VR9SDgAKICAgICAg/ABORUMgTENEMTg2ME5Y/wAyWjEwNTU0OFlBCiAgAMY= modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 Date: Sat Apr 14 12:06:53 2018 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2018-02-17 (56 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: Dell Inc. OptiPlex 960 ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=renderer\ --field-trial-handle=1723057349114046884,15150261428984315871,131072\ --service-pipe-token=37EAA69C933987BA6B39E9FAD8C52622\ --lang=en-GB\ --enable-offline-auto-reload\ --enable-offline-auto-reload-visible-only\ --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so\ --ppapi-flash-version=29.0.0.113\ --num-raster-threads=2\ --enable-main-frame-before-activation\ --service-request-channel-token=37EAA69C933987BA6B39E9FAD8C52622\ --renderer-client-id=46\ --shared-files=v8_context_snapshot_data:100,v8_natives_data:101,v8_snapshot_data:102 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=2eb09b3b-d6eb-48ac-97fc-4f0bbe9c0d4f ro quiet splash vt.handoff=1 Signal: 4 SourcePackage: chromium-browser StacktraceTop: () () () () () Title: chromium-browser crashed with SIGILL UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date:
[Desktop-packages] [Bug 1764001] Re: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset()
*** This bug is a duplicate of bug 1738239 *** https://bugs.launchpad.net/bugs/1738239 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1738239, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1764001/+attachment/5115741/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1764001/+attachment/5115743/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1764001/+attachment/5115746/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1764001/+attachment/5115747/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1764001/+attachment/5115748/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1764001/+attachment/5115749/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1764001/+attachment/5115750/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1738239 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1764001 Title: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset() Status in gnome-control-center package in Ubuntu: New Bug description: Was working in terminal when this bug popped up. 2 Chrome tabs were open in the background. Note - had installed Chrome from Google vs Chromium Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Other than the dialogue with the message of an error no other consequences were noted ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 13:29:13 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-04-12 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-hostname-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-hostname-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-hostname-gnu/libglib-2.0.so.0 g_slice_free_chain_with_offset () from /usr/lib/x86_64-hostname-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-hostname-gnu/libgtk-3.so.0 Title: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1764001/+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 1682455] Re: thunderbird not available in GNOME Software
I noticed that yelp was also complaining about missing help-browser icon until today when it started using native AppStream metadata instead of letting appstream-generator create the basic metadata from its .desktop. So maybe we could fix this bug sooner by creating that metadata file and including it in the firefox and thunderbird binary packages. Otherwise, I think this bug might be fixed when we get a newer version of appstream-generator installed in the Ubuntu server that provides the metadata downloads. ** Tags added: appstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1682455 Title: thunderbird not available in GNOME Software Status in firefox package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu's firefox and thunderbird ship their app icons in /usr/share/pixmaps/ Please move them to /usr/share/icons/hicolor/*/apps/ instead so that these apps can be shown as available for install in GNOME Software. References -- http://appstream.ubuntu.com/bionic/main/issues/thunderbird.html http://appstream.ubuntu.com/bionic/main/issues/firefox.html https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-icon Original Report --- I am filing this against Thunderbird, even though it also concerns another package (GNOME Software). Essentially, using a freshly installed Ubuntu GNOME 17.04, Thunderbird is not available in GNOME Software (the default software app for this flavour). You cannot find it via search or the packages browser. The only way to install it is via apt-get and even then it doesn't show in Software (see attached picture). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1682455/+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 1763996] [NEW] Screen dims when wireless devices have low battery levels
Public bug reported: I have noticed this happening on my Thinkpad x230, but I have also seen this in other laptops. The laptop with adequate (above 40%) battery charge suddenly dims the screen after displaying a notification about my logitech performance mx having low battery. I expect the battery levels on my wireless peripherals having no effect over my laptop's power settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 20:15:55 2018 InstallationDate: Installed on 2018-04-08 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1763996 Title: Screen dims when wireless devices have low battery levels Status in gnome-settings-daemon package in Ubuntu: New Bug description: I have noticed this happening on my Thinkpad x230, but I have also seen this in other laptops. The laptop with adequate (above 40%) battery charge suddenly dims the screen after displaying a notification about my logitech performance mx having low battery. I expect the battery levels on my wireless peripherals having no effect over my laptop's power settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 20:15:55 2018 InstallationDate: Installed on 2018-04-08 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1763996/+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 1763993] [NEW] bug
Public bug reported: graphics are very poor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 15 00:27:21 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS690 [Radeon X1200] [1458:d000] MachineType: Gigabyte Technology Co., Ltd. GA-MA69VM-S2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=857c15e8-651e-45d0-a401-07e1fcf2c863 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: GA-MA69VM-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd12/29/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA69VM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA69VM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA69VM-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.90+git1802210630.009634~oibaf~a version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1802241930.f0b397~oibaf~a version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1802241930.f0b397~oibaf~a version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.99+git1802211933.f777e9~oibaf~a version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1802181857.757955~oibaf~a version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1712110734.048baf~oibaf~a xserver.bootTime: Sat Apr 14 22:50:25 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSONiX USB Device KEYBOARD, id 8 inputSONiX USB Device MOUSE, id 9 inputSONiX USB Device KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages ubuntu -- 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/1763993 Title: bug Status in xorg package in Ubuntu: New Bug description: graphics are very poor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 15 00:27:21 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS690 [Radeon X1200] [1458:d000] MachineType: Gigabyte Technology Co., Ltd. GA-MA69VM-S2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=857c15e8-651e-45d0-a401-07e1fcf2c863 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: GA-MA69VM-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd12/29/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA69VM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA69VM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA69VM-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.90+git1802210630.009634~oibaf~a ve
[Desktop-packages] [Bug 1763989] Re: unity-gnome-shell-migration.17.10.py crashed with signal 5
*** This bug is a duplicate of bug 1754623 *** https://bugs.launchpad.net/bugs/1754623 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754623, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763989/+attachment/5115657/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763989/+attachment/5115659/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763989/+attachment/5115662/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763989/+attachment/5115663/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763989/+attachment/5115664/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763989/+attachment/5115665/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763989/+attachment/5115666/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1754623 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1763989 Title: unity-gnome-shell-migration.17.10.py crashed with signal 5 Status in gnome-session package in Ubuntu: New Bug description: Encountered on first boot after upgrading from 16.04 to 18.04. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 20:13:44 2018 ExecutablePath: /usr/share/session-migration/scripts/unity-gnome-shell-migration.17.10.py InstallationDate: Installed on 2015-12-25 (841 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/share/session-migration/scripts/unity-gnome-shell-migration.17.10.py ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/false Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 Signal: 5 SourcePackage: gnome-session StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: unity-gnome-shell-migration.17.10.py crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1763989/+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 1763985] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763985/+attachment/5115631/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763985/+attachment/5115633/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763985/+attachment/5115636/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763985/+attachment/5115637/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763985/+attachment/5115638/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763985/+attachment/5115639/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763985/+attachment/5115640/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763985 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashed with signal 5 in g_log_default_handler() ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 13 14:53:25 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-07-18 (635 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to bionic on 2018-04-13 (1 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763985/+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 1763983] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1754924 *** https://bugs.launchpad.net/bugs/1754924 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754924, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763983/+attachment/5115614/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763983/+attachment/5115616/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763983/+attachment/5115619/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763983/+attachment/5115620/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763983/+attachment/5115621/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763983/+attachment/5115622/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763983/+attachment/5115623/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1754924 gnome-control-center crashed with SIGSEGV in actualize_printers_list() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1763983 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() Status in gnome-control-center package in Ubuntu: New Bug description: Control center crashes when called by ordinary user, whatever the tab displayed, after a few seconds. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 19:15:37 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-03-29 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55e564f57311:mov0x90(%rbp),%rsi PC (0x55e564f57311) ok source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: lpadmin netdev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1763983/+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 1748812] Re: cannot view wifi networks after resume from suspend
I wasn't able to reproduce it with liveUSB and only one Wi-Fi connection. Will try to add more connections (few openvpn probably) -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+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 28835] Re: "Unmount" in volume right-click menu, is tech-speak and undiscoverable
** Changed in: nautilus Status: New => Expired -- 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/28835 Title: "Unmount" in volume right-click menu, is tech-speak and undiscoverable Status in One Hundred Papercuts: New Status in Nautilus: Expired Status in nautilus package in Ubuntu: Triaged Bug description: If I right-click a removable device in computer://, there is an "Unmount Volume" option. There are two issues with this: 1) "Unmount" is a technical term users may not know. "Remove safely" or something would probably be better. 2) It is not easily discoverable. This is bad for two reasons: 2.1 - People does not necessarily know that a usb-stick should be properly unmounted to ensure filesystem integrity. 2.2 - It is not possible to just eject a CD by pushing the eject button on the drive. I think the best solution for 2) is to add an Eject/Remove Safely icon in the notification area, popping up a eject/remove safely dialog when clicked. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/28835/+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 1763975] Re: DP1.2 daisy-chain flickering
The flickering does not happen if I bypass the Avocent SV340D KVM and plug directly into the monitor. Any thoughts as to why this would happen? -- 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/1763975 Title: DP1.2 daisy-chain flickering Status in xorg package in Ubuntu: New Bug description: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2 disabled on the second monitor as per Dell instructions). I am getting flickering whereby randomly display1 or display2 turn black and then back on again. When I disable DP1.2 on the display1, and therefore get a duplicate display (as opposed to extended) on display2, I get no flickering at all. The same setup yields no flickering when running from a Windows 10 box, so don't think it is the monitors. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 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: Sat Apr 14 12:52:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2068] InstallationDate: Installed on 2018-04-01 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: Intel Corporation NUC7i7BNH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763975/+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 1763975] Re: DP1.2 daisy-chain flickering
** Description changed: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to - DisplayPort on a Dell U2414 which has DP1.2 enabled and is daisy- - chainged to another Dell U2414 (DP1.2 disabled on the second monitor as - per Dell instructions). + DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has + DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2 + disabled on the second monitor as per Dell instructions). I am getting flickering whereby randomly display1 or display2 turn black and then back on again. When I disable DP1.2 on the display1, and therefore get a duplicate display (as opposed to extended) on display2, I get no flickering at all. The same setup yields no flickering when running from a Windows 10 box, so don't think it is the monitors. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 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: Sat Apr 14 12:52:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: Intel Corporation Device [8086:2068] + Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: Intel Corporation Device [8086:2068] InstallationDate: Installed on 2018-04-01 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: Intel Corporation NUC7i7BNH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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 -- 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/1763975 Title: DP1.2 daisy-chain flickering Status in xorg package in Ubuntu: New Bug description: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2 disabled on the second monitor as per Dell instructions). I am getting flickering whereby randomly display1 or display2 turn black and then back on again. When I disable DP1.2 on the display1, and therefore get a duplicate display (as opposed to extended) on display2, I get no flickering at all. The same setup yields no flickering when running from a Windows 10 box, so don't think it is the monitors. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 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: Sat Apr 14 12:52:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5927] (rev 06) (p
[Desktop-packages] [Bug 1763972] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763972/+attachment/5115545/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763972/+attachment/5115547/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763972/+attachment/5115550/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763972/+attachment/5115551/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763972/+attachment/5115552/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763972/+attachment/5115553/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763972/+attachment/5115554/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763972 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: shortly after startup ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 13 23:04:03 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-02-28 (44 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180227) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763972/+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 1763978] [NEW] nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Public bug reported: Since this week (i believe April 9th) Nvidia-prime isn't working for me. Running: Distributor ID: Ubuntu Description:Ubuntu Bionic Beaver (development branch) Release:18.04 Codename: bionic Nvidia-prime version: Nvidia-prime version: Installed: 0.8.7 Candidate: 0.8.7 Version table: *** 0.8.7 500 Error code: apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Failed with result 'exit-code'. ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1763978 Title: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Status in nvidia-prime package in Ubuntu: New Bug description: Since this week (i believe April 9th) Nvidia-prime isn't working for me. Running: Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic Nvidia-prime version: Nvidia-prime version: Installed: 0.8.7 Candidate: 0.8.7 Version table: *** 0.8.7 500 Error code: apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1763978/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
In my issue the CPU is AMD ryzen. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1763975] [NEW] DP1.2 daisy-chain flickering
Public bug reported: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to DisplayPort on a Dell U2414 which has DP1.2 enabled and is daisy- chainged to another Dell U2414 (DP1.2 disabled on the second monitor as per Dell instructions). I am getting flickering whereby randomly display1 or display2 turn black and then back on again. When I disable DP1.2 on the display1, and therefore get a duplicate display (as opposed to extended) on display2, I get no flickering at all. The same setup yields no flickering when running from a Windows 10 box, so don't think it is the monitors. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 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: Sat Apr 14 12:52:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2068] InstallationDate: Installed on 2018-04-01 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: Intel Corporation NUC7i7BNH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- 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/1763975 Title: DP1.2 daisy-chain flickering Status in xorg package in Ubuntu: New Bug description: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to DisplayPort on a Dell U2414 which has DP1.2 enabled and is daisy- chainged to another Dell U2414 (DP1.2 disabled on the second monitor as per Dell instructions). I am getting flickering whereby randomly display1 or display2 turn black and then back on again. When I disable DP1.2 on the display1, and therefore get a duplicate display (as opposed to extended) on display2, I get no flickering at all. The same setup yields no flickering when running from a Windows 10 box, so don't think it is the monitors. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 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: Sat Apr 14 12:52:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2068] InstallationDate: Installed on 2018-04-01 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: Intel Corporation NUC7i7BNH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu
[Desktop-packages] [Bug 1763973] [NEW] stupid inconsistent defalt applications for .cpp and .h files
Public bug reported: Steps to reproduce: - Navigate to a folder that contains .h and .cpp files - double-click on a .cpp file - double-click on a .h file Expected: both should be opened by default with the same application. I'd say it would make more sense that it was gedit rather than vim, given that gedit is the default for most other extensions that typically correspond to other languages, e.g. .php, .java, etc. But anyway, .cpp and .h should have the same default Observed: the default for .h files is to open in gedit; the default for .cpp files is to open in vim in a terminal. That's just stupid. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 14 18:47:51 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1197x691+723+24'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1645 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages xenial -- 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/1763973 Title: stupid inconsistent defalt applications for .cpp and .h files Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Navigate to a folder that contains .h and .cpp files - double-click on a .cpp file - double-click on a .h file Expected: both should be opened by default with the same application. I'd say it would make more sense that it was gedit rather than vim, given that gedit is the default for most other extensions that typically correspond to other languages, e.g. .php, .java, etc. But anyway, .cpp and .h should have the same default Observed: the default for .h files is to open in gedit; the default for .cpp files is to open in vim in a terminal. That's just stupid. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 14 18:47:51 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1197x691+723+24'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1645 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1763973/+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 1763973] Re: stupid inconsistent defalt applications for .cpp and .h files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1763973 Title: stupid inconsistent defalt applications for .cpp and .h files Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Navigate to a folder that contains .h and .cpp files - double-click on a .cpp file - double-click on a .h file Expected: both should be opened by default with the same application. I'd say it would make more sense that it was gedit rather than vim, given that gedit is the default for most other extensions that typically correspond to other languages, e.g. .php, .java, etc. But anyway, .cpp and .h should have the same default Observed: the default for .h files is to open in gedit; the default for .cpp files is to open in vim in a terminal. That's just stupid. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 14 18:47:51 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1197x691+723+24'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1645 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1763973/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Hi daniel, I wasn't able to reproduce with 16.04. Did you install the regular Ubuntu desktop, or a specific flavour? -- 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/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Fix Released Status in d-conf package in Ubuntu: Fix Released Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in session-migration package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Status in d-conf source package in Bionic: Fix Released Status in dconf source package in Bionic: Triaged Status in gnome-session source package in Bionic: Fix Released Status in session-migration source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Committed Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Hello. On 16.04 LTS (16.04.4) Release it looks this way: [~]$ ls -ld .config/ drwxr-xr-x 24 user1 user1 4096 apr 14 18:21 .config/ [~]$ ls -ld .local/ drwx-- 3 user1 user1 4096 apr 30 2017 .local/ Thanks. -- 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/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Fix Released Status in d-conf package in Ubuntu: Fix Released Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in session-migration package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Status in d-conf source package in Bionic: Fix Released Status in dconf source package in Bionic: Triaged Status in gnome-session source package in Bionic: Fix Released Status in session-migration source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Committed Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1759462] Re: Keyboard shortcuts not operational on 18.04
I had forgotten to update my comment (wrote on 2018-03-28: ) - About a day later the behaviour returned and the caffeine test was not effective. -- 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/1759462 Title: Keyboard shortcuts not operational on 18.04 Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: After installing 18.04, I noticed that certain keyboard shortcuts no longer function. It appears to be related to the shortcuts that gnome-settings-daemon control as my shortcuts that are provided by my desktop (Budgie) still function. Some examples are: * Media keys for volume up/down/mute * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same behaviour. I double checked, and it looks like the needed daemon is still running, ``` dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-power dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sound dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-color dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-printer dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep --color=auto gnome-settings-daemon ``` Reboot does not seem to help. However, occasionally the shortcuts do seem to work - but only very occasionally. Any other info needed? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 27 21:12:18 2018 InstallationDate: Installed on 2018-03-05 (22 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+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 1759462] Re: Keyboard shortcuts not operational on 18.04
Additional Info: I just found out another detail quite by accident. My system is set up to use the “fn” key to make the F buttons behave as an f button (F1-12). Meaning by default a press will trigger the volume up/down, etc. So when the audio keys conk out… my other f key functions (brightness, etc) still work. BUT, if I hold “alt”, and press my audio keys - they work! Now knowing this pattern, - I went through my F keys… and tested what worked (brightness, audio, mute, search) F1 (mute) - “F1” works with the “fn” key, and the mute only works when also pressing “alt” F2 (vol down) - “F2” works with the “fn” key, and the vol down only works when also pressing “alt” F3 (vol up) - “F3” works with the “fn” key, and the vol up only works when also pressing “alt” F4 (disable mic) - Works as expected. F5 (bright down) - Works as expected. F6 (bright up) - Works as expected. F7 (projector) - Untested. F8 (airplane mode) - Works as expected. F9 (tools) - Does not work in any capacity F10 (Search) - “F10” works with the “fn” key, and the search only works when also pressing “alt” F11 (launchA) - Works as expected. F12 (open file browser) - Works as expected. Also filed an upstream bug. https://bugzilla.gnome.org/show_bug.cgi?id=794385 ** Bug watch added: GNOME Bug Tracker #794385 https://bugzilla.gnome.org/show_bug.cgi?id=794385 -- 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/1759462 Title: Keyboard shortcuts not operational on 18.04 Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: After installing 18.04, I noticed that certain keyboard shortcuts no longer function. It appears to be related to the shortcuts that gnome-settings-daemon control as my shortcuts that are provided by my desktop (Budgie) still function. Some examples are: * Media keys for volume up/down/mute * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same behaviour. I double checked, and it looks like the needed daemon is still running, ``` dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-power dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sound dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-color dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-printer dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep --color=auto gnome-settings-daemon ``` Reboot does not seem to help. However, occasionally the shortcuts do seem to work - but only very occasionally. Any other info needed? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 27 21:12:18 2018 InstallationDate: Installed on 2018-03-05 (22 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) SourcePackage: gnome-settings-daemon Up
[Desktop-packages] [Bug 1763960] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763960/+attachment/5115437/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763960/+attachment/5115439/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763960/+attachment/5115442/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763960/+attachment/5115443/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763960/+attachment/5115444/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763960/+attachment/5115445/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763960/+attachment/5115446/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763960 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crashes when I launch Slack in an Xorg-session. No crash when running under Wayland or when starting an Ubuntu session (Xorg) as opposed to a vanilla GNOME session. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 16:47:50 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-04-11 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763960/+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 1745866] Re: [nvidia] Audio does not auto-switch to HDMI after switching the connected HDMI TV on
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1745866 Title: [nvidia] Audio does not auto-switch to HDMI after switching the connected HDMI TV on Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I start the computer is the connected TV (HDMI) is off and the pulseaudio device stays on unplugged when I switch the TV on. If I switch the TV on before I start the computer, everything works fine. alsa_output.pci-_01_00.1.hdmi-stereo linux-image-14.0-15-generic nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic Regards, Norbert --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.14.0-15-generic. AplayDevices: aplay: device_list:270: no soundcards found... ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 ArecordDevices: arecord: device_list:270: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-25 (36 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171222) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown] PackageArchitecture: amd64 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: bionic third-party-packages Uname: Linux 4.14.0-15-generic x86_64 UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: H67M-GE/HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1762292] Re: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main)
Nice, thank you all! :-) -- 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/1762292 Title: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main) Status in appstream package in Ubuntu: Fix Released Bug description: Please sync appstream 0.12.0-3 (main) from Debian unstable (main) This introduces a new feature release pretty late in the cycle, so it is something to more carefully consider. Even if it's very late, I do think upgrading this package in Bionic is a good idea though. First of all, it makes upgrading the appstream-generator package to version 0.7.1-3 possible, allowing people to generate much better and smaller metadata for Debian and Ubuntu repositories (and this is what sparked the creation of this sync request). But there are also many other good reasons. This is the NEWS file for the new release, with explanations on why we want the respective changes (I shuffled some entries around to form logical groups) : Version 0.12.0 ~~ Released: 2018-04-04 Features: * Implement release types * qt: Support release types This adds a new feature to the AppStream specification and libappstream that allows release metadata to be tagged as "development" or "stable" releases. Nothing in Ubuntu uses this, so adding will not break anything, but having this in the LTS release means upstream projects can use this feature more easily, and Ubuntu will understand metadata containing it. * Update static data lists * spdx: Add some compatibility workarounds for SPDX 3.0 * validator: Validate SPDX license expressions for metadata_license This updates the SPDX[1] license lists to version 3.0 and adds some compatibility glue to libappstream to parse the new license strings introduced in SPDX 3.0. This is very useful to have, because many projects will start using the new identifier, and it makes sense for AppStream in Ubuntu to be ready for that. Furthermore, it prevents errors from people using the new IDs with older AppStream versions (unfortunately, SPDX 3.0 broke the format, AppStream speaks all flavors of SPDX now, though) [1]: https://spdx.org/licenses/ * apt: Add config snippets to enable icon downloads This results in an easy way for users as well as software centers to enable the download of application icon tarballs via APT just by installing a sepecific package (apt-icons-*). This is quite neat to make icon downloads configurable easily, and also have a central place for the APT configuration. The new packages are used in Debian already by GNOME Software and Plasma Dicover. All existing solutions to enable icons work though, this is an optional change. * Implement support for requires/recommends * Add recommends/requires data to the cache * Add a quick way to check if a version satisfies an AsRelation requirement * yaml: Make Requires/Recommends data more compact and easier to emit * Default to format version 0.12 * validator: Validate requires/recommends tags This adds a new feature to allow AppStream components to require other components or system resources (e.g. minimal memory sizes). Nothing uses this yet, due to that this feature also can't break anything. Having it in the LTS means that upstream projects can already add the metadata easily though and have it validated. * ascli: Properly document the --no-net flag * ascli: Allow to disable network access via an environment variable This is useful in a package build environment where AppStream metadata is validated and the distributor wants to make sure appstreamcli doesn't try to access the network without changing upstream's code and passing the --no-net flag explicitly somewhere. Nice feature to have, no risk potential to break existing code. * Make as_str_replace use as_gstring_replace internally * yaml: Ensure all string values have whitespaces stripped * Make as_component_get_launchables public API * apt: Support 48x48px icons This are miscellaneous improvements which should not cause any issue at all. The 48x48px icons are used in some software centers, having them can be useful (this was a feature requested by Elementary, so chances are they will use these icons at some point). Specification: * spec: Add a "type" property to tag * spec: Initial draft for requires/recommends * spec: Document the YAML Rquires/Recommends fields * spec: Clarify that the memory requirement uses MiB as unit This improve the AppStream specification or extend it. It's just documentation changes. Bugfixes: * qt: Implement missing constructors This fixes some nasty crashes in Qt applications using AppStream, like Plasma Discover. * apt: escape the icon scale factor as it is using the arobase character This fixes a bug which basically ren
[Desktop-packages] [Bug 1579142] Re: Evince windows cannot be resized after upgrade to Xenial
I am experiencing this on Ubuntu 18.04 with evince 3.28.2-1. A possible regression? -- 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/1579142 Title: Evince windows cannot be resized after upgrade to Xenial Status in gnome-shell package in Ubuntu: Fix Released Bug description: Since upgrade to Xenial, windows of evince cannot be resized on my machine. Windows can be maximized and restored, but windows cannot be resized with the mouse to arbitrary width and height. Works fine for windows of other applications. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-58.64~14.04.1-generic 3.19.8-ckt16 Uname: Linux 3.19.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 6 18:27:55 2016 InstallationDate: Installed on 2015-11-05 (183 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1579142/+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 1762292] Re: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main)
** No longer affects: gnome-software (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/1762292 Title: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main) Status in appstream package in Ubuntu: Fix Released Bug description: Please sync appstream 0.12.0-3 (main) from Debian unstable (main) This introduces a new feature release pretty late in the cycle, so it is something to more carefully consider. Even if it's very late, I do think upgrading this package in Bionic is a good idea though. First of all, it makes upgrading the appstream-generator package to version 0.7.1-3 possible, allowing people to generate much better and smaller metadata for Debian and Ubuntu repositories (and this is what sparked the creation of this sync request). But there are also many other good reasons. This is the NEWS file for the new release, with explanations on why we want the respective changes (I shuffled some entries around to form logical groups) : Version 0.12.0 ~~ Released: 2018-04-04 Features: * Implement release types * qt: Support release types This adds a new feature to the AppStream specification and libappstream that allows release metadata to be tagged as "development" or "stable" releases. Nothing in Ubuntu uses this, so adding will not break anything, but having this in the LTS release means upstream projects can use this feature more easily, and Ubuntu will understand metadata containing it. * Update static data lists * spdx: Add some compatibility workarounds for SPDX 3.0 * validator: Validate SPDX license expressions for metadata_license This updates the SPDX[1] license lists to version 3.0 and adds some compatibility glue to libappstream to parse the new license strings introduced in SPDX 3.0. This is very useful to have, because many projects will start using the new identifier, and it makes sense for AppStream in Ubuntu to be ready for that. Furthermore, it prevents errors from people using the new IDs with older AppStream versions (unfortunately, SPDX 3.0 broke the format, AppStream speaks all flavors of SPDX now, though) [1]: https://spdx.org/licenses/ * apt: Add config snippets to enable icon downloads This results in an easy way for users as well as software centers to enable the download of application icon tarballs via APT just by installing a sepecific package (apt-icons-*). This is quite neat to make icon downloads configurable easily, and also have a central place for the APT configuration. The new packages are used in Debian already by GNOME Software and Plasma Dicover. All existing solutions to enable icons work though, this is an optional change. * Implement support for requires/recommends * Add recommends/requires data to the cache * Add a quick way to check if a version satisfies an AsRelation requirement * yaml: Make Requires/Recommends data more compact and easier to emit * Default to format version 0.12 * validator: Validate requires/recommends tags This adds a new feature to allow AppStream components to require other components or system resources (e.g. minimal memory sizes). Nothing uses this yet, due to that this feature also can't break anything. Having it in the LTS means that upstream projects can already add the metadata easily though and have it validated. * ascli: Properly document the --no-net flag * ascli: Allow to disable network access via an environment variable This is useful in a package build environment where AppStream metadata is validated and the distributor wants to make sure appstreamcli doesn't try to access the network without changing upstream's code and passing the --no-net flag explicitly somewhere. Nice feature to have, no risk potential to break existing code. * Make as_str_replace use as_gstring_replace internally * yaml: Ensure all string values have whitespaces stripped * Make as_component_get_launchables public API * apt: Support 48x48px icons This are miscellaneous improvements which should not cause any issue at all. The 48x48px icons are used in some software centers, having them can be useful (this was a feature requested by Elementary, so chances are they will use these icons at some point). Specification: * spec: Add a "type" property to tag * spec: Initial draft for requires/recommends * spec: Document the YAML Rquires/Recommends fields * spec: Clarify that the memory requirement uses MiB as unit This improve the AppStream specification or extend it. It's just documentation changes. Bugfixes: * qt: Implement missing constructors This fixes some nasty crashes in Qt applications using AppStream, like Plasma Discover. * apt: escape the icon scale factor as it is using the arobase character This fixes a bu
[Desktop-packages] [Bug 1758467] Re: Update yelp* to 3.28.0
** Changed in: yelp (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp-xsl in Ubuntu. https://bugs.launchpad.net/bugs/1758467 Title: Update yelp* to 3.28.0 Status in yelp package in Ubuntu: Triaged Status in yelp-tools package in Ubuntu: Triaged Status in yelp-xsl package in Ubuntu: Triaged Bug description: The Ubuntu Docs team requested that the new versions of yelp* stuff not be updated to the 3.28 versions for Ubuntu 18.04 LTS. The new versions have changes that will require rewriting of the rules used to generate the html documentation for https://help.ubuntu.com/stable /ubuntu-help/ The desktop app yelp should have no compatibility problems. Even if it takes some time to update those html rules, Ubuntu 18.04 LTS can be used for a while to update the web site. It just would be annoying to be stuck on 16.04 LTS for a while instead! Therefore, I'm filing this tracking bug and setting the block-proposed tag in case someone accidentally syncs the packages even though we're in Freeze status for Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1758467/+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 1763111] Re: autokey starting maximized (not in system tray)
This is a Bionic Beaver bug: I don't know how to tell you... -- 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/1763111 Title: autokey starting maximized (not in system tray) Status in xorg package in Ubuntu: New Bug description: It's so in Kubuntu 18.04 (beta final): autokey (auto)start as window, not, as expected (and as in Kubuntu 17.10) as system tray icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763111/+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 1754458] Re: nm-applet symbol not displayed on mate (18.04)
FYI: please don't run graphical programs with plain `sudo`, see https://askubuntu.com/a/270019/549800 -- 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/1754458 Title: nm-applet symbol not displayed on mate (18.04) Status in ubuntu-mate: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 18.04, the network manager applet symbol isn't displayed any longer. The other functionality (asking for credentials) is working. I also see other symbols. aptitude show network-manager-gnome Paket: network-manager-gnome Version: 1.8.10-2ubuntu1 Neu: ja Zustand: Installiert stdout/stderr: Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module" ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab information for modem at /org/freedesktop/ModemManager1/Modem/6: No ModemManager support (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is not available for modem at /org/freedesktop/ModemManager1/Modem/6 (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on widget which has a parent ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: MATE Date: Thu Mar 8 21:27:56 2018 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) WpaSupplicantLog: nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1754458/+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 1758467] Re: Update yelp* to 3.28.0
** Changed in: yelp (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp-xsl in Ubuntu. https://bugs.launchpad.net/bugs/1758467 Title: Update yelp* to 3.28.0 Status in yelp package in Ubuntu: Fix Released Status in yelp-tools package in Ubuntu: Triaged Status in yelp-xsl package in Ubuntu: Triaged Bug description: The Ubuntu Docs team requested that the new versions of yelp* stuff not be updated to the 3.28 versions for Ubuntu 18.04 LTS. The new versions have changes that will require rewriting of the rules used to generate the html documentation for https://help.ubuntu.com/stable /ubuntu-help/ The desktop app yelp should have no compatibility problems. Even if it takes some time to update those html rules, Ubuntu 18.04 LTS can be used for a while to update the web site. It just would be annoying to be stuck on 16.04 LTS for a while instead! Therefore, I'm filing this tracking bug and setting the block-proposed tag in case someone accidentally syncs the packages even though we're in Freeze status for Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1758467/+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 1763924] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
*** This bug is a duplicate of bug 1762827 *** https://bugs.launchpad.net/bugs/1762827 ** This bug has been marked a duplicate of bug 1762827 package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 -- 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/1763924 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: while installing wine in the end i got this Errors were encountered while processing: /tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Im using Lubantu 17.10 x64 1 gb RAM Intel Pentium 4-2 core 3.20 MHz 3.20 MHz ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sat Apr 14 13:04:05 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-10 (34 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1763924/+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 1340076] Re: HDMI audio is severely distorted.
** Tags added: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1340076 Title: HDMI audio is severely distorted. Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have recently installed Ubuntu onto a newly built computer with an ASRock H87 Performance Motherboard. I am using a TV monitor for a screen, connected with HDMI. The visuals work fine but the audio is severely distorted and echoes. When testing the sound in the hardware settings, it sounds like "FRONTFRONTFRONTFRONT" with static or overdrive getting more and more prominent as the sound goes on. I have changed the Alsamixer levels but found no change. The built-in sound card also shows up when i look for it as per the Sound Troubleshooting page. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: snd_hda_codec_generic snd_hda_controller fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 2371 F pulseaudio /dev/snd/controlC1: luke 2371 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 10 17:52:52 2014 InstallationDate: Installed on 2014-07-09 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [To Be Filled By O.E.M., ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: H87 Performance dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd05/06/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1340076/+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 1754445] Re: gnome-shell crashed with SIGSEGV in cogl_object_unref() from iter_remove_or_steal() from g_hash_table_iter_remove() from st_texture_cache_evict_icons() from on_ico
My bug #1763850 got marked as a dupplicate (and probably is). It's seems to only occur once after a fresh install on my system. I tried to reproduced and succeeded. What I did was: a fresh install with encrypted drive, login to regular "ubuntu"-session, update all software, reboot, login to "ubuntu wayland"-session -> image freezes -> thrown-back to login screen, login to regular "ubuntu"-session, do things for a few minutes (I was surfing with firefox both times) -> crash report appears on-screen. -- 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/1754445 Title: gnome-shell crashed with SIGSEGV in cogl_object_unref() from iter_remove_or_steal() from g_hash_table_iter_remove() from st_texture_cache_evict_icons() from on_icon_theme_changed() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/990288ee13e03a048791700aa0af1ccfaecd49bc https://errors.ubuntu.com/problem/e4d313a6d362e991dc79947946d24a22a3a2f84a --- i don´t know ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Mar 8 20:18:43 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f921c91b510 :mov (%rdi),%rax PC (0x7f921c91b510) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: cogl_object_unref () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in cogl_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754445/+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 1763940] [NEW] Pressing Print Screen in keyboard makes Rhythmbox go to sleep
Public bug reported: Steps: 1. Start Rhythmbox and play music 2. Press Print Screen in keyboard 3. Music stops and cannot be played again in Rhythmbox 4. If the music does not stop from the first time try step 2 again and again until it stops I can navigate the UI of Rhythmbox, but I cannot play music. I have to kill the sleeping process in order to play music. I can reproduce this bug in Totem and Clementine too. Clementine and Totem present this error: pa_stream_writable_size() failed: Connection terminated This bug affects Bionic too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr9438 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 14 14:42:55 2018 InstallationDate: Installed on 2017-06-21 (296 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08 mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1763940 Title: Pressing Print Screen in keyboard makes Rhythmbox go to sleep Status in pulseaudio package in Ubuntu: New Bug description: Steps: 1. Start Rhythmbox and play music 2. Press Print Screen in keyboard 3. Music stops and cannot be played again in Rhythmbox 4. If the music does not stop from the first time try step 2 again and again until it stops I can navigate the UI of Rhythmbox, but I cannot play music. I have to kill the sleeping process in order to play music. I can reproduce this bug in Totem and Clementine too. Clementine and Totem present this error: pa_stream_writable_size() failed: Connection terminated This bug affects Bionic too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr9438 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 14 14:42:55 2018 InstallationDate: Installed on 2017-06-21 (296 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08 mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1763940/+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 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings
I am also confirming that the issue is fixed. Thanks! -- 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/1758306 Title: Cannot switch mouse primary button to Right (left-handed) in Settings Status in gnome-control-center package in Ubuntu: Fix Released Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured for left handed use. That is the mouse primary button being switched to the right. GCC doesn't seem to work for this now. I don't know if it's related to evdev or what. Held back reporting this in case it was fixed by changes overnight. Updated this morning and problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13 Uname: Linux 4.13.0-36201803011620-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 23 07:07:02 2018 InstallationDate: Installed on 2018-01-19 (62 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+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 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2
The solution would be to just set the binary to be installed in the install file. Independent from the decision of deb multimedia. Workable solution with the least amount of effort. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1750264 Title: program 'cd-paranoia' is missing from package in 1.0.0-2 Status in libcdio package in Ubuntu: Invalid Status in libcdio-paranoia package in Ubuntu: Confirmed Bug description: apt show libcdio-utils: Description: sample applications based on the CDIO libraries This package contains a collection of small libcdio-based tools: * cd-drive show CD-ROM drive characteristics * cd-info show information about a CD or CD-image * cd-paranoia an audio CD ripper * cd-read read information from a CD or CD-image * cdda-player a simple curses-based audio CD player * iso-info show information about an ISO 9660 image * iso-read read portions of an ISO 9660 image * mmc-tool issue low-level commands to a CD drive cd-paranoia is missing from package. This breaks abcde 'optional' functionality which is in fact the most common used, since the original cdparanoia (separate program) is abandoned since 10 years. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 libcdio-utils: Installiert: 1.0.0-2 Installationskandidat: 1.0.0-2 Versionstabelle: *** 1.0.0-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcdio-utils 1.0.0-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Feb 18 18:18:55 2018 ProcEnviron: TERM=qterminal PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libcdio UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+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 569994] Re: eject hotkey fails to eject cd
** Changed in: gnome-settings-daemon Status: New => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/569994 Title: eject hotkey fails to eject cd Status in GNOME Settings Daemon: Expired Status in gvfs package in Ubuntu: Triaged Bug description: Dell E1505 inspiron laptop. Fn-F10 hotkey combo ejects cd/dvd tray on jaunty and earlier versions of gnome, but fails on lucid gnome. When I hit Fn-F10, the eject on-screen-display icon appears, but the cd does not open. I've checked the tray on another OS and it works with that key combo, so it's not a hardware problem. The output from xev when I press Fn-F10 is: MappingNotify event, serial 36, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 FocusOut event, serial 36, synthetic NO, window 0x5c1, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 36, synthetic NO, window 0x5c1, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 36, synthetic NO, window 0x0, keys: 4294967213 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The fact that the eject on-screen-display icon pops up makes me think this has nothing to do with failure to recognize the key input, and more likely relates to how gnome processes the XF86Eject command. For example, if I install xdotool and enter 'xdotool key XF86Eject' in a console, I see the same result. The o-s-d icon appears, but the cd/dvd fails to open. Entering 'eject' in the console results in the cd/dvd opening. Not sure what else you need, but let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/569994/+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 1756871] Re: Please remove libxfont1 from Ubuntu
** Changed in: libxfont1 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxfont1 in Ubuntu. https://bugs.launchpad.net/bugs/1756871 Title: Please remove libxfont1 from Ubuntu Status in libxfont1 package in Ubuntu: Fix Released Bug description: libxfont1 has no reverse dependencies any more. Please remove it from Ubuntu bionic. $ reverse-depends src:libxfont1 No reverse dependencies found $ reverse-depends -b src:libxfont1 No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont1/+bug/1756871/+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 1760192] Re: Update gnome-screenshot to version 3.26
There is a Unity patch that is making the update a bit more complicated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1760192 Title: Update gnome-screenshot to version 3.26 Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: bionic and artful still have gnome-screenshot 3.25. Please update to 3.26 https://git.gnome.org/browse/gnome-screenshot/tree/NEWS GNOME Screenshot 3.26.0 - 30th October 2017 === - #787214 - App menu placed below header bar when Application Menu on the top panel of GNOME Shell is disabled [Cosimo Cecchi] - #765941 - Add backbutton after screenshot [Daniel Byrne] - #783442 - Cannot build gnome-screenshot with meson on FreeBSD because of -D_POSIX_C_SOURCE [Ting-Wei Lan] - Translation updates: Friulan, Indonesian, German, Esperanto, Kazakh, Spanish, Slovenian, Croatian, Czech, Hungarian, Swedish, Polish, Galician, Turkish, Serbian, Finnish, Nepali, French, Lithuanian, Danish, Chinese (Taiwan), Latvian, Italian, Belarusian, Bulgarian, Slovak, Korean, Brazilian Portuguese, Basque, Dutch, Greek, Catalan, Icelandic, Persian, Catalan (Valencian), Chinese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1760192/+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 1763931] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1754924 *** https://bugs.launchpad.net/bugs/1754924 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754924, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763931/+attachment/5115239/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763931/+attachment/5115241/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763931/+attachment/5115245/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763931/+attachment/5115246/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763931/+attachment/5115247/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763931/+attachment/5115248/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763931/+attachment/5115249/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1754924 gnome-control-center crashed with SIGSEGV in actualize_printers_list() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1763931 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu 18.04 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 14:04:28 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-03-08 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x55b016638311:mov0x90(%rbp),%rsi PC (0x55b016638311) ok source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1763931/+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 1760192] Re: Update gnome-screenshot to version 3.26
** Description changed: bionic and artful still have gnome-screenshot 3.25. Please update to 3.26 + + https://git.gnome.org/browse/gnome-screenshot/tree/NEWS + + GNOME Screenshot 3.26.0 - 30th October 2017 + === + + - #787214 - App menu placed below header bar when Application Menu on the + top panel of GNOME Shell is disabled [Cosimo Cecchi] + - #765941 - Add backbutton after screenshot [Daniel Byrne] + - #783442 - Cannot build gnome-screenshot with meson on FreeBSD + because of -D_POSIX_C_SOURCE [Ting-Wei Lan] + - Translation updates: + Friulan, Indonesian, German, Esperanto, Kazakh, Spanish, Slovenian, + Croatian, Czech, Hungarian, Swedish, Polish, Galician, Turkish, + Serbian, Finnish, Nepali, French, Lithuanian, Danish, Chinese (Taiwan), + Latvian, Italian, Belarusian, Bulgarian, Slovak, Korean, Brazilian + Portuguese, Basque, Dutch, Greek, Catalan, Icelandic, Persian, + Catalan (Valencian), Chinese -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1760192 Title: Update gnome-screenshot to version 3.26 Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: bionic and artful still have gnome-screenshot 3.25. Please update to 3.26 https://git.gnome.org/browse/gnome-screenshot/tree/NEWS GNOME Screenshot 3.26.0 - 30th October 2017 === - #787214 - App menu placed below header bar when Application Menu on the top panel of GNOME Shell is disabled [Cosimo Cecchi] - #765941 - Add backbutton after screenshot [Daniel Byrne] - #783442 - Cannot build gnome-screenshot with meson on FreeBSD because of -D_POSIX_C_SOURCE [Ting-Wei Lan] - Translation updates: Friulan, Indonesian, German, Esperanto, Kazakh, Spanish, Slovenian, Croatian, Czech, Hungarian, Swedish, Polish, Galician, Turkish, Serbian, Finnish, Nepali, French, Lithuanian, Danish, Chinese (Taiwan), Latvian, Italian, Belarusian, Bulgarian, Slovak, Korean, Brazilian Portuguese, Basque, Dutch, Greek, Catalan, Icelandic, Persian, Catalan (Valencian), Chinese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1760192/+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 1725604] Re: gnome-control-center crashed with SIGSEGV in net_device_get_find_connection()
After some network manager updates, my connection DSL/PPPoE is not being recognized correctly. Before: https://i.imgur.com/RUoXqYX.png After: https://i.imgur.com/w7lNq4E.png -- 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/1725604 Title: gnome-control-center crashed with SIGSEGV in net_device_get_find_connection() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Occurred when trying to turn on Mobile broadband connection. I think this is the first of these kind of bug reported in Ubuntu 17.10. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 13:50:45 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-09 (12 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center network SegvAnalysis: Segfault happened at: 0x55dd0bf3ed13 : jmpq *0xb8(%rax) PC (0x55dd0bf3ed13) ok source "*0xb8(%rax)" ok SP (0x7ffed7f73968) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-control-center StacktraceTop: net_device_get_find_connection () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in net_device_get_find_connection() UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725604/+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 1760192] Re: Update gnome-screenshot to version 3.26
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screenshot (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1760192 Title: Update gnome-screenshot to version 3.26 Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: bionic and artful still have gnome-screenshot 3.25. Please update to 3.26 https://git.gnome.org/browse/gnome-screenshot/tree/NEWS GNOME Screenshot 3.26.0 - 30th October 2017 === - #787214 - App menu placed below header bar when Application Menu on the top panel of GNOME Shell is disabled [Cosimo Cecchi] - #765941 - Add backbutton after screenshot [Daniel Byrne] - #783442 - Cannot build gnome-screenshot with meson on FreeBSD because of -D_POSIX_C_SOURCE [Ting-Wei Lan] - Translation updates: Friulan, Indonesian, German, Esperanto, Kazakh, Spanish, Slovenian, Croatian, Czech, Hungarian, Swedish, Polish, Galician, Turkish, Serbian, Finnish, Nepali, French, Lithuanian, Danish, Chinese (Taiwan), Latvian, Italian, Belarusian, Bulgarian, Slovak, Korean, Brazilian Portuguese, Basque, Dutch, Greek, Catalan, Icelandic, Persian, Catalan (Valencian), Chinese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1760192/+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 1763924] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
** Tags removed: need-duplicate-check -- 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/1763924 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: while installing wine in the end i got this Errors were encountered while processing: /tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Im using Lubantu 17.10 x64 1 gb RAM Intel Pentium 4-2 core 3.20 MHz 3.20 MHz ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sat Apr 14 13:04:05 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-10 (34 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1763924/+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 1763924] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o
Public bug reported: while installing wine in the end i got this Errors were encountered while processing: /tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Im using Lubantu 17.10 x64 1 gb RAM Intel Pentium 4-2 core 3.20 MHz 3.20 MHz ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sat Apr 14 13:04:05 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-10 (34 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-conflict -- 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/1763924 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: while installing wine in the end i got this Errors were encountered while processing: /tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Im using Lubantu 17.10 x64 1 gb RAM Intel Pentium 4-2 core 3.20 MHz 3.20 MHz ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sat Apr 14 13:04:05 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-10 (34 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1763924/+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 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings
Confirm that as of Saturday April 14/18 update: the issue is resolved for me. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released -- 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/1758306 Title: Cannot switch mouse primary button to Right (left-handed) in Settings Status in gnome-control-center package in Ubuntu: Fix Released Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured for left handed use. That is the mouse primary button being switched to the right. GCC doesn't seem to work for this now. I don't know if it's related to evdev or what. Held back reporting this in case it was fixed by changes overnight. Updated this morning and problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13 Uname: Linux 4.13.0-36201803011620-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 23 07:07:02 2018 InstallationDate: Installed on 2018-01-19 (62 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+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 1763918] StacktraceTop.txt
** Attachment added: "StacktraceTop.txt" https://bugs.launchpad.net/bugs/1763918/+attachment/5115195/+files/StacktraceTop.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1763918 Title: Xorg crashed with SIGSEGV in GetBarrierDevice() Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: i work in gedit...! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-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-15ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sat Apr 14 14:37:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed nvidia, 390.48, 4.15.0-15-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd] InstallationDate: Installed on 2017-09-02 (224 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x5650239f51fc:cmp0x10(%rax),%esi PC (0x5650239f51fc) ok source "0x10(%rax)" (0x1022af410) not located in a known VMA region (needed readable region)! destination "%esi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nvidia-graphics-drivers StacktraceTop: ?? () miPointerSetPosition () ?? () ?? () GetPointerEvents () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x: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 version.compiz: compiz N/A 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-1ubuntu3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1763918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.ne
[Desktop-packages] [Bug 1763918] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763918/+attachment/5115194/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1763918 Title: Xorg crashed with SIGSEGV in GetBarrierDevice() Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: i work in gedit...! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-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-15ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sat Apr 14 14:37:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed nvidia, 390.48, 4.15.0-15-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd] InstallationDate: Installed on 2017-09-02 (224 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x5650239f51fc:cmp0x10(%rax),%esi PC (0x5650239f51fc) ok source "0x10(%rax)" (0x1022af410) not located in a known VMA region (needed readable region)! destination "%esi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nvidia-graphics-drivers StacktraceTop: ?? () miPointerSetPosition () ?? () ?? () GetPointerEvents () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x: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 version.compiz: compiz N/A 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-1ubuntu3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1763918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~des
[Desktop-packages] [Bug 1763918] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763918/+attachment/5115196/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763918/+attachment/5115107/+files/CoreDump.gz ** Changed in: nvidia-graphics-drivers (Ubuntu) Importance: Undecided => Medium ** Summary changed: - Xorg crashed with SIGSEGV in miPointerSetPosition() + Xorg crashed with SIGSEGV in GetBarrierDevice() ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1763918 Title: Xorg crashed with SIGSEGV in GetBarrierDevice() Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: i work in gedit...! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-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-15ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sat Apr 14 14:37:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed nvidia, 390.48, 4.15.0-15-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd] InstallationDate: Installed on 2017-09-02 (224 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x5650239f51fc:cmp0x10(%rax),%esi PC (0x5650239f51fc) ok source "0x10(%rax)" (0x1022af410) not located in a known VMA region (needed readable region)! destination "%esi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nvidia-graphics-drivers StacktraceTop: ?? () miPointerSetPosition () ?? () ?? () GetPointerEvents () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x: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 version.compiz: compiz N/A 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-1ubuntu3 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+g
[Desktop-packages] [Bug 1763919] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763919/+attachment/5115132/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763919/+attachment/5115134/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763919/+attachment/5115137/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763919/+attachment/5115138/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763919/+attachment/5115139/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763919/+attachment/5115140/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763919/+attachment/5115141/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763919 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: This error popped up automatically after I logged in ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 11:20:36 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-04-10 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763919/+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 1763920] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763920/+attachment/5115145/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763920/+attachment/5115147/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763920/+attachment/5115151/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763920/+attachment/5115152/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763920/+attachment/5115153/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763920/+attachment/5115154/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763920/+attachment/5115155/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763920 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: occurs realoading after suspension ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 12:38:24 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-06-04 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763920/+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 1763918] [NEW] Xorg crashed with SIGSEGV in miPointerSetPosition()
Public bug reported: i work in gedit...! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-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-15ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sat Apr 14 14:37:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed nvidia, 390.48, 4.15.0-15-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd] InstallationDate: Installed on 2017-09-02 (224 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x5650239f51fc: cmp0x10(%rax),%esi PC (0x5650239f51fc) ok source "0x10(%rax)" (0x1022af410) not located in a known VMA region (needed readable region)! destination "%esi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nvidia-graphics-drivers StacktraceTop: ?? () miPointerSetPosition () ?? () ?? () GetPointerEvents () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x: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 version.compiz: compiz N/A 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-1ubuntu3 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: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ubuntu ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1763918 Title: Xorg crashed with SIGSEGV in miPointerSetPosition() Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: i work in gedit...! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvi
[Desktop-packages] [Bug 1763913] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763913/+attachment/5115053/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763913/+attachment/5115055/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763913/+attachment/5115058/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763913/+attachment/5115059/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763913/+attachment/5115060/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763913/+attachment/5115061/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763913/+attachment/5115062/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763913 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: I just install exfat-fuse and exfat-utils, don't know if that was the cause ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 10:39:47 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-04-07 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763913/+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 1763912] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763912/+attachment/5115043/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763912/+attachment/5115045/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763912/+attachment/5115048/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763912/+attachment/5115049/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763912/+attachment/5115050/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763912/+attachment/5115051/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763912/+attachment/5115052/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763912 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: i got idea why this happen after boot up ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 14:38:36 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-04-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763912/+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 1757208] Re: udisksd crashed with SIGSEGV in udisks_linux_drive_object_get_block()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1757208 Title: udisksd crashed with SIGSEGV in udisks_linux_drive_object_get_block() Status in udisks2 package in Ubuntu: Confirmed Bug description: I unmounted a single USB disk, and all others disappeared off the desktop with it. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udisks2 2.6.5-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Mar 20 16:47:19 2018 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2018-02-13 (35 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Precision Tower 3420 ProcCmdline: /usr/lib/udisks2/udisksd ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x55a0cf0fb92a : mov0x18(%rax),%rdi PC (0x55a0cf0fb92a) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: udisks_linux_drive_object_get_block () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: udisksd crashed with SIGSEGV in udisks_linux_drive_object_get_block() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.name: 08K0X7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn08K0X7:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757208/+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 1763901] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763901/+attachment/5114942/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763901/+attachment/5114944/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763901/+attachment/5114948/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763901/+attachment/5114949/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763901/+attachment/5114950/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763901/+attachment/5114951/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763901/+attachment/5114952/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763901 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: just booted after update ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 13 23:36:44 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-09-02 (588 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) LocalLibraries: /usr/local/lib/libgcrypt.so.20.1.3 /usr/local/lib/libgpg-error.so.0.20.0 ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763901/+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 1763899] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763899/+attachment/5114921/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763899/+attachment/5114923/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763899/+attachment/5114927/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763899/+attachment/5114928/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763899/+attachment/5114929/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763899/+attachment/5114930/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763899/+attachment/5114931/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763899 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashed with signal 5 in g_log_default_handler() ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 10:56:41 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-13 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763899/+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 1763874] Re: Cherry-pick cairo good patch from 0.63 to improve performance
** Changed in: poppler (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1763874 Title: Cherry-pick cairo good patch from 0.63 to improve performance Status in poppler package in Ubuntu: Fix Committed Status in poppler package in Debian: Fix Released Bug description: Bug filed for potential SRU purposes. See Debian bug for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1763874/+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 1763897] Re: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()
*** This bug is a duplicate of bug 1758651 *** https://bugs.launchpad.net/bugs/1758651 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1758651, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763897/+attachment/5114893/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763897/+attachment/5114896/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763897/+attachment/5114904/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763897/+attachment/5114906/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763897/+attachment/5114907/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763897/+attachment/5114908/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763897/+attachment/5114909/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1758651 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1763897 Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent() Status in xorg-server package in Ubuntu: New Bug description: Sorry, I wont be too much help. This error message just popped up. A few minutes before that my computer had a black screen and the ventilation was running at maximum level. I pressed the on/off button for 10 seconds and restarted the system, which went fine. Then this error popped up out of nowhere. I didnt have any additional problems. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 08:31:01 2018 DistUpgraded: 2018-04-02 22:38:13,100 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: broadcom-sta, 6.30.223.271, 4.15.0-13-generic, x86_64: installed broadcom-sta, 6.30.223.271, 4.4.0-116-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00eb] InstallationDate: Installed on 2016-04-22 (721 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookAir4,2 ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=b1921a9c-bdd1-4c11-9d4d-4e676d7b1589 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=1 Renderer: Software Signal: 7 SourcePackage: xorg-server StacktraceTop: mieqProcessDeviceEvent () ?? () ?? () ?? () __libc_start_main (main=0x561da04e8aa0, argc=12, argv=0x7ffe9217a688, init=, fini=, rtld_fini=, stack_end=0x7ffe9217a678) at ../csu/libc-start.c:310 Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent() UpgradeStatus: Upgraded to bionic on 2018-04-02 (11 days ago) UserGroups: dmi.bios.date: 10/26/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B14.1510261805 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B14.1510261805:bd10/26/2015:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
[Desktop-packages] [Bug 1763294] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1754924 *** https://bugs.launchpad.net/bugs/1754924 ** This bug is no longer a duplicate of bug 1763187 gnome-control-center crashed with SIGSEGV in actualize_printers_list() ** This bug has been marked a duplicate of bug 1754924 gnome-control-center crashed with SIGSEGV in actualize_printers_list() -- 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/1763294 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() Status in gnome-control-center package in Ubuntu: New Bug description: same as described ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 04:02:35 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-04-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x558c0eb44311:mov0x90(%rbp),%rsi PC (0x558c0eb44311) ok source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1763294/+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 1756871] Re: Please remove libxfont1 from Ubuntu
** Changed in: libxfont1 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxfont1 in Ubuntu. https://bugs.launchpad.net/bugs/1756871 Title: Please remove libxfont1 from Ubuntu Status in libxfont1 package in Ubuntu: Triaged Bug description: libxfont1 has no reverse dependencies any more. Please remove it from Ubuntu bionic. $ reverse-depends src:libxfont1 No reverse dependencies found $ reverse-depends -b src:libxfont1 No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont1/+bug/1756871/+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