[Touch-packages] [Bug 2047144] [NEW] Black screen stays forever after inactivity
Public bug reported: IMPORTANT this only happens with WAYLAND but i couldn't choose wayland in the bug report options. On my Ubuntu 22.04.03 I have set the time for my screen to go black/shut off in case of inactivity in the energy settings (to save energy) to 5 minutes. So I go back to my computer after 10 minutes or so and the screen is black like it should be. Problem is, that I can't turn the screen on or what I really mean is: get back to the desktop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 21 13:08:29 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CoffeeLake-H GT2 [UHD Graphics 630] [1462:120f] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106M [GeForce GTX 1060 Mobile] [1462:120f] InstallationDate: Installed on 2023-10-22 (59 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS73 Stealth 8RE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=e4b68fb9-8f19-4768-9b90-c84e28ec65ef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2019 dmi.bios.release: 1.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17B5IMS.110 dmi.board.asset.tag: Default string dmi.board.name: MS-17B5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17B5IMS.110:bd05/17/2019:br1.16:svnMicro-StarInternationalCo.,Ltd.:pnGS73Stealth8RE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17B5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17B5.1: dmi.product.family: GS dmi.product.name: GS73 Stealth 8RE dmi.product.sku: 17B5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2047144 Title: Black screen stays forever after inactivity Status in xorg package in Ubuntu: New Bug description: IMPORTANT this only happens with WAYLAND but i couldn't choose wayland in the bug report options. On my Ubuntu 22.04.03 I have set the time for my screen to go black/shut off in case of inactivity in the energy settings (to save energy) to 5 minutes. So I go back to my computer after 10
[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
** Changed in: apport (Ubuntu Xenial) Assignee: (unassigned) => cristian swing (sed1991s) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Won't Fix Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to 'N/A' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964828] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
** Changed in: apport (Ubuntu Focal) Assignee: (unassigned) => cristian swing (sed1991s) ** Changed in: apport (Ubuntu Jammy) Assignee: (unassigned) => cristian swing (sed1991s) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1964828 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: New Status in apport source package in Jammy: Fix Released Bug description: [Impact] If the user reports a bug and rejects to enter the root password for collecting information (like the CasperMD5json), the Ubuntu add_info hook will fail with a stack trace. The remaining code for collecting more information is not executed. So the resulting bug reports will be less helpful. The check_for_disk_error call is not reached and therefore skipped. [Test Plan] 1. Install Ubuntu (e.g. from ubuntu-22.04-desktop-amd64.iso) 2. Open a terminal 3. Run: ubuntu-bug -f 4. Select "installer" and click on OK 5. Click on "abort" when ask for the password 6. The terminal should not show a stacktrace [Where problems could occur] The changed code is the Ubuntu add_info hook. So this hook could fail due to a regression or reveal bugs in the later code path. The later code path could cause more more load on the users machine (but only when the user wants to report the issue). Apport will catch failing add_info hooks and store the failure in the report. [Orinial report] ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperVersion: 1.467 CurrentDesktop: KDE Date: Mon Mar 14 21:22:23 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: systemd (Ubuntu Focal) Status: Invalid => Fix Released ** Changed in: systemd (Ubuntu Jammy) Status: Invalid => Fix Released ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => cristian swing (sed1991s) ** Changed in: systemd (Ubuntu Jammy) Assignee: (unassigned) => cristian swing (sed1991s) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => cristian swing (sed1991s) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<<<<<< ORIGINAL TEXT >>>>>>>>>>>> This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:sv
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: (unassigned) => Cristian (christianmateescu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i3
[Touch-packages] [Bug 1923332] [NEW] I don't know
Public bug reported: I don't know ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 10 23:37:06 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [17aa:3686] InstallationDate: Installed on 2021-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 10150 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=e17409f1-effa-44b2-97fb-f77630566ffd ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2014 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: INKT23AUS dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900059 STD dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: Bx40-LeTV dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrINKT23AUS:bd04/22/2014:br1.23:efr1.23:svnLENOVO:pn10150:pvrLenovoC560:rvnLENOVO:rnINVALID:rvr31900059STD:cvnLENOVO:ct13:cvrBx40-LeTV: dmi.product.family: IdeaCentre dmi.product.name: 10150 dmi.product.sku: LENOVO_MT_1015 dmi.product.version: Lenovo C560 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923332 Title: I don't know Status in xorg package in Ubuntu: New Bug description: I don't know ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 10 23:37:06 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [17aa:3686] InstallationDate: Installed on 2021-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 10150 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=e17409f1-effa-44b2-97fb-f77630566ffd ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2014 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: INKT23AUS dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900059 STD dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: Bx40-LeTV dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrINKT23AUS:bd04/22/2014:br1.23:efr1.23:svnLENOVO:pn10150:pvrLenovoC560:rvnLENOVO:rnINVALID:rvr31900059STD:cvnLENOVO:ct13:cvrBx40-LeTV: dmi.product.family: IdeaCentre dmi.product.name: 10150 dmi.product.sku: LENOVO_MT_1015 dmi.product.version: Lenovo C560 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.91
[Touch-packages] [Bug 1316830] Re: /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak
Is incredible how this is still a thing in 2019 in Ubuntu 18.04 LTS... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1316830 Title: /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak Status in accountsservice package in Ubuntu: Confirmed Bug description: netikras@netikras-netbook ~/received/accountsservice-0.6.20 $ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=16 DISTRIB_CODENAME=petra DISTRIB_DESCRIPTION="Linux Mint 16 Petra" uname -a Linux netikras-netbook 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013 i686 i686 i686 GNU/Linux Nothing. Using my netbook as usual. Did not really notice when this started since earlier today did not feel any significant slowdowns. That's what happened: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 13155 root 20 0 61424 25m 2948 R 99,6 1,3 1:06.01 accounts-daemon netikras@netikras-netbook /tmp $ while :; do ps aux | grep accounts|grep -v grep;echo; sleep 2; done root 13155 93.6 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon root 13155 92.7 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon root 13155 91.9 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon accounts-daemon is using lots o CPU cycles and memory. Stats above are after restarting daemon for several times. Before this memory usage was >60%; CPU - 100%. In file attached you should be able to see there's a loop checking for something repeatedly. Not sure this is the cause though, but feels like it.. It's the first time I've noticed this problem, but I often leave my computer running unattended so I cannot tell if it's really the first time it happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1316830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Any news here? :( If helps, I've also upgraded from Xenial long time ago. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
Looks like my problem was unrelated to this issue, it was actually caused by timidity blocking the physical sound device. This workaround fixed it: https://askubuntu.com/questions/1085174/no- sound-after-upgrade-to-18-10-only-a-dummy-device-is-shown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO 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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
I also noticed this, my laptop's integrated Intel audio device is also missing from pulseaudio(both as input and output), but I can see other HDMI or USB sound devices I may have attached and I can switch to them and they work as expected. Interestingly the device works when playing a WAV file using aplay, but only if I run aplay as root. As a normal user I can just see it in alsamixer and I can play with the volume and mute controls there. Here's the error I get when using aplay as my ordinary user: $ aplay test.wav ALSA lib pcm_dmix.c:1071:(snd_pcm_dmix_open) unable to create IPC semaphore aplay: main:828: audio open error: Permission denied -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO 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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
The lines have been added to: /lib/systemd/system/apport-autoreport.service --- [Unit] [...] Wants=whoopsie.service After=whoopsie.service ** Attachment added: "$ cat /lib/systemd/system/apport-autoreport.service" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5229777/+files/apport-autoreport.service.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
I rebooted the notebook, and reviewed the service: 'systemctl status apport-autoreport.service': ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2019-01-16 19:04:59 -03; 10min ago Process: 2959 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=0/SUCCESS) Main PID: 2959 (code=exited, status=0/SUCCESS) For me, it works well. ** Attachment added: "$ systemctl status apport-autoreport.service" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5229775/+files/systemctl_status_apport-autoreport.service.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
I just updated to apport 2.20.10-0ubuntu19 ** Attachment added: "$ dpkg -l | grep apport" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5229748/+files/dpkg_-l_+_grep_apport.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
** Description changed: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport- autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. - Hello, - - Attached image. - - Regards, - -- - Cristian Aravena Romero (caravena) + ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
Excellent Brian! Thank you for your work! -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: Triaged Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Again I had to go to comment #20 -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Triaged Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
*"I will warn" (avasaré) Sorry (: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Confirmed Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
I removed "After=whoopsie.service" from /lib/systemd/system/apport- autoreport.service and updated apport from ~2.20.10-0ubuntu14 to 2.20.10-0ubuntu18 in Ubuntu Disco. Then I rebooted the computer and reviewed the service "$ systemctl status apport-autoreport.service". And it is working correctly. I do not know if after the update the problem is completely resolved or it will continue to appear randomly. Anything I will avasaré in this report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Confirmed Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811096] Re: gnome-shell[2843]: The offending signal was destroy on StBoxLayout 0x5606a3267650.
** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1811096 Title: gnome-shell[2843]: The offending signal was destroy on StBoxLayout 0x5606a3267650. Status in gnome-shell package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/896 --- Hello, I'm working with vlc and frezze gnome-shell (attached log file). $ journalctl -b-1 ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: == Stack trace for context 0x5606981781b0 == ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #0 7ffde02d1690 I resource:///org/gnome/shell/ui/popupMenu.js:221 (7f116b91dee0 @ 22) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #1 7ffde02d1750 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #2 7ffde02d17d0 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:736 (7f11499c3a60 @ 30) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #3 7ffde02d17d0 I self-hosted:261 (7f116bbc1dc0 @ 223) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #4 7ffde02d17d0 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:734 (7f11499c39d0 @ 37) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #5 7ffde02d18a0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #6 7ffde02d1920 I self-hosted:979 (7f116bbf0280 @ 440) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #7 7ffde02d19a0 I self-hosted:979 (7f116bbf0280 @ 440) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #8 7ffde02d1a30 I resource:///org/gnome/gjs/modules/signals.js:128 (7f116bbc18b0 @ 386) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #9 7ffde02d1a90 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:154 (7f11499beaf0 @ 224) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #10 7ffde02d1b60 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #11 7ffde02d1ba0 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:352 (7f11499c1700 @ 36) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #12 7ffde02d1c70 I self-hosted:261 (7f116bbc1dc0 @ 223) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #13 7ffde02d1c70 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:352 (7f11499c1550 @ 808) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #14 7ffde02d1d40 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #15 7ffde02d1e00 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:305 (7f11499c14c0 @ 274) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #16 7ffde02d1ed0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #17 7ffde02d1f50 I self-hosted:979 (7f116bbf0280 @ 440) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #18 7ffde02d2020 b resource:///org/gnome/gjs/modules/overrides/Gio.js:78 (7f116bbb89d0 @ 113) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.1-2ubuntu3 Uname: Linux 4.20.0-042000-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 9 10:56:00 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['mediapla...@patapon.info', 'ubuntu-d...@ubuntu.com', 'system-moni...@paradoxxx.zero.gmail.com']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' 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 2018-12-02 (37 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-12-02 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Hello Brian Murray (brian-murray), Will this change come in the next version? Best regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806660] Re: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids
** Also affects: alsa-lib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806660 Title: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids Status in Linux: Confirmed Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello, The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids. In the upper part of gnome-shell it appears that they are with the headphones, and it is not like that. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2784 F pulseaudio /dev/snd/pcmC0D0p: caravena 2784 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 07:59:27 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Hello Brad (apeitheo), Your modification helped me (Comment #20). I have restarted twice and the service 'apport-autoreport.service' works correctly for my. Best regards, -- Cristian Aravena Romero (caravena) ** Attachment added: "systemctl_status_apport-autoreport.service.txt" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5220615/+files/systemctl_status_apport-autoreport.service.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806971] [NEW] Condition: start condition failed at Wed 2018-12-05 12:36:10 -03; 1h 57min ag
Public bug reported: Hello, caravena@romanescu:~$ systemctl status apport-autoreport.service ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2018-12-05 12:35:59 -03; 1h 57min ago Condition: start condition failed at Wed 2018-12-05 12:36:10 -03; 1h 57min ago └─ ConditionPathExists=/var/lib/apport/autoreport was not met Main PID: 3817 (code=exited, status=0/SUCCESS) dic 05 12:35:59 romanescu systemd[1]: Starting Process error reports when automatic reporting is enabled... dic 05 12:35:59 romanescu whoopsie-upload-all[3817]: /var/crash/_usr_lib_telepathy_telepathy-idle.1000.crash already marked for upload, skipping dic 05 12:35:59 romanescu whoopsie-upload-all[3817]: /var/crash/_sbin_plymouthd.0.crash already marked for upload, skipping dic 05 12:35:59 romanescu whoopsie-upload-all[3817]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping dic 05 12:35:59 romanescu whoopsie-upload-all[3817]: All reports processed dic 05 12:35:59 romanescu systemd[1]: Started Process error reports when automatic reporting is enabled. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apport 2.20.10-0ubuntu14 Uname: Linux 4.18.20-041820-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 5 14:39:33 2018 InstallationDate: Installed on 2018-12-02 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to disco on 2018-12-02 (2 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1806971 Title: Condition: start condition failed at Wed 2018-12-05 12:36:10 -03; 1h 57min ag Status in apport package in Ubuntu: New Bug description: Hello, caravena@romanescu:~$ systemctl status apport-autoreport.service ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2018-12-05 12:35:59 -03; 1h 57min ago Condition: start condition failed at Wed 2018-12-05 12:36:10 -03; 1h 57min ago └─ ConditionPathExists=/var/lib/apport/autoreport was not met Main PID: 3817 (code=exited, status=0/SUCCESS) dic 05 12:35:59 romanescu systemd[1]: Starting Process error reports when automatic reporting is enabled... dic 05 12:35:59 romanescu whoopsie-upload-all[3817]: /var/crash/_usr_lib_telepathy_telepathy-idle.1000.crash already marked for upload, skipping dic 05 12:35:59 romanescu whoopsie-upload-all[3817]: /var/crash/_sbin_plymouthd.0.crash already marked for upload, skipping dic 05 12:35:59 romanescu whoopsie-upload-all[3817]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping dic 05 12:35:59 romanescu whoopsie-upload-all[3817]: All reports processed dic 05 12:35:59 romanescu systemd[1]: Started Process error reports when automatic reporting is enabled. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apport 2.20.10-0ubuntu14 Uname: Linux 4.18.20-041820-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 5 14:39:33 2018 InstallationDate: Installed on 2018-12-02 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to disco on 2018-12-02 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1806971/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1802700] Re: Cannot install graphic drivers
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1802700 Title: Cannot install graphic drivers Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: i just instal linux 18.04 but the graphic drivers not installed, so my maximum resolution is 360p. I use Lenovo G50-80 with graphic AMR radeon M330 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 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: Sun Nov 11 12:01:41 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 18.20-673703, 4.15.0-29-generic, x86_64: installed amdgpu, 18.20-673703, 4.15.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:390c] Subsystem: Lenovo Radeon R5 M330 [17aa:390c] InstallationDate: Installed on 2018-11-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO INVALID ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=2c4eae76-fae9-48ac-98de-2dfbd276535b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN93WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: NANANANA NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNANANANANODPK:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.version: INVALID dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/linux/+bug/1802700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1802350 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1802350 Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: On a fresh install of ubutu 18.04 all sound work (youtube and system sounds) I connected external hdmi monitor with speakers. I switched audio output to hdmi in settings Then all audio was channeled to external monitor speakers (youtube and system sounds) Then I disconnected external monitor and did not touch the audio output Now only system sounds are working. Youtube in chrome does not work. Audio settings says internal speakers. Firefox youtube has audio normally After reboot same issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 1412 F pulseaudio /dev/snd/controlC1: ed 1412 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 12:28:37 2018 InstallationDate: Installed on 2018-11-01 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11: dmi.product.family: 00 dmi.product.name: Inspiron 5547 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1802366] Re: i dont know
** Changed in: xorg (Ubuntu) Assignee: François ZOLIN (ustas) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1802366 Title: i dont know Status in xorg package in Ubuntu: New Bug description: + i don't speak English+i am not informatics just a user ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 410.73 Sat Oct 20 22:12:33 CDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Nov 8 19:13:59 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 410.73, 4.15.0-39-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-33-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 970M] [1043:22da] InstallationDate: Installed on 2017-12-29 (313 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: ASUSTeK COMPUTER INC. G751JT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=3b41e99c-b074-4029-826b-39ad3587 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G751JT.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G751JT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG751JT.202:bd09/10/2014:svnASUSTeKCOMPUTERINC.:pnG751JT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG751JT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G751JT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 xserver.bootTime: Thu Nov 8 15:34:32 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1802366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Brian, caravena@romanescu:~$ sudo systemctl status whoopsie.service ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2018-11-06 07:33:02 -03; 6h ago Main PID: 1665 (whoopsie) Tasks: 3 (limit: 4915) Memory: 3.1M CGroup: /system.slice/whoopsie.service └─1665 /usr/bin/whoopsie -f nov 06 11:33:26 romanescu whoopsie[1665]: [11:33:26] offline nov 06 11:33:27 romanescu whoopsie[1665]: [11:33:27] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1 nov 06 11:33:27 romanescu whoopsie[1665]: [11:33:27] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1 nov 06 11:33:27 romanescu whoopsie[1665]: [11:33:27] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1 nov 06 11:33:29 romanescu whoopsie[1665]: [11:33:29] online nov 06 12:03:38 romanescu whoopsie[1665]: [12:03:38] offline nov 06 12:03:40 romanescu whoopsie[1665]: [12:03:40] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1 nov 06 12:03:40 romanescu whoopsie[1665]: [12:03:40] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1 nov 06 12:03:40 romanescu whoopsie[1665]: [12:03:40] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1 nov 06 12:03:41 romanescu whoopsie[1665]: [12:03:41] online Best regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
** Attachment added: "sudo systemctl status whoopsie.service" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5209737/+files/sudo_systemctl_status_whoopsie.service.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: I experienced this bug ever since I have upgraded my laptop from 16.04. But it got resolved in my last update after I reported the bug. However, I forgot to go back to Launchpad to mark it as resolved and now the problem comes again after I just updated the system. So, as the title stated, I can't get in the system due to the infinite black screen I am facing. I am only able to report this bug under the recovery mode. Besides, there's something wrong with the lock screen too. I can't get back to the system if I just put the system into "sleep mode". Black screen again! What's worst, the brightness of my display can't be adjusted as well! I feel like being blind at night! Please help!!! Thank you! And I think there might be the compatibility problem between my laptop and the new desktop -- Gnome, which is the default in 18.04. What should do? I really love using Ubuntu, as I really learned a lot in these days I used it as my study os for CS. Any help is appreciated, thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.17.0-041700rc3-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 19:49:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd] InstallationDate: Installed on 2018-04-04 (215 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK COMPUTER INC. T300FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300FA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T300FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Nov 6 03:47:33 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
https://help.ubuntu.com/community/ReportingBugs -- Cristian Aravena Romero (caravena) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 ** This bug has been marked a duplicate of bug 210472 Timidity daemon doesn't play nice with pulse audio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1801540 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801264] Re: Wifi drops out 1-30 minutes after boot on Ubuntu 18.10
Please reproduce the problem, do a hard reset and then run this command: journalctl -b-1 > prev_boot.txt and send us the resulting file prev_boot.txt ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1801264 Title: Wifi drops out 1-30 minutes after boot on Ubuntu 18.10 Status in network-manager package in Ubuntu: Incomplete Bug description: I will boot, Wifi connects fine, and then the wifi drops out and no connection can be made until a restart. When I try to reconnect it "Connection Failed: Activation of network connection failed". The Wifi works fine on phone and on Fedora 29. Network Manager 1.12.4 Expected: Wifi stays connected Happened: Wifi drops out after 1-30 minutes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 13:38:42 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s20f0u2 ethernet connected /org/freedesktop/NetworkManager/Devices/3 Wired connection 1 a79e5d9a-26c0-34c5-a20d-5a371d0eafd6 /org/freedesktop/NetworkManager/ActiveConnection/9 wlp1s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1801264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801202] Re: Xorg freeze
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Description changed: The screen freezes suddenly when i'm trying to play an online video or when i have too many tabs or folders open. + + --- + + CurrentDmesg.txt: + [ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0 + [ 5465.753954] ata1.00: irq_stat 0x4008 + [ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED + [ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma 131072 in + res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409 (media error) + [ 5465.753973] ata1.00: status: { DRDY ERR } + [ 5465.753976] ata1.00: error: { UNC } + [ 5466.031887] ata1.00: configured for UDMA/133 + [ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE + [ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current] + [ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error - auto reallocate failed + [ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01 00 00 + [ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120 + [ 5466.031994] ata1: EH complete + + --- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 01:04:22 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-36-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b] Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b] InstallationDate: Installed on 2018-10-04 (28 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80QQ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E0CN63WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Nano 5B6 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 100-15IBD dmi.modalias: dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD: dmi.product.family: IDEAPAD dmi.product.name: 80QQ dmi.product.version: Lenovo ideapad 100-15IBD dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1801202 Title: Xorg freeze Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description
[Touch-packages] [Bug 1801181] Re: Pixelized display
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1801181 Title: Pixelized display Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts --- CurrentDmesg.txt: [ 29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [ 30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2087A37 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T500 dmi.product.name: 2087A37 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 20:57:30 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801172] Re: Network Manager fails to require VPN
Please reproduce the problem, do a hard reset and then run this command: journalctl -b-1 > prev_boot.txt and send us the resulting file prev_boot.txt ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1801172 Title: Network Manager fails to require VPN Status in network-manager package in Ubuntu: Incomplete Bug description: In Network Manager you can require that the local network requires a particular VPN connection. This works without issue, when networking is enabled, VPN connects automatically. But should there be any service interruption, Network Manager will reconnect using the local network and then exposing the real IP address. This issue only started to occur in 18.04 using GNome desktop environment. This was not an issue in 16.04 using GNome or Unity. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 16:16:08 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 100 IwConfig: enp0s3no wireless extensions. lono wireless extensions. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f ethernet 1541106764 Thu 01 Nov 2018 04:12:44 PM CDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s3 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1801172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801181] Re: Pixelized display
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Description changed: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts + + --- + + CurrentDmesg.txt: + [ 29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid + [ 29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! + [ 30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid + [ 30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! + + -- + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: - bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed - bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed + bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed + bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: - Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] - Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) -Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] + Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] + Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) + Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2087A37 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T500 dmi.product.name: 2087A37 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 20:57:30 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 ** Also affects: linux (Ubuntu) Importance: Undecided St
[Touch-packages] [Bug 1801172] Re: Network Manager fails to require VPN
Your system is updated/upgrade? -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1801172 Title: Network Manager fails to require VPN Status in network-manager package in Ubuntu: Incomplete Bug description: In Network Manager you can require that the local network requires a particular VPN connection. This works without issue, when networking is enabled, VPN connects automatically. But should there be any service interruption, Network Manager will reconnect using the local network and then exposing the real IP address. This issue only started to occur in 18.04 using GNome desktop environment. This was not an issue in 16.04 using GNome or Unity. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 16:16:08 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 100 IwConfig: enp0s3no wireless extensions. lono wireless extensions. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f ethernet 1541106764 Thu 01 Nov 2018 04:12:44 PM CDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s3 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1801172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800555] Re: Computer slow. Error reports appear.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800555 Title: Computer slow. Error reports appear. Status in xorg-server package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot process finishes up... CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 29 17:37:27 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (778 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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 Oct 29 17:32:25 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 inputLogitech USB Optical Mouse MOUSE, id 10 xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800963] Re: Changing Primary DIsplay Flips Which Display Has The Dock
This bug is missing log files that will aid in diagnosing the problem. Please enter the following command in a terminal window: apport-collect 1800963 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. ** Changed in: software-properties (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in software-properties package in Ubuntu: Incomplete Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1800963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1800839 Title: Dualshock3 hid_sony accelerometer not registering as joystick Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25 [12649.015925] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24 [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux perhaps this is only a config issue as when the new split gyro & analog sticks/buttons/triggers both appeared as joysticks while you can now see only Sony PLAYSTATION(R)3 Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 Controller Motion Sensors (input25) does not. Any questions I am happy to respond, I have every reason to believe this is actually not a bluez issue but google gives me no returns other than general compatibility issues over the new hid_sony driver splitting the gyro from the pad. I use this to stay current on instrument flying while working out of town using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator that fis in my laptop bag. thanks dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Wed Oct 31 15:06:00 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. GL503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL503VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 60:F6:77:DD:DB:90 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:624605 acl:10743 sco:0 events:125 errors:0 TX bytes:5814 acl:12 sco:0 commands:106 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1800839 Title: Dualshock3 hid_sony accelerometer not registering as joystick Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25 [12649.015925] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24 [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux perhaps this is only a config issue as when the new split gyro & analog sticks/buttons/triggers both appeared as joysticks while you can now see only Sony PLAYSTATION(R)3 Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 Controller Motion Sensors (input25) does not. Any questions I am happy to respond, I have every reason to believe this is actually not a bluez issue but google gives me no returns other than general compatibility issues over the new hid_sony driver splitting the gyro from the pad. I use this to stay current on instrument flying while working out of town using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator that fis in my laptop bag. thanks dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Wed Oct 31 15:06:00 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. GL503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL503VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 60:F6:77:DD:DB:90 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:624605 acl:10743 sco:0 events:125 errors:0 TX bytes:5814 acl:12 sco:0 commands:106 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800458] Re: [Intel Corporation UHD Graphics 620] Xorg freeze
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800458 Title: [Intel Corporation UHD Graphics 620] Xorg freeze Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: Whenever i dock my laptop it freezes and I have to power it off. Black screen. HP 2013 UltraSlim Docking Station --- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 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: Mon Oct 29 13:13:09 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5] InstallationDate: Installed on 2018-10-15 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook 14u G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2018 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.01.08 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.50.00 dmi.chassis.asset.tag: 5CG8305291 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.01.08:bd06/05/2018:svnHP:pnHPZBook14uG5:pvr:rvnHP:rn83B2:rvrKBCVersion04.50.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP ZBook 14u G5 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800458] Re: [Intel Corporation UHD Graphics 620] Xorg freeze
Checking the logs, it appears that there are two video cards, but according to the backtrace there are problems with the video card 'Intel'. CurrentDmesg.txt: [ 98.239676] Call Trace: [ 98.239685] v4l_enum_fmt+0x74/0x110 [videodev] [ 98.239689] __video_do_ioctl+0x370/0x380 [videodev] [ 98.239692] ? terminate_walk+0x8e/0xf0 [ 98.239696] video_usercopy+0x24d/0x640 [videodev] [ 98.239700] ? video_ioctl2+0x20/0x20 [videodev] [ 98.239704] video_ioctl2+0x15/0x20 [videodev] [ 98.239709] v4l2_ioctl+0xc8/0xf0 [videodev] [ 98.239741] ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915] [ 98.239744] do_vfs_ioctl+0xa8/0x630 [ 98.239746] ? kmem_cache_free+0x1b3/0x1e0 [ 98.239749] ? putname+0x4c/0x60 [ 98.239751] ? do_sys_open+0x13e/0x2c0 [ 98.239780] ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915] [ 98.239782] SyS_ioctl+0x79/0x90 [ 98.239786] do_syscall_64+0x73/0x130 [ 98.239790] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 ** Summary changed: - Xorg freeze + [Intel Corporation UHD Graphics 620] Xorg freeze ** Description changed: Whenever i dock my laptop it freezes and I have to power it off. Black screen. HP 2013 UltraSlim Docking Station --- + + Checking the logs, it appears that there are two video cards, but + according to the backtrace there are problems with the video card + 'Intel'. CurrentDmesg.txt: [ 98.239676] Call Trace: [ 98.239685] v4l_enum_fmt+0x74/0x110 [videodev] [ 98.239689] __video_do_ioctl+0x370/0x380 [videodev] [ 98.239692] ? terminate_walk+0x8e/0xf0 [ 98.239696] video_usercopy+0x24d/0x640 [videodev] [ 98.239700] ? video_ioctl2+0x20/0x20 [videodev] [ 98.239704] video_ioctl2+0x15/0x20 [videodev] [ 98.239709] v4l2_ioctl+0xc8/0xf0 [videodev] [ 98.239741] ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915] [ 98.239744] do_vfs_ioctl+0xa8/0x630 [ 98.239746] ? kmem_cache_free+0x1b3/0x1e0 [ 98.239749] ? putname+0x4c/0x60 [ 98.239751] ? do_sys_open+0x13e/0x2c0 [ 98.239780] ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915] [ 98.239782] SyS_ioctl+0x79/0x90 [ 98.239786] do_syscall_64+0x73/0x130 [ 98.239790] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 --- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 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: Mon Oct 29 13:13:09 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5] InstallationDate: Installed on 2018-10-15 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook 14u G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2018 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.01.08 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.50.00 dmi.chassis.asset.tag: 5CG8305291 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.01.08:bd06/05/2018:svnHP:pnHPZBook14uG5:pvr:rvnHP:rn83B2:rvrKBCVersion04.50.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP ZBook 14u G5 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git
[Touch-packages] [Bug 1800458] Re: Xorg freeze
** Description changed: Whenever i dock my laptop it freezes and I have to power it off. Black screen. HP 2013 UltraSlim Docking Station + + --- + + CurrentDmesg.txt: + [ 98.239676] Call Trace: + [ 98.239685] v4l_enum_fmt+0x74/0x110 [videodev] + [ 98.239689] __video_do_ioctl+0x370/0x380 [videodev] + [ 98.239692] ? terminate_walk+0x8e/0xf0 + [ 98.239696] video_usercopy+0x24d/0x640 [videodev] + [ 98.239700] ? video_ioctl2+0x20/0x20 [videodev] + [ 98.239704] video_ioctl2+0x15/0x20 [videodev] + [ 98.239709] v4l2_ioctl+0xc8/0xf0 [videodev] + [ 98.239741] ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915] + [ 98.239744] do_vfs_ioctl+0xa8/0x630 + [ 98.239746] ? kmem_cache_free+0x1b3/0x1e0 + [ 98.239749] ? putname+0x4c/0x60 + [ 98.239751] ? do_sys_open+0x13e/0x2c0 + [ 98.239780] ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915] + [ 98.239782] SyS_ioctl+0x79/0x90 + [ 98.239786] do_syscall_64+0x73/0x130 + [ 98.239790] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 + + --- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 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: Mon Oct 29 13:13:09 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] -Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5] + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] + Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5] InstallationDate: Installed on 2018-10-15 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd - Bus 001 Device 002: ID 8087:0a2b Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd + Bus 001 Device 002: ID 8087:0a2b Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook 14u G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2018 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.01.08 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.50.00 dmi.chassis.asset.tag: 5CG8305291 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.01.08:bd06/05/2018:svnHP:pnHPZBook14uG5:pvr:rvnHP:rn83B2:rvrKBCVersion04.50.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP ZBook 14u G5 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800458 Title: Xorg freeze Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Whenever i dock my laptop it freezes and I have to power it off. Black screen. HP 2013 UltraSlim Docking Station --- CurrentDmesg.txt: [ 98.239676] Call Trace: [ 98.239685] v4l_enum_fmt+0x74/0x110 [videodev] [ 98.239689] __video_do_ioctl+0x370/0x380 [videodev] [ 98.239692] ? terminate_walk+0x8e/0xf0 [ 98.
[Touch-packages] [Bug 1800458] Re: Xorg freeze
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800458 Title: Xorg freeze Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Whenever i dock my laptop it freezes and I have to power it off. Black screen. HP 2013 UltraSlim Docking Station --- CurrentDmesg.txt: [ 98.239676] Call Trace: [ 98.239685] v4l_enum_fmt+0x74/0x110 [videodev] [ 98.239689] __video_do_ioctl+0x370/0x380 [videodev] [ 98.239692] ? terminate_walk+0x8e/0xf0 [ 98.239696] video_usercopy+0x24d/0x640 [videodev] [ 98.239700] ? video_ioctl2+0x20/0x20 [videodev] [ 98.239704] video_ioctl2+0x15/0x20 [videodev] [ 98.239709] v4l2_ioctl+0xc8/0xf0 [videodev] [ 98.239741] ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915] [ 98.239744] do_vfs_ioctl+0xa8/0x630 [ 98.239746] ? kmem_cache_free+0x1b3/0x1e0 [ 98.239749] ? putname+0x4c/0x60 [ 98.239751] ? do_sys_open+0x13e/0x2c0 [ 98.239780] ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915] [ 98.239782] SyS_ioctl+0x79/0x90 [ 98.239786] do_syscall_64+0x73/0x130 [ 98.239790] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 --- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 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: Mon Oct 29 13:13:09 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5] InstallationDate: Installed on 2018-10-15 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook 14u G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2018 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.01.08 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.50.00 dmi.chassis.asset.tag: 5CG8305291 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.01.08:bd06/05/2018:svnHP:pnHPZBook14uG5:pvr:rvnHP:rn83B2:rvrKBCVersion04.50.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP ZBook 14u G5 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://
[Touch-packages] [Bug 1800210] Re: dose not work rite
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800210 Title: dose not work rite Status in xorg package in Ubuntu: Incomplete Bug description: APP STOR DOES NOT WORK RITE ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompositorRunning: None Date: Fri Oct 26 15:04:24 2018 DistUpgraded: 2018-10-25 22:05:32,733 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] InstallationDate: Installed on 2018-10-25 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C655 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2c9d5f71-ce27-4b3c-8018-0404d4ab5fb9 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago) dmi.bios.date: 07/07/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite C655 dmi.product.sku: Montevina_Fab dmi.product.version: PSC08U-03C01K dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Thu Oct 25 19:03:50 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5760 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1800210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799998] Re: [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%
** Summary changed: - 20% of volume is like 0% + [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0% -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/178 Title: [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0% Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is no sound on my laptop when volume is set to 20% or less. Also, when I set it to 100%, its output is lower than on Windows. The problem occurs when using a headphone as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: roinujnosde 1600 F...m pulseaudio /dev/snd/controlC0: roinujnosde 1600 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 13:33:21 2018 InstallationDate: Installed on 2018-10-09 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800292] Re: Mouse click every 1-2 minutes
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800292 Title: Mouse click every 1-2 minutes Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: After turn on my computer and my Ubuntu install updates today (Oct 27), I restarted to apply the updates and my mouse started do auto click 2-3 times in sequence every 1-2 minutes. I tried to restart, tried to unplug my mouse but it keep happening. Its infuriating, because im watching youtube fullscreen and every 1-2 minutes it clicks and stop the video and go out full screen, so I need to play again and go to fullscreen again, just to 1-2 minutes later repeat all over again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04: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-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Oct 27 12:54:34 2018 DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-34-generic, x86_64: installed nvidia, 390.48, 4.15.0-36-generic, x86_64: installed nvidia, 390.48, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:131d] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d] InstallationDate: Installed on 2018-06-07 (141 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LN ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago) dmi.bios.date: 05/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LN.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 27 12:24:30 2018 xserver.configfile: default xserver.errors: systemd-logind: failed to release device: Device not taken xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800292] Re: Mouse click every 1-2 minutes
** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800292 Title: Mouse click every 1-2 minutes Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After turn on my computer and my Ubuntu install updates today (Oct 27), I restarted to apply the updates and my mouse started do auto click 2-3 times in sequence every 1-2 minutes. I tried to restart, tried to unplug my mouse but it keep happening. Its infuriating, because im watching youtube fullscreen and every 1-2 minutes it clicks and stop the video and go out full screen, so I need to play again and go to fullscreen again, just to 1-2 minutes later repeat all over again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04: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-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Oct 27 12:54:34 2018 DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-34-generic, x86_64: installed nvidia, 390.48, 4.15.0-36-generic, x86_64: installed nvidia, 390.48, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:131d] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d] InstallationDate: Installed on 2018-06-07 (141 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LN ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago) dmi.bios.date: 05/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LN.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 27 12:24:30 2018 xserver.configfile: default xserver.errors: systemd-logind: failed to release device: Device not taken xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800292] Re: Mouse click every 1-2 minutes
Could you try another mouse? -- Cristian Aravena Romero (caravena) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800292 Title: Mouse click every 1-2 minutes Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After turn on my computer and my Ubuntu install updates today (Oct 27), I restarted to apply the updates and my mouse started do auto click 2-3 times in sequence every 1-2 minutes. I tried to restart, tried to unplug my mouse but it keep happening. Its infuriating, because im watching youtube fullscreen and every 1-2 minutes it clicks and stop the video and go out full screen, so I need to play again and go to fullscreen again, just to 1-2 minutes later repeat all over again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04: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-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Oct 27 12:54:34 2018 DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-34-generic, x86_64: installed nvidia, 390.48, 4.15.0-36-generic, x86_64: installed nvidia, 390.48, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:131d] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d] InstallationDate: Installed on 2018-06-07 (141 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LN ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago) dmi.bios.date: 05/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LN.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 27 12:24:30 2018 xserver.configfile: default xserver.errors: systemd-logind: failed to release device: Device not taken xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800292] Re: Mouse click every 1-2 minutes
** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800292 Title: Mouse click every 1-2 minutes Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After turn on my computer and my Ubuntu install updates today (Oct 27), I restarted to apply the updates and my mouse started do auto click 2-3 times in sequence every 1-2 minutes. I tried to restart, tried to unplug my mouse but it keep happening. Its infuriating, because im watching youtube fullscreen and every 1-2 minutes it clicks and stop the video and go out full screen, so I need to play again and go to fullscreen again, just to 1-2 minutes later repeat all over again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04: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-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Oct 27 12:54:34 2018 DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-34-generic, x86_64: installed nvidia, 390.48, 4.15.0-36-generic, x86_64: installed nvidia, 390.48, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:131d] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d] InstallationDate: Installed on 2018-06-07 (141 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LN ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago) dmi.bios.date: 05/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LN.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 27 12:24:30 2018 xserver.configfile: default xserver.errors: systemd-logind: failed to release device: Device not taken xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1800292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799964] Re: Ubuntu 18.10 After Blank Screen System Won't Come Back
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799964 Title: Ubuntu 18.10 After Blank Screen System Won't Come Back Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: In Ubuntu 18.10 if the blank screen feature initiates (5 minutes default) the system will remain blank and there is no way to get the display back on without a hard reset. The video card I am using is a Vega 64. Other users who have Vega AMD GPU's are experiencing the same issue. This is only happening in Ubuntu 18.10. Does not occur in my Arch or Fedora installs. To reproduce: - Let 'Blank Screen' feature execute (5 min default) - Screen will not come back ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 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: Thu Oct 25 10:18:59 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4] InstallationDate: Installed on 2018-10-19 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Micro-Star International Co., Ltd. MS-7B78 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=21c08187-f134-41b4-b8e5-93bead748c4f ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.20 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd04/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799994] Re: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36
** Bug watch added: freedesktop.org Bugzilla #108555 https://bugs.freedesktop.org/show_bug.cgi?id=108555 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=108555 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/174 Title: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36 Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: Confirmed Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.f
[Touch-packages] [Bug 1799994] Re: Xorg loads, no display on 4.15.0-38, works on 4.15.0-36
Please: Xorg.0.log for '4.15.0-38' and '4.15.0-39'. Best regards, -- Cristian ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Xorg loads, no display on 4.15.0-38, works on 4.15.0-36 + Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/174 Title: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:
[Touch-packages] [Bug 1799998] Re: 20% of volume is like 0%
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/178 Title: 20% of volume is like 0% Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: There is no sound on my laptop when volume is set to 20% or less. Also, when I set it to 100%, its output is lower than on Windows. The problem occurs when using a headphone as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: roinujnosde 1600 F...m pulseaudio /dev/snd/controlC0: roinujnosde 1600 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 13:33:21 2018 InstallationDate: Installed on 2018-10-09 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799994] Re: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36
For linux -38 and -39: apport-collect -p xorg 174 Thanks you! -- Cristian ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/174 Title: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: Incomplete Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.vers
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect -p xorg 1799613 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Incomplete Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
https://bugzilla.freedesktop.org/show_bug.cgi?id=108554 -- Cristian Aravena Romero (caravena) ** Bug watch added: freedesktop.org Bugzilla #108554 https://bugs.freedesktop.org/show_bug.cgi?id=108554 ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=108554 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1799613 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/582 -- Cristian Aravena Romero (caravena) ** Description changed: + https://bugzilla.kernel.org/show_bug.cgi?id=201501 + + --- + + https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/582 + + --- + My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 - State: SUSPENDED - Name: alsa_output.pci-_00_1b.0.analog-stereo - Description: Built-in Audio Analog Stereo - Driver: module-alsa-card.c - Sample Specification: s32le 2ch 48000Hz - Channel Map: front-left,front-right - Owner Module: 7 - Mute: no - Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB - balance 0.00 - Base Volume: 65536 / 100% / 0.00 dB - Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor - Latency: 0 usec, configured 0 usec - Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY - Properties: - alsa.resolution_bits = "32" - device.api = "alsa" - device.class = "sound" - alsa.class = "generic" - alsa.subclass = "generic-mix" - alsa.name = "ALC892 Analog" - alsa.id = "ALC892 Analog" - alsa.subdevice = "0" - alsa.subdevice_name = "subdevice #0" - alsa.device = "0" - alsa.card = "2" - alsa.card_name = "HDA Intel PCH" - alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" - alsa.driver_name = "snd_hda_intel" - device.bus_path = "pci-:00:1b.0" - sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" - device.bus = "pci" - device.vendor.id = "8086" - device.vendor.name = "Intel Corporation" - device.product.id = "1c20" - device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" - device.form_factor = "internal" - device.string = "front:2" - device.buffering.buffer_size = "65536" - device.buffering.fragment_size = "32768" - device.access_mode = "mmap+timer" - device.profile.name = "analog-stereo" - device.profile.description = "Analog Stereo" - device.description = "Built-in Audio Analog Stereo" - alsa.mixer_name = "Realtek ALC892" - alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" - module-udev-detect.discovered = "1" - device.icon_name = "audio-card-pci" - Ports: - analog-output-lineout: Line Out (priority: 9900, available) - analog-output-headphones: Headphones (priority: 9000, not available) - Active Port: analog-output-lineout - Formats: - pcm + State: SUSPENDED + Name: alsa_output.pci-_00_1b.0.analog-stereo + Description: Built-in Audio Analog Stereo + Driver: module-alsa-card.c + Sample Specification: s32le 2ch 48000Hz + Channel Map: front-left,front-right + Owner Module: 7 + Mute: no + Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB + balance 0.00 + Base Volume: 65536 / 100% / 0.00 dB + Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor + Latency: 0 usec, configured 0 usec + Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY + Properties: + alsa.resolution_bits = "32" + device.api = "alsa" + device.class = "sound" + alsa.class = "generic" + alsa.subclass = "generic-mix" + alsa.
[Touch-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
https://bugzilla.kernel.org/show_bug.cgi?id=201501 -- Cristian Aravena Romero (caravena) ** Bug watch added: Linux Kernel Bug Tracker #201501 https://bugzilla.kernel.org/show_bug.cgi?id=201501 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=201501 Importance: Unknown Status: Unknown ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
[Touch-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
Thank you for taking the time to report this bug and helping to make Ubuntu better. Execute the following command in the terminal: $ apport-collect -p linux 1799541 Best regards, -- Cristian Aravena Romero (caravena) ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Incomplete Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 us
[Touch-packages] [Bug 1799283] Re: Macbook Air keyboard backlighting does not work on Ubuntu 18.10
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8 ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799283 Title: Macbook Air keyboard backlighting does not work on Ubuntu 18.10 Status in xorg package in Ubuntu: Incomplete Bug description: Tested on a fresh installation of Ubuntu 18.10 and also on Ubuntu 18.10 Live. The keyboard backlighting works fine on Ubuntu 18.04 and MacOS . Also tested `xset led 1` for 1 to 32 command and it does not work as well. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 22:41:33 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b] InstallationDate: Installed on 2018-10-20 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Apple Inc. MacBookAir6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=89e36b21-5540-440c-a145-16be978fa6ba ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0103.B00.1708080653 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0103.B00.1708080653:bd08/08/2017:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.family: MacBook Air dmi.product.name: MacBookAir6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Hola sudo apt-get install --reinstall hplip hplip-data sudo apt-get install --reinstall python3 soluciono mi problema! Gracias Dimitri!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Invalid Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798083] Re: Nvidia doesn't work after I upgraded to 4.19rc8
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1798083 Title: Nvidia doesn't work after I upgraded to 4.19rc8 Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Bug description: I upgraded my linux to 4.19rc8 When I logged in ubuntu,It says `Error parsing nvidia-settings: lines[i] is undefined` Then I checked,nvidia doesn't work. $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. gnome-shell[5862]: error: Error parsing nvidia-settings: lines[i] is undefined nvidia-settings-autostart.desktop[6862]: ERROR: NVIDIA driver is not loaded nvidia-settings-autostart.desktop[6862]: ERROR: Error querying enabled displays on GPU 0 (Missing Extension). nvidia-settings-autostart.desktop[6862]: ERROR: Error querying connected displays on GPU 0 (Missing Extension). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 20:18:27 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-10-generic, x86_64: installed nvidia, 390.87, 4.18.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1b90] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1b90] InstallationDate: Installed on 2018-10-10 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc8-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'
** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1797625 Title: Missing the 'Call Trace' with the cases of 'KernelOops' Status in apport package in Ubuntu: New Bug description: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1797625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797625] [NEW] Missing the 'Call Trace' with the cases of 'KernelOops'
Public bug reported: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session ** Description changed: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 + And the file: 'OopsText.txt' does not appear in the 'Call Trace'. + Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." - - - And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: - + ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1797625 Title: Missing the 'Call Trace' with the cases of 'KernelOops' Status in apport package in Ubuntu: New Bug description: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - A
[Touch-packages] [Bug 1797588] Re: System lagging
Hello David, https://bugs.freedesktop.org/show_bug.cgi?id=108346#c1 "Do you have this problem? If so, a bit more information could help. What DE are you using, what version of mesa, what programs aren't opening "well", etc?" Best regards, -- Cristian Aravena Romero (caravena) ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1797588 Title: System lagging Status in X.Org X server: Unknown Status in xorg package in Ubuntu: Incomplete Bug description: The system is lagging and not opening programs well. even switching between windows is very slow. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 12 08:37:51 2018 DistUpgraded: 2018-09-28 22:03:01,394 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT216 [GeForce GT 220] [1043:82f3] InstallationDate: Installed on 2018-01-02 (282 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=b73e1c3a-b0eb-4da1-9c26-2fba56feefa2 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-29 (13 days ago) dmi.bios.date: 06/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Sep 28 08:34:42 2018 xserver.configfile: default 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.outputs: Output DVI-I-1 HDMI-1 VGA-1 xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1797588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797588] Re: System lagging
https://bugs.freedesktop.org/show_bug.cgi?id=108346 -- Cristian Aravena Romero (caravena) ** Bug watch added: freedesktop.org Bugzilla #108346 https://bugs.freedesktop.org/show_bug.cgi?id=108346 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=108346 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1797588 Title: System lagging Status in X.Org X server: Unknown Status in xorg package in Ubuntu: New Bug description: The system is lagging and not opening programs well. even switching between windows is very slow. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 12 08:37:51 2018 DistUpgraded: 2018-09-28 22:03:01,394 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT216 [GeForce GT 220] [1043:82f3] InstallationDate: Installed on 2018-01-02 (282 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=b73e1c3a-b0eb-4da1-9c26-2fba56feefa2 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-29 (13 days ago) dmi.bios.date: 06/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Sep 28 08:34:42 2018 xserver.configfile: default 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.outputs: Output DVI-I-1 HDMI-1 VGA-1 xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1797588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797555] Re: headphone not detected on initialization
Hello Bruno, Please create a new report with this command in the terminal: $ ubuntu-bug linux Best regards, -- Cristian Aravena Romero (caravena) ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797555 Title: headphone not detected on initialization Status in pulseaudio package in Ubuntu: Incomplete Bug description: every time i initialize the computer with the headphone connected, there's no sound in the headphones. i have to take the headphone off and plug it again, then i'm prompted with the ubuntu window asking if it's a headphone, phone or mic. after selecting the headphone option the audio works fine. this happens every time, not a single exception to this behavior. my laptop is a Dell Inspiron 15-3567 with Ubuntu 18.04. 1) Ubuntu 18.04.1 2) Pulseaudio 1:11.1-1ubuntu7.1 3) Expected to initialize the OS with the headphone connected and get the headphone recognized right away. 4) There's no sound in the headphones, and i have to take them off and plug it again. Then after responding to the ubuntu audio window the sound goes back to working again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1797432 Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: Headphone jack stopped working. Speakers do work. Nevermind issue was on my end not sure how to close bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 11 13:12:34 2018 InstallationDate: Installed on 2018-01-05 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1797432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all
@EoflaOE You could try the version [0]'Ubuntu Desktop > 18.04' [0] https://www.ubuntu.com/#download Best regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1797432 Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Headphone jack stopped working. Speakers do work. Nevermind issue was on my end not sure how to close bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 11 13:12:34 2018 InstallationDate: Installed on 2018-01-05 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1797432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1797432 Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Headphone jack stopped working. Speakers do work. Nevermind issue was on my end not sure how to close bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 11 13:12:34 2018 InstallationDate: Installed on 2018-01-05 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1797432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794843] Re: New release of 'gstreamer1.0' (1.14.4)
** Tags added: rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794843 Title: New release of 'gstreamer1.0' (1.14.4) Status in gstreamer1.0 package in Ubuntu: In Progress Bug description: Hello, https://packages.debian.org/source/sid/gstreamer1.0 'Source Package: gstreamer1.0 (1.14.3-1)' Best regards, -- Cristian Aravena Romero (caravena) --- https://gstreamer.freedesktop.org/releases/1.14/#1.14.3 == 1.14.3 == The third 1.14 bug-fix release (1.14.3) was released on 16 September 2018. This release only contains bugfixes and it should be safe to update from 1.14.x. Highlighted bugfixes in 1.14.3 opusenc: fix crash on 32-bit platforms compositor: fix major buffer leak when doing crossfading on some but not all pads wasapi: various fixes for wasapisrc and wasapisink regressions x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. Rebuild to..." runtime errors with x264 version ≥ 153 audioaggregator, audiomixer: caps negotiation fixes input-selector: latency handling fixes playbin, playsink: audio visualization support fixes dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand profile opencv: Fix build for opencv >= 3.4.2 h265parse: miscellaneous fixes backported from h264parse pads: fix changing of pad offsets from inside pad probes pads: ensure that pads are blocked for IDLE probes if they are called from the streaming thread too ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.2-2 Uname: Linux 4.18.10-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 13:43:05 2018 InstallationDate: Installed on 2017-10-13 (349 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1794843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1306299] Re: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: el subproceso script pre-ins
Hello, If you can close this report, Thank you! Best regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1306299 Title: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 2 Status in vim package in Ubuntu: Expired Bug description: Crash. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] Uname: Linux 3.14.0-031400-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 AptOrdering: vim-runtime: Install vim: Install vim-runtime: Configure vim: Configure Architecture: amd64 Date: Thu Apr 10 20:41:32 2014 DuplicateSignature: package:vim-runtime:(not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags]:el subproceso script pre-installation nuevo devolvió el código de salida de error 2 ErrorMessage: el subproceso script pre-installation nuevo devolvió el código de salida de error 2 InstallationDate: Installed on 2014-01-23 (77 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122) SourcePackage: vim Title: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1306299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796367] Re: New release of 'mesa' (18.2.2)
** Summary changed: - New release of 'mesa3d' (18.2.2) + New release of 'mesa' (18.2.2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1796367 Title: New release of 'mesa' (18.2.2) Status in mesa package in Ubuntu: New Bug description: Hello, https://www.mesa3d.org/relnotes/18.2.2.html Bug fixes - [apitrace] Graphical artifacts in Civilization VI on RX Vega - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported - radv: OpBitfieldUExtract returns incorrect result when count is zero - [DXVK] MSAA reflections are broken in GTA V - [Debian Stretch]Fail to build because "xcb_randr_lease_t" Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.1-1ubuntu1 Uname: Linux 4.18.12-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 13:45:21 2018 Dependencies: gcc-8-base 8.2.0-7ubuntu1 libc6 2.28-0ubuntu1 libgcc1 1:8.2.0-7ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu1 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-8-generic, x86_64: installed virtualbox, 5.2.18, 4.18.12-gnu, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0d7] InstallationDate: Installed on 2017-10-13 (357 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.12-gnu root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Fri Jul 20 17:46:48 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1796367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796367] [NEW] New release of 'mesa3d' (18.2.2)
Public bug reported: Hello, https://www.mesa3d.org/relnotes/18.2.2.html Bug fixes - [apitrace] Graphical artifacts in Civilization VI on RX Vega - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported - radv: OpBitfieldUExtract returns incorrect result when count is zero - [DXVK] MSAA reflections are broken in GTA V - [Debian Stretch]Fail to build because "xcb_randr_lease_t" Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.1-1ubuntu1 Uname: Linux 4.18.12-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 13:45:21 2018 Dependencies: gcc-8-base 8.2.0-7ubuntu1 libc6 2.28-0ubuntu1 libgcc1 1:8.2.0-7ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu1 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-8-generic, x86_64: installed virtualbox, 5.2.18, 4.18.12-gnu, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0d7] InstallationDate: Installed on 2017-10-13 (357 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.12-gnu root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Fri Jul 20 17:46:48 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu upgrade-software-version wayland-session ** Description changed: Hello, https://www.mesa3d.org/relnotes/18.2.2.html Bug fixes - Bug 104602 - [apitrace] Graphical artifacts in Civilization VI on RX Vega - Bug 104926 - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported - Bug 107276 - radv: OpBitfieldUExtract returns incorrect result when count is zero - Bug 107786 - [DXVK] MSAA reflections are broken in GTA V - Bug 108024 - [Debian Stretch]Fail to build because "xcb_randr_lease_t" + - [apitrace] Graphical artifacts in Civilization VI on RX Vega + - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported + - radv: OpBitfieldUExtract returns incorrect result when count is zero + - [DXVK] MSAA reflections are broken in GTA V + - [Debian Stretch]Fail to build because "xcb_randr_lease_t" Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.1-1ubuntu1 Uname: Linux 4.18.12-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 13:45:21 2018 Dependencies: - gcc-8-base 8.2.0-7ubuntu1 - libc6 2.28-0ubuntu1 - libgcc1 1:8.2.0-7ubuntu1 - libidn2-0 2.0.5-1 - libunistring2 0.9.10-1ubuntu1 + gcc-8-base 8.2.0-7ubuntu1 + libc6 2.28-0ubuntu1 + libgcc1 1:8.2.0-7ub
[Touch-packages] [Bug 1794843] Re: New release of 'gstreamer1.0' (1.14.4)
** Summary changed: - New release of 'gstreamer1.0' (1.14.3-1) in Debian + New release of 'gstreamer1.0' (1.14.4) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794843 Title: New release of 'gstreamer1.0' (1.14.4) Status in gstreamer1.0 package in Ubuntu: Triaged Bug description: Hello, https://packages.debian.org/source/sid/gstreamer1.0 'Source Package: gstreamer1.0 (1.14.3-1)' Best regards, -- Cristian Aravena Romero (caravena) --- https://gstreamer.freedesktop.org/releases/1.14/#1.14.3 == 1.14.3 == The third 1.14 bug-fix release (1.14.3) was released on 16 September 2018. This release only contains bugfixes and it should be safe to update from 1.14.x. Highlighted bugfixes in 1.14.3 opusenc: fix crash on 32-bit platforms compositor: fix major buffer leak when doing crossfading on some but not all pads wasapi: various fixes for wasapisrc and wasapisink regressions x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. Rebuild to..." runtime errors with x264 version ≥ 153 audioaggregator, audiomixer: caps negotiation fixes input-selector: latency handling fixes playbin, playsink: audio visualization support fixes dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand profile opencv: Fix build for opencv >= 3.4.2 h265parse: miscellaneous fixes backported from h264parse pads: fix changing of pad offsets from inside pad probes pads: ensure that pads are blocked for IDLE probes if they are called from the streaming thread too ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.2-2 Uname: Linux 4.18.10-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 13:43:05 2018 InstallationDate: Installed on 2017-10-13 (349 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1794843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794843] Re: New release of 'gstreamer1.0' (1.14.3-1) in Debian
Hello, https://gstreamer.freedesktop.org/releases/1.14/#1.14.4 The fourth 1.14 bug-fix release (1.14.4) was released on 2 October 2018. This release only contains bugfixes and it should be safe to update from 1.14.x. Highlighted bugfixes in 1.14.4 glviewconvert: wait and set the gl sync meta on buffers glviewconvert: Copy composition meta from the primary buffer to both outputs glcolorconvert: Don't copy overlay composition meta over to NULL outbufs matroskademux: add functionality needed for MSE use case fixing youtube playback in epiphany/webkit-gtk msdk: fix build on windows opusenc: fix another crash on 32-bit x86 on windows (alignment issue in SSE optimisations) osxaudio: add support for parsing more channel layouts tagdemux: Use upstream GST_EVENT_STREAM_START (and stream-id) if present vorbisdec: fix header handling regression: init decoder immediately once we have headers wasapisink: recover from low buffer levels in shared mode fix GstSegment unit test which would fail on some 32-bit x86 CPUs Best regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794843 Title: New release of 'gstreamer1.0' (1.14.3-1) in Debian Status in gstreamer1.0 package in Ubuntu: Triaged Bug description: Hello, https://packages.debian.org/source/sid/gstreamer1.0 'Source Package: gstreamer1.0 (1.14.3-1)' Best regards, -- Cristian Aravena Romero (caravena) --- https://gstreamer.freedesktop.org/releases/1.14/#1.14.3 == 1.14.3 == The third 1.14 bug-fix release (1.14.3) was released on 16 September 2018. This release only contains bugfixes and it should be safe to update from 1.14.x. Highlighted bugfixes in 1.14.3 opusenc: fix crash on 32-bit platforms compositor: fix major buffer leak when doing crossfading on some but not all pads wasapi: various fixes for wasapisrc and wasapisink regressions x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. Rebuild to..." runtime errors with x264 version ≥ 153 audioaggregator, audiomixer: caps negotiation fixes input-selector: latency handling fixes playbin, playsink: audio visualization support fixes dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand profile opencv: Fix build for opencv >= 3.4.2 h265parse: miscellaneous fixes backported from h264parse pads: fix changing of pad offsets from inside pad probes pads: ensure that pads are blocked for IDLE probes if they are called from the streaming thread too ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.2-2 Uname: Linux 4.18.10-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 13:43:05 2018 InstallationDate: Installed on 2017-10-13 (349 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1794843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794843] [NEW] FFe: New release of 'gstreamer1.0' (1.14.3-1) in Debian
Public bug reported: Hello, https://packages.debian.org/source/sid/gstreamer1.0 'Source Package: gstreamer1.0 (1.14.3-1)' Best regards, -- Cristian Aravena Romero (caravena) --- https://gstreamer.freedesktop.org/releases/1.14/#1.14.3 == 1.14.3 == The third 1.14 bug-fix release (1.14.3) was released on 16 September 2018. This release only contains bugfixes and it should be safe to update from 1.14.x. Highlighted bugfixes in 1.14.3 opusenc: fix crash on 32-bit platforms compositor: fix major buffer leak when doing crossfading on some but not all pads wasapi: various fixes for wasapisrc and wasapisink regressions x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. Rebuild to..." runtime errors with x264 version ≥ 153 audioaggregator, audiomixer: caps negotiation fixes input-selector: latency handling fixes playbin, playsink: audio visualization support fixes dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand profile opencv: Fix build for opencv >= 3.4.2 h265parse: miscellaneous fixes backported from h264parse pads: fix changing of pad offsets from inside pad probes pads: ensure that pads are blocked for IDLE probes if they are called from the streaming thread too ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.2-2 Uname: Linux 4.18.10-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 13:43:05 2018 InstallationDate: Installed on 2017-10-13 (349 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic upgrade-software-version wayland-session ** Description changed: Hello, https://packages.debian.org/source/sid/gstreamer1.0 'Source Package: gstreamer1.0 (1.14.3-1)' + + Best regards, + -- + Cristian Aravena Romero (caravena) --- https://gstreamer.freedesktop.org/releases/1.14/#1.14.3 == 1.14.3 == The third 1.14 bug-fix release (1.14.3) was released on 16 September 2018. This release only contains bugfixes and it should be safe to update from 1.14.x. Highlighted bugfixes in 1.14.3 opusenc: fix crash on 32-bit platforms compositor: fix major buffer leak when doing crossfading on some but not all pads wasapi: various fixes for wasapisrc and wasapisink regressions x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. Rebuild to..." runtime errors with x264 version ≥ 153 audioaggregator, audiomixer: caps negotiation fixes input-selector: latency handling fixes playbin, playsink: audio visualization support fixes dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand profile opencv: Fix build for opencv >= 3.4.2 h265parse: miscellaneous fixes backported from h264parse pads: fix changing of pad offsets from inside pad probes pads: ensure that pads are blocked for IDLE probes if they are called from the streaming thread too - Best regards, - -- - Cristian Aravena Romero (caravena) - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.2-2 Uname: Linux 4.18.10-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 13:43:05 2018 InstallationDate: Installed on 2017-10-13 (349 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - FFe: New release of 'libgstreamer1.0-0' in Debian + FFe: New release of 'libgstreamer1.0-0' (1.14.3-1) in Debian ** Summary changed: - FFe: New release of 'libgstreamer1.0-0' (1.14.3-1) in Debian + FFe: New release of 'gstreamer1.0' (1.14.3-1) in Debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794843 Title: FFe: New release of 'gstreamer1.0' (1.14.3-1) in Debian Status in gstreamer1.0 package in Ubuntu: New Bug description: Hello, https://packages.debian.org/source/sid/gstreamer1.0 'Source Package: gstreamer1.0 (1.14.3-1)' Best regards, -- Cristian Aravena Romero (caravena) --- https://gstreamer.freedesktop.org/releases/1.14/#1.14.3 == 1.14.3 == The third 1.14 bug-fix release (1.14.3) was released on 16 September 2018. This release only contains bugfixes and it should be safe to update from 1.14.x. Highlighted bugfixes in 1.14.3 opusenc: fix crash on 32-bit platforms compositor: fix major buffer leak when doing crossfading on some but not
[Touch-packages] [Bug 1792578] Re: tracker-store crashed with SIGSEGV
** Information type changed from Private to Public ** Description changed: Hello, I do not know how it happened Best regards, -- Cristian Aravena Romero (caravena) + + + + https://gitlab.gnome.org/GNOME/tracker/issues/39 ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: tracker 2.0.3-3 Uname: Linux 4.18.7-gnu x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 14 08:51:24 2018 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2017-10-13 (335 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: - Segfault happened at: 0x7ff7ad4aa0d7:mov%rcx,0x30(%rdx) - PC (0x7ff7ad4aa0d7) ok - source "%rcx" ok - destination "0x30(%rdx)" (0x0030) not located in a known VMA region (needed writable region)! - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7ff7ad4aa0d7:mov%rcx,0x30(%rdx) + PC (0x7ff7ad4aa0d7) ok + source "%rcx" ok + destination "0x30(%rdx)" (0x0030) not located in a known VMA region (needed writable region)! + Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: - () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 - () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 - () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 - () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 - () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 + () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 + () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 + () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 + () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 + () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 Title: tracker-store crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1792578 Title: tracker-store crashed with SIGSEGV Status in tracker package in Ubuntu: New Bug description: Hello, I do not know how it happened Best regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/tracker/issues/39 ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: tracker 2.0.3-3 Uname: Linux 4.18.7-gnu x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 14 08:51:24 2018 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2017-10-13 (335 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x7ff7ad4aa0d7:mov%rcx,0x30(%rdx) PC (0x7ff7ad4aa0d7) ok source "%rcx" ok destination "0x30(%rdx)" (0x0030) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 () at /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 Title: tracker-store crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1792578/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Hello Brian Murray, The error continues :-( caravena@caravena-530u3c-530u4c:/var/log$ whoopsie caravena@caravena-530u3c-530u4c:/var/log$ systemctl status apport-autoreport.service ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2018-08-23 08:02:30 -03; 1h 24min ago Process: 813 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=1/FAILURE) Main PID: 813 (code=exited, status=1/FAILURE) ago 23 08:02:28 caravena-530u3c-530u4c systemd[1]: Starting Process error reports when automatic reporting is enabled... ago 23 08:02:30 caravena-530u3c-530u4c whoopsie-upload-all[813]: ERROR: whoopsie is not running ago 23 08:02:30 caravena-530u3c-530u4c systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE ago 23 08:02:30 caravena-530u3c-530u4c systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. ago 23 08:02:30 caravena-530u3c-530u4c systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Kind regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Hello Brian Murray, First run the program 'whoopsie' then run 'systemctl status apport- autoreport.service' and no longer throw the error... caravena@caravena-530u3c-530u4c:/var/crash$ whoopsie caravena@caravena-530u3c-530u4c:/var/crash$ systemctl status apport-autoreport.service ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2018-08-22 10:15:46 -03; 3h 24min ago Process: 11093 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=0/SUCCESS) Main PID: 11093 (code=exited, status=0/SUCCESS) ago 22 10:15:46 caravena-530u3c-530u4c systemd[1]: Starting Process error reports when automatic reporting is enabled... ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: /var/crash/_usr_bin_gnome-control-center.1000.crash already marked for upload, skipping ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: /var/crash/_usr_lib_telepathy_telepathy-idle.1000.crash already marked for upload, skipping ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: /var/crash/_usr_bin_Xwayland.1000.crash already marked for upload, skipping ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: All reports processed ago 22 10:15:46 caravena-530u3c-530u4c systemd[1]: Started Process error reports when automatic reporting is enabled. kind regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788383] Re: Bluetooth: hci0: last event is not cmd complete (0x0f)
** Description changed: Hello, dmesg: [ 320.201884] Bluetooth: hci0: last event is not cmd complete (0x0f) - Looking forward to hearing from you, + Kind regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 Uname: Linux 4.18.3-041803-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 22 08:20:18 2018 InstallationDate: Installed on 2017-10-13 (312 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) InterestingModules: rfcomm bnep btusb bluetooth MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.3-041803-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. hciconfig: - hci0:Type: Primary Bus: USB - BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8 - UP RUNNING PSCAN - RX bytes:4815 acl:0 sco:0 events:107 errors:0 - TX bytes:5444 acl:0 sco:0 commands:68 errors:0 + hci0:Type: Primary Bus: USB + BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8 + UP RUNNING PSCAN + RX bytes:4815 acl:0 sco:0 events:107 errors:0 + TX bytes:5444 acl:0 sco:0 commands:68 errors:0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1788383 Title: Bluetooth: hci0: last event is not cmd complete (0x0f) Status in bluez package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 320.201884] Bluetooth: hci0: last event is not cmd complete (0x0f) Kind regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 Uname: Linux 4.18.3-041803-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 22 08:20:18 2018 InstallationDate: Installed on 2017-10-13 (312 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) InterestingModules: rfcomm bnep btusb bluetooth MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.3-041803-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. hciconfig: hci0:Type: Primary Bus: USB BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:4815 acl:0 sco:0 events:107 errors:0 TX bytes:5444 acl:0 sco:0 commands:68 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1788383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788383] [NEW] Bluetooth: hci0: last event is not cmd complete (0x0f)
Public bug reported: Hello, dmesg: [ 320.201884] Bluetooth: hci0: last event is not cmd complete (0x0f) Looking forward to hearing from you, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 Uname: Linux 4.18.3-041803-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 22 08:20:18 2018 InstallationDate: Installed on 2017-10-13 (312 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) InterestingModules: rfcomm bnep btusb bluetooth MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.3-041803-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. hciconfig: hci0: Type: Primary Bus: USB BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:4815 acl:0 sco:0 events:107 errors:0 TX bytes:5444 acl:0 sco:0 commands:68 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1788383 Title: Bluetooth: hci0: last event is not cmd complete (0x0f) Status in bluez package in Ubuntu: New Bug description: Hello, dmesg: [ 320.201884] Bluetooth: hci0: last event is not cmd complete (0x0f) Looking forward to hearing from you, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 Uname: Linux 4.18.3-041803-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 22 08:20:18 2018 InstallationDate: Installed on 2017-10-13 (312 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) InterestingModules: rfcomm bnep btusb bluetooth MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.3-041803-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. hciconfig: hci0:Type: Primary Bus: USB BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:4815 acl:0 sco:0 events:107 errors:0 TX bytes:5444 acl:0 sco:0 commands:68 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1788383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Hello Brian Murray, $ systemctl status apport-autoreport.service ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-08-18 21:09:36 -03; 4min 17s ago Process: 823 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=1/FAILURE) Main PID: 823 (code=exited, status=1/FAILURE) ago 18 21:09:35 caravena-530u3c-530u4c systemd[1]: Starting Process error reports when automatic reporting is enabled... ago 18 21:09:36 caravena-530u3c-530u4c whoopsie-upload-all[823]: ERROR: whoopsie is not running ago 18 21:09:36 caravena-530u3c-530u4c systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE ago 18 21:09:36 caravena-530u3c-530u4c systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. ago 18 21:09:36 caravena-530u3c-530u4c systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
** Description changed: When running - sudo apt update + sudo apt update in a terminal I sometimes see the following message printed within the output. - (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: + (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. + + -- + + https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in appstream package in Ubuntu: Confirmed Status in glib2.0 package in Ubuntu: Confirmed Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1785498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] [NEW] [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Public bug reported: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session ** Attachment added: "20180817_195237.jpg" https://bugs.launchpad.net/bugs/1787729/+attachment/5177139/+files/20180817_195237.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: New Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785703] Re: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
** Also affects: aptitude (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785703 Title: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in aptitude package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Bug description: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1785703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785703] [NEW] appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Public bug reported: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session ** Attachment added: "aptitude.png" https://bugs.launchpad.net/bugs/1785703/+attachment/5172303/+files/aptitude.png ** Description changed: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) + + https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785703 Title: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in glib2.0 package in Ubuntu: New Bug description: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1785703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions
** Package changed: gstreamer1.0 (Ubuntu) => gstreamer-vaapi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1770725 Title: [i915 SNB] Totem window is all black in Wayland sessions Status in Gstreamer1.0: Incomplete Status in gstreamer-vaapi package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello, You can not see the image of the movie. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.0-1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.10-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri May 11 15:35:17 2018 InstallationDate: Installed on 2017-10-13 (210 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions
Hello Daniel van Vugt, If I remove "gstreamer1.0-vaapi" you can see the video in Wayland with Totem. Regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1770725 Title: [i915 SNB] Totem window is all black in Wayland sessions Status in Gstreamer1.0: Incomplete Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello, You can not see the image of the movie. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.0-1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.10-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri May 11 15:35:17 2018 InstallationDate: Installed on 2017-10-13 (210 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions
** Attachment added: "$sudo dpkg -l" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5145634/+files/dpkg_-l.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1770725 Title: [i915 SNB] You can not see the image of the movie in Wayland sessions Status in Gstreamer1.0: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Hello, You can not see the image of the movie. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.0-1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.10-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri May 11 15:35:17 2018 InstallationDate: Installed on 2017-10-13 (210 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions
Hello Daniel, With mpv it works well Regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1770725 Title: [i915 SNB] You can not see the image of the movie in Wayland sessions Status in Gstreamer1.0: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Hello, You can not see the image of the movie. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.0-1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.10-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri May 11 15:35:17 2018 InstallationDate: Installed on 2017-10-13 (210 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions
** Attachment added: "Description of the movie" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5145633/+files/Captura%20de%20pantalla%20de%202018-05-28%2013-35-01.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1770725 Title: [i915 SNB] You can not see the image of the movie in Wayland sessions Status in Gstreamer1.0: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Hello, You can not see the image of the movie. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.0-1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.10-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri May 11 15:35:17 2018 InstallationDate: Installed on 2017-10-13 (210 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions
** Attachment added: "totem" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5145653/+files/Captura%20de%20pantalla%20de%202018-05-28%2013-43-34.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1770725 Title: [i915 SNB] You can not see the image of the movie in Wayland sessions Status in Gstreamer1.0: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Hello, You can not see the image of the movie. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.0-1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.10-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri May 11 15:35:17 2018 InstallationDate: Installed on 2017-10-13 (210 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp