[Touch-packages] [Bug 2063200] [NEW] useradd --extrausers --groups tries to lock /etc/group
Public bug reported: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: New Bug description: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+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 2056642] [NEW] drop down menu appears on another workspace
Public bug reported: I am using Selenium webdriver to open a drop down menu in Firefox. When I manually open the drop down menu the bug does not appear. Because the drop down menu is being closed when I switch between workspaces. But when I switch to another workspace when the drop down menu is opened by Selenium webdriver it is appearing on the other workspace and I can interact with it. Screenshot is attached. $ dpkg --list | grep firefox ii firefox1:1snap1-0ubuntu2 amd64Transitional package - firefox -> firefox snap ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 17:35:02 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.50, 6.5.0-21-generic, x86_64: installed virtualbox/6.1.50, 6.5.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0102] MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-25-generic root=UUID=929bcce7-36fe-499e-8f75-ae48a4583b03 ro rootflags=subvol=@ quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H61M-GS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd03/07/2011:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-GS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 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 ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/2056642/+attachment/5754315/+files/PmqOQjl.png -- 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/2056642 Title: drop down menu appears on another workspace Status in xorg package in Ubuntu: New Bug description: I am using Selenium webdriver to open a drop down menu in Firefox. When I manually open the drop down menu the bug does not appear. Because the drop down menu is being closed when I switch between workspaces. But when I switch to another workspace when the drop down menu is opened by Selenium webdriver it is appearing on the other workspace and I can interact with it. Screenshot is attached. $ dpkg --list | grep firefox ii firefox1:1snap1-0ubuntu2 amd64Transitional package - firefox -> firefox snap ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 17:35:02 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.50, 6.5.0-21-generic, x86_64: installed virtualbox/6.1.50, 6.5.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated
[Touch-packages] [Bug 2037281] Re: Shutdown when triggering daemon-reload early in boot
I have done manual tests with jammy-proposed and focal-proposed. I have added in /etc/systemd/system, the following service and enabled it. Then rebooted. ``` [Unit] DefaultDependencies=no Before=systemd-udev-trigger.service [Service] Type=oneshot ExecStart=systemctl daemon-reload [Install] WantedBy=multi-user.target ``` If the bug was present, it would not complete the boot and have filesystems unmounted. When the fix is working, the boot would complete and it is possible to ssh to it. Results of the test: Ubuntu Core 22 Without jammy-proposed: systemd 249.11-0ubuntu3.11 -> broken With jammy-proposed: systemd 249.11-0ubuntu3.12 -> fixed Ubuntu Core 20, with pc-kernel 22/beta Without focal-proposed: systemd 245.4-4ubuntu3.22 -> broken With focal-proposed: systemd 245.4-4ubuntu3.23 -> fixed So I confirm the systemd packages in jammy-proposed and focal-proposed are fixing this issue. ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- 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/2037281 Title: Shutdown when triggering daemon-reload early in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Jammy: Fix Committed Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. [ Impact ] If a user adds a service that calls `systemctl daemon-reload`, and if this service is started before systemd-udevd. And if the initrd is systemd (the case of Ubuntu Core), then most service will be stopped or cancel, and the machine will mostly shutdown everything and hang. The fix has been backported down to 250 upstream. It is already on kinetic and later. The fix only affects systems where systemd is used in initrd. [ Test Plan ] On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on any system that uses systemd in initrd. Add a systemd service that calls `systemctl daemon-reload`. The service should have `DefaultDependencies=no` in order to start as soon as possible and be enabled. Restart the machine. If fix is not applied, after the service is started, most of units with be shutdown, and the system will be unusable. [ Where problems could occur ] This should affect systems with systemd in initrd. There are risks on systems that have an udev rule in initrd not present in the main system. There are risks on systems that use db_persist in initrd where the device can potentially get dead state. Though this does not seem to happen on Ubuntu Core 22, even though we use db_persist for dev mapper devices. Regression is upstream bug #23429. Commits named "core/device: device_coldplug(): don't set DEVICE_DEAD" and "core/device: do not downgrade device state if it is already enumerated" could be applied as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2037281] Re: Shutdown when triggering daemon-reload eary in boot
Just adding a comment on how to reproduce the bug, because I have lost a day trying to figure it out again. This fails only when not using secure boot because the device mapper state is kept from initrd to main boot. -- 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/2037281 Title: Shutdown when triggering daemon-reload eary in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Jammy: New Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. [ Impact ] If a user adds a service that calls `systemctl daemon-reload`, and if this service is started before systemd-udevd. And if the initrd is systemd (the case of Ubuntu Core), then most service will be stopped or cancel, and the machine will mostly shutdown everything and hang. The fix has been backported down to 250 upstream. It is already on kinetic and later. The fix only affects systems where systemd is used in initrd. [ Test Plan ] On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on any system that uses systemd in initrd. Add a systemd service that calls `systemctl daemon-reload`. The service should have `DefaultDependencies=no` in order to start as soon as possible and be enabled. Restart the machine. If fix is not applied, after the service is started, most of units with be shutdown, and the system will be unusable. [ Where problems could occur ] This should affect systems with systemd in initrd. There are risks on systems that have an udev rule in initrd not present in the main system. There are risks on systems that use db_persist in initrd where the device can potentially get dead state. Though this does not seem to happen on Ubuntu Core 22, even though we use db_persist for dev mapper devices. Regression is upstream bug #23429. Commits named "core/device: device_coldplug(): don't set DEVICE_DEAD" and "core/device: do not downgrade device state if it is already enumerated" could be applied as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2037281] Re: Shutdown when triggering daemon-reload eary in boot
** Description changed: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. + [ Impact ] - [ Impact ] - * An explanation of the effects of the bug on users and - * justification for backporting the fix to the stable release. - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + If a user adds a service that calls `systemctl daemon-reload`, and if + this service is started before systemd-udevd. And if the initrd is + systemd (the case of Ubuntu Core), then most service will be stopped or + cancel, and the machine will mostly shutdown everything and hang. + + The fix has been backported down to 250 upstream. It is already on + kinetic and later. + + The fix only affects systems where systemd is used in initrd. [ Test Plan ] - * detailed instructions how to reproduce the bug - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. - * if other testing is appropriate to perform before landing this update, -this should also be described here. + + On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on any + system that uses systemd in initrd. + + Add a systemd service that calls `systemctl daemon-reload`. + The service should have `DefaultDependencies=no` in order to start as soon as possible and be enabled. + + Restart the machine. + + If fix is not applied, after the service is started, most of units with + be shutdown, and the system will be unusable. [ Where problems could occur ] - * Think about what the upload changes in the software. Imagine the change is -wrong or breaks something else: how would this show up? - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. - * This must '''never''' be "None" or "Low", or entirely an argument as to why -your upload is low risk. - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. - [ Other Info ] - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + This should affect systems with systemd in initrd. + + There are risks on systems that have an udev rule in initrd not present + in the main system. + + There are risks on systems that use db_persist in initrd where the + device can potentially get dead state. Though this does not seem to + happen on Ubuntu Core 22, even though we use db_persist for dev mapper + devices. Regression is upstream bug #23429. Commits named "core/device: + device_coldplug(): don't set DEVICE_DEAD" and "core/device: do not + downgrade device state if it is already enumerated" could be applied as + well. -- 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/2037281 Title: Shutdown when triggering daemon-reload eary in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Jammy: New Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without
[Touch-packages] [Bug 2037281] [NEW] Shutdown when triggering daemon-reload eary in boot
Public bug reported: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2037281 Title: Shutdown when triggering daemon-reload eary in boot Status in systemd package in Ubuntu: New Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 1982563] [NEW] sbat-distro should be set
Public bug reported: -Dsbat-distro should be set so that the systemd efi stub gets a .sbat section. This is needed for secure boot. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1982563 Title: sbat-distro should be set Status in systemd package in Ubuntu: New Bug description: -Dsbat-distro should be set so that the systemd efi stub gets a .sbat section. This is needed for secure boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982563/+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 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
This can be reproduced without xmltodict, using only the stdlib:
>>> from xml.parsers import expat
>>> parser = expat.ParserCreate(namespace_separator=':')
>>> parser.Parse('', True)
Traceback (most recent call last):
File "", line 1, in
xml.parsers.expat.ExpatError: out of memory: line 1, column 0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to expat in Ubuntu.
https://bugs.launchpad.net/bugs/1961800
Title:
Seeing out of memory errors after libexpat1 upgrade to
2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
Status in expat package in Ubuntu:
Invalid
Status in python-xmltodict package in Ubuntu:
Confirmed
Bug description:
I started seeing errors parsing XML files today (Feb 22, 2022) after
my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server.
The parsing is being done by python3's xmltodict module, which uses
python3 expat as the actual parser. This is the error it raises:
xml.parsers.expat.ExpatError: out of memory: line 1, column 0
So far this is happening on multiple xml files, although they all come
from the same source (these are jenkins config.xml files). I'm working
on coming up with a minimal test case which I'll provide once I have
it cleaned up of any private data.
[System info]
$ lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04
$ apt-cache policy libexpat1
libexpat1:
Installed: 2.2.5-3ubuntu0.4
Candidate: 2.2.5-3ubuntu0.4
Version table:
*** 2.2.5-3ubuntu0.4 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
2.2.5-3 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
I'm on a dual screen with 4k and 2.7k (Surface pro 4) intel graphical chipset, i7 with 4 cores. On a 20.04, using gnome-shell over Xorg, gnome-shell proc usage jumps from 0-3% to 40-60% usage when using indicator-multiload. gnome-shell over Wayland will have same issue, with an added visible mouse stuttering problem. interestingly, I've installed unity7 (with ubuntu-unity-desktop 0.2), and this doesn't occur on unity as dramatically: it goes from 2-4% without indicator-multiload to 6-8%. This makes it totally usable on unity. indicator-multiload 0.4-0ubuntu5 gnome-shell 3.36.4-1ubuntu1~20.04.2 compiz-core 1:0.9.14.1+20.04.20200211-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 1766503] Re: ibus-* randomly use high CPU
Wait, there's more If I do multiple CTRL-z + Enter in gnome-calculator, the CPU goes HIGHER , and it stays there until ANY action is made ( either opening an app ( mouse or kbd shortcut, doesn't matter ) , or switch window by alt-tab or mouse ) Seems like an ibus (big?) problem . Also seems ibus is running on multiple processes/cores ( and hangs on all of them in the end ) , is this intended ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in GNOME Shell: Unknown Status in The Ubuntu Power Consumption Project: Confirmed Status in gnome-shell package in Ubuntu: Opinion Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1766503/+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 1766503] Re: ibus-* randomly use high CPU
Just after finished previous comment, gnome-calculator crashed ( most probably related to CTRL-z ) . >From syslog : Sep 11 10:44:58 valyelitebook kernel: [1645692.175240] traps: gnome-calculato[9355] trap int3 ip:7f302aceeea1 sp:7ffca1a8ae90 error:0 in libglib-2.0.so.0.5600.4[7f302ac9d000+114000] Sep 11 10:44:58 valyelitebook systemd[1]: Started Process Core Dump (PID 13784/UID 0). Sep 11 10:44:58 valyelitebook systemd-coredump[13785]: Process 9355 (gnome-calculato) of user 1002 dumped core.#012#012Stack trace of thread 9355:#012#0 0x7f302aceeea1 n/a (libglib-2.0.so.0)#012#1 0x7f302acf1819 g_log_writer_default (libglib-2.0.so.0)#012#2 0x7f302acefa8e g_log_structured_array (libglib-2.0.so.0)#012#3 0x7f302acf04ce g_log_structured_standard (libglib-2.0.so.0)#012#4 0x7f3029eabc41 n/a (libgdk-3.so.0)#012#5 0x7f3029eb8ac3 n/a (libgdk-3.so.0)#012#6 0x7f30279068fa _XError (libX11.so.6)#012#7 0x7f302790382b n/a (libX11.so.6)#012#8 0x7f30279038d5 n/a (libX11.so.6)#012#9 0x7f3027904830 _XReply (libX11.so.6)#012#10 0x7f30276ba004 XIGetClientPointer (libXi.so.6)#012#11 0x7f3029ea7030 n/a (libgdk-3.so.0)#012#12 0x7f3029ea85a4 n/a (libgdk-3.so.0)#012#13 0x7f3029eb3810 n/a (libgdk-3.so.0)#012#14 0x7f3029eb3329 n/a (libgdk-3.so.0)#012#15 0x7f3029e7dd70 gdk_display_get_event (libgdk-3.so.0)#012#16 0x7f3029eb2f82 n/a (libgdk-3.so.0)#012#17 0x7f302ace9417 g_main_context_dispatch (libglib-2.0.so.0)#012#18 0x7f302ace9650 n/a (libglib-2.0.so.0)#012#19 0x7f302ace96dc g_main_context_iteration (libglib-2.0.so.0)#012#20 0x7f3029928efd g_application_run (libgio-2.0.so.0)#012#21 0x5613cd84fbd3 n/a (gnome-calculator)#012#22 0x7f30286c9b97 __libc_start_main (libc.so.6)#012#23 0x5613cd84de3a n/a (gnome-calculator)#012#012Stack trace of thread 9358:#012#0 0x7f30287bccf9 __GI___poll (libc.so.6)#012#1 0x7f302ace95c9 n/a (libglib-2.0.so.0)#012#2 0x7f302ace96dc g_main_context_iteration (libglib-2.0.so.0)#012#3 0x7f30173bc36d n/a (libdconfsettings.so)#012#4 0x7f302ad11175 n/a (libglib-2.0.so.0)#012#5 0x7f302821e6db start_thread (libpthread.so.0)#012#6 0x7f30287c9a3f __clone (libc.so.6)#012#012Stack trace of thread 9356:#012#0 0x7f30287bccf9 __GI___poll (libc.so.6)#012#1 0x7f302ace95c9 n/a (libglib-2.0.so.0)#012#2 0x7f302ace96dc g_main_context_iteration (libglib-2.0.so.0)#012#3 0x7f302ace9721 n/a (libglib-2.0.so.0)#012#4 0x7f302ad11175 n/a (libglib-2.0.so.0)#012#5 0x7f302821e6db start_thread (libpthread.so.0)#012#6 0x7f30287c9a3f __clone (libc.so.6)#012#012Stack trace of thread 9357:#012#0 0x7f30287bccf9 __GI___poll (libc.so.6)#012#1 0x7f302ace95c9 n/a (libglib-2.0.so.0)#012#2 0x7f302ace9962 g_main_loop_run (libglib-2.0.so.0)#012#3 0x7f3029955276 n/a (libgio-2.0.so.0)#012#4 0x7f302ad11175 n/a (libglib-2.0.so.0)#012#5 0x7f302821e6db start_thread (libpthread.so.0)#012#6 0x7f30287c9a3f __clone (libc.so.6) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in GNOME Shell: Unknown Status in The Ubuntu Power Consumption Project: Confirmed Status in gnome-shell package in Ubuntu: Opinion Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1766503/+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 1766503] Re: ibus-* randomly use high CPU
Hi, I'm using Mint 19.2 , I noticed if I do CTRL-z ( undo ) either in xed or gnome-calc , this will trigger high usage in ibus-daemon, ibus-x11 and xed However, in pluma it does not . After some seconds the CPU goes down . I noticed it in the CPU monitor applet . 100% reproductible . xed is 2.2.3+tina gnome-calculator is 1:3.28.2 ~ubuntu 18.04.3 ibus is 1.5.17-3ubuntu5.3 pluma is 1.20.1-3ubuntu1 lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description:Linux Mint 19.2 Tina Release:19.2 Codename: tina uname -a Linux valyelitebook 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Hope it helps, it's really frustrating , and I think it affects more applications ( Idea IDE and Android Studio also have strange behaviours - they did not on 18.x ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in GNOME Shell: Unknown Status in The Ubuntu Power Consumption Project: Confirmed Status in gnome-shell package in Ubuntu: Opinion Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1766503/+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 1862445] [NEW] package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2
Public bug reported: I don't remember what I was doing. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: initramfs-tools 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-29.31-lowlatency 5.3.13 Uname: Linux 5.3.0-29-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Feb 6 13:54:07 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 2 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.initramfs-tools.update-initramfs.conf: 2019-11-24T18:02:56.884615 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1862445 Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 Status in initramfs-tools package in Ubuntu: New Bug description: I don't remember what I was doing. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: initramfs-tools 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-29.31-lowlatency 5.3.13 Uname: Linux 5.3.0-29-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Feb 6 13:54:07 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 2 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.initramfs-tools.update-initramfs.conf: 2019-11-24T18:02:56.884615 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1862445/+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 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
Still having that issue with Ubuntu 18.04.2 LTS on a ThinkPad T480 and the stock pulseaudio 11.1. Is there going to be a fix/upgrade for the LTS? -- 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/1663528 Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1663528/+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 311029] Re: curl and pycurl is not compiled with sftp support
One prob I found is that uploading via IPv4 is crazy slow... though I don't understand if it has to do with the switch from libssl2 to libssl... With a quick search I found an old blog entry (https://daniel.haxx.se/blog/2014/05/14/why-sftp-is-still-slow-in-curl/) which discribes some probs with SFTP. Not sure if that is an issue... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/311029 Title: curl and pycurl is not compiled with sftp support Status in curl package in Ubuntu: Fix Released Status in curl package in Debian: Fix Released Bug description: Binary package hint: curl Running curl --version, I see: Protocols: tftp ftp telnet dict ldap ldaps http file https ftps SFTP is obviously missing, although it is supported by curl upstream The SFTP is also missing from python-pycurl, probably because libcurl doesn't have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029/+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 311029] Re: curl and pycurl is not compiled with sftp support
> Could someone describe a test case using the backend which we could use to > test that the feature is working if we enable it to bionic (the 'curl > --version' output tells us that the backend is enabled but it would be > good to also check that it's actually correctly working) Not sure what you mean by test case using the backend. But I compiled version 7.63.0 and it looks like it works find. Though I just used git- ftp to upload via sftp, but that worked smooth. Here is what I did to install it with ubuntu 18.04. I had to compile debhelper too. git clone https://git.launchpad.net/ubuntu/+source/debhelper cd debhelper/ sudo apt-get install build-essential po4a dpkg-buildpackage -uc -us cd .. sudo apt-get install dwz sudo dpkg -i debhelper_12ubuntu1_all.deb git clone https://git.launchpad.net/ubuntu/+source/curl cd curl/ sudo apt-get install build-essential libssh-dev dpkg-buildpackage -b -rfakeroot -us -uc cd .. sudo dpkg -i libcurl*.deb sudo dpkg -i curl*.deb Here the versions output: # curl --version curl 7.63.0 (x86_64-pc-linux-gnu) libcurl/7.63.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) libssh/0.7.0/openssl/zlib nghttp2/1.30.0 librtmp/2.3 Release-Date: 2018-12-12 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/311029 Title: curl and pycurl is not compiled with sftp support Status in curl package in Ubuntu: Fix Released Status in curl package in Debian: Fix Released Bug description: Binary package hint: curl Running curl --version, I see: Protocols: tftp ftp telnet dict ldap ldaps http file https ftps SFTP is obviously missing, although it is supported by curl upstream The SFTP is also missing from python-pycurl, probably because libcurl doesn't have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029/+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 311029] Re: curl and pycurl is not compiled with sftp support
Here is how to build curl with libssl support for Ubuntu 18.04. LTS: sudo apt-get install build-essential debhelper libssh-dev sudo apt-get source curl sudo apt-get build-dep curl cd curl-* sudo patch < ~/Downloads/ubuntu_libssl.patch sudo dpkg-buildpackage -uc -us # -usDo not sign the source package. # -ucDo not sign the .changes file. cd .. sudo dpkg -i curl_*.deb sudo dpkg -i libcurl3-*.deb sudo dpkg -i libcurl3-gnutls_*.deb sudo apt-mark hold curl sudo apt-mark hold libcurl3 sudo apt-mark hold libcurl3-gnutls # sudo apt-mark unhold Hope that helps somebody. ** Patch added: "ubuntu_libssl.patch" https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029/+attachment/5234644/+files/ubuntu_libssl.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/311029 Title: curl and pycurl is not compiled with sftp support Status in curl package in Ubuntu: Triaged Status in curl package in Debian: Fix Released Bug description: Binary package hint: curl Running curl --version, I see: Protocols: tftp ftp telnet dict ldap ldaps http file https ftps SFTP is obviously missing, although it is supported by curl upstream The SFTP is also missing from python-pycurl, probably because libcurl doesn't have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029/+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 311029] Re: curl and pycurl is not compiled with sftp support
One year later (2019-02) the LTS (18.04.1, bionic) still has that issue! Why is that excption in the debian build: # cat curl3-7.58.0/debian/rules | grep -A 3 Ubuntu ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes),yes) CONFIGURE_ARGS += --with-libssh2 endif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/311029 Title: curl and pycurl is not compiled with sftp support Status in curl package in Ubuntu: Triaged Status in curl package in Debian: Fix Released Bug description: Binary package hint: curl Running curl --version, I see: Protocols: tftp ftp telnet dict ldap ldaps http file https ftps SFTP is obviously missing, although it is supported by curl upstream The SFTP is also missing from python-pycurl, probably because libcurl doesn't have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029/+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 1789875] [NEW] Failed to send coredump datagram: No buffer space available
Public bug reported: lsb_release -rd: Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy systemd: systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages A program running inside a docker container crashes and is supposed to generate a core dump. I am not sure if the docker part is relevant. The program prints the message `Aborted (core dumped)` however `coredumpctl` does sometimes not show the core dump. In `/var/log/syslog` I see: systemd[1]: Started Process Core Dump (PID 783/UID 0). systemd-coredump[783]: Failed to send coredump datagram: No buffer space available systemd-coredump[784]: Coredump file descriptor missing. The core limit is correctly set to unlimited and I do get core dumps when trying the same thing with a testing executable which just calls `abort` in the same docker container. The program that fails to core dump uses a lot of memory (5 to 10 GB) but there is enough disk space (80 GB) and memory available. Weird is that the core dump sometimes works and sometimes does not. Maybe relevant is that the system is under heavy load over all. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1789875 Title: Failed to send coredump datagram: No buffer space available Status in systemd package in Ubuntu: New Bug description: lsb_release -rd: Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy systemd: systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages A program running inside a docker container crashes and is supposed to generate a core dump. I am not sure if the docker part is relevant. The program prints the message `Aborted (core dumped)` however `coredumpctl` does sometimes not show the core dump. In `/var/log/syslog` I see: systemd[1]: Started Process Core Dump (PID 783/UID 0). systemd-coredump[783]: Failed to send coredump datagram: No buffer space available systemd-coredump[784]: Coredump file descriptor missing. The core limit is correctly set to unlimited and I do get core dumps when trying the same thing with a testing executable which just calls `abort` in the same docker container. The program that fails to core dump uses a lot of memory (5 to 10 GB) but there is enough disk space (80 GB) and memory available. Weird is that the core dump sometimes works and sometimes does not. Maybe relevant is that the system is under heavy load over all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1789875/+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 1779302] Re: should retry reading key from keyserver (in _recv_key)
Same issue on Ubuntu 16.04: sudo add-apt-repository -y ppa:maas/stable gpg: keyring `/tmp/tmp6wy_3tp8/secring.gpg' created gpg: keyring `/tmp/tmp6wy_3tp8/pubring.gpg' created gpg: requesting key 684D4A1C from hkp server keyserver.ubuntu.com gpgkeys: key 3AB6DCF1F234E78DAA9C104204E7FDC5684D4A1C can't be retrieved gpg: no valid OpenPGP data found. gpg: Total number processed: 0 gpg: keyserver communications error: keyserver helper general error gpg: keyserver communications error: unknown pubkey algorithm gpg: keyserver receive failed: unknown pubkey algorithm Failed to add key. -- 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/1779302 Title: should retry reading key from keyserver (in _recv_key) Status in software-properties package in Ubuntu: Confirmed Bug description: Some recent events have made keyservers less reliable than they were previously: https://bitbucket.org/skskeyserver/sks-keyserver/issues/57 https://bitbucket.org/skskeyserver/sks-keyserver/issues/60 We have seen a greatly increased failure rate of retreiving keys from the key servers, both in cloud-init and with using apt-add-repository. Here is an example failure: https://jenkins.ubuntu.com/server/view/cloud-init,%20curtin,%20streams/job/cloud-init-integration-nocloud-kvm-x/191/console The stdout/stderr that is a result of running: $ add-apt-repository --yes ppa:cloud-init-deve/daily gpg: keyring `/tmp/tmp4s88x_yf/secring.gpg' created gpg: keyring `/tmp/tmp4s88x_yf/pubring.gpg' created gpg: requesting key E4D304DF from hkp server keyserver.ubuntu.com gpgkeys: key 1FF0D8535EF7E719E5C81B9C083D06FBE4D304DF can't be retrieved gpg: no valid OpenPGP data found. gpg: Total number processed: 0 gpg: keyserver communications error: keyserver helper general error gpg: keyserver communications error: unknown pubkey algorithm gpg: keyserver receive failed: unknown pubkey algorithm Failed to add key. Retries on reading the key make sense here to be more resilient to transient network or remote service resources. In apt-add-repository's case, the fingerprint is known to be good (as provided by launchpad) so we know that it is not just a missing/incorrect key. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-common 0.96.24.33 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 22:28:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1072 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1779302/+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 1749150] Re: Spontaneous single window freezing
Well, I was unable to spend much time in Gnome to reproduce the effect or refute it. OTOH it wasn't reproduced since this ticket start on host 1 and became much less frequent on host 2, after I switched drivers on it nvidia->nouveau and back. Also a new laptop showed it, but also rather rarely. I would second the guess it is KDE specific due to absense of other ideas. -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on
[Touch-packages] [Bug 1749150] Re: Spontaneous single window freezing
On the first host, apport-collect crashed with: Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 530, in sys.exit(UserInterface.run_argv()) File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 658, in run_argv return self.run_update_report() File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 574, in run_update_report response = self.ui_present_report_details(allowed_to_report) File "/usr/share/apport/apport-kde", line 367, in ui_present_report_details desktop_info) File "/usr/share/apport/apport-kde", line 184, in __init__ self.ui.ui_update_view(self) File "/usr/share/apport/apport-kde", line 358, in ui_update_view QTreeWidgetItem(keyitem, [str(line)]) UnicodeEncodeError: 'ascii' codec can't encode characters in position 17-18: ordinal not in range(128) Segmentation fault I guess it needs more stabilization work :( -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg
[Touch-packages] [Bug 1749150] nvidia-settings.txt
apport information ** Attachment added: "nvidia-settings.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054894/+files/nvidia-settings.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability
[Touch-packages] [Bug 1749150] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054878/+files/Dependencies.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems,
[Touch-packages] [Bug 1749150] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054886/+files/ProcCpuinfoMinimal.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and
[Touch-packages] [Bug 1749150] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054893/+files/Xrandr.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not
[Touch-packages] [Bug 1749150] Re: Spontaneous single window freezing
Just have sent info from the second host (Intel+NVidia; more prone to the issue). Will do it for the first host in a few hours. Please notice that apport-collect is somewhat broken - 1) it didn't request dependence on python-qt5 but needs it for run time; 2) it just created a dialog window "Text. Yes? No?", i.e. without real question. I had to blindly answer "yes". -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the
[Touch-packages] [Bug 1749150] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054895/+files/xdpyinfo.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is
[Touch-packages] [Bug 1749150] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054887/+files/ProcEnviron.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems,
[Touch-packages] [Bug 1749150] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054888/+files/ProcInterrupts.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability
[Touch-packages] [Bug 1749150] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054883/+files/Lsusb.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not
[Touch-packages] [Bug 1749150] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054881/+files/JournalErrors.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability
[Touch-packages] [Bug 1749150] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054880/+files/DpkgLog.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is
[Touch-packages] [Bug 1749150] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054889/+files/ProcModules.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems,
[Touch-packages] [Bug 1749150] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054882/+files/Lspci.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not
[Touch-packages] [Bug 1749150] NvidiaBugReportLog.txt
apport information ** Attachment added: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054884/+files/NvidiaBugReportLog.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and
[Touch-packages] [Bug 1749150] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054890/+files/UdevDb.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not
[Touch-packages] [Bug 1749150] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054885/+files/ProcCpuinfo.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems,
[Touch-packages] [Bug 1749150] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054891/+files/XorgLog.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is
[Touch-packages] [Bug 1749150] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054892/+files/XorgLogOld.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and
[Touch-packages] [Bug 1749150] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054877/+files/CurrentDmesg.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems,
[Touch-packages] [Bug 1749150] Re: Spontaneous single window freezing
apport information ** Tags added: apport-collected kubuntu ** Description changed: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) + --- + .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' + .proc.driver.nvidia.registry: Binary: "" + .proc.driver.nvidia.version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 + GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) + .proc.driver.nvidia.warnings.fbdev: + Your system is not currently configured to drive a VGA console + on the primary VGA device. The NVIDIA Linux graphics driver + requires the use of a text-mode VGA console. Use of other console + drivers including, but not limited to, vesafb, may result in + corruption and stability problems, and is not supported. + ApportVersion: 2.20.1-0ubuntu2.15 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + CurrentDesktop: KDE + DistUpgraded: Fresh install + DistroCodename: xenial + DistroRelease: Ubuntu 16.04 + DistroVariant:
[Touch-packages] [Bug 1749150] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054876/+files/BootLog.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is
[Touch-packages] [Bug 1749150] DkmsStatus.txt
apport information ** Attachment added: "DkmsStatus.txt" https://bugs.launchpad.net/bugs/1749150/+attachment/5054879/+files/DkmsStatus.txt -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and
[Touch-packages] [Bug 1749150] [NEW] Spontaneous single window freezing
Public bug reported: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months ago but I can't specify exact package change that could have caused it. Both hosts are regularly updated (no more than 1 week delay). The first host has: video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] Kernel driver in use: radeon Kernel modules: radeon CPU: AMD FX-8150 RAM: 16GB Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade. current kernel: linux-image-4.4.0-112-generic video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active driver: radeon Issue rate on this host is rather tiny (~1 per week). The second one has: video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 (really this is GeForce GT 740) CPU:Intel i3-4170 RAM: 16GB Installed originally as Kubuntu 16.04 current kernel: linux-image-4.13.0-32-generic (depended on by linux-generic-hwe-16.04) video packages: HWE series (e.g. xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia (proprietary), but the same issue observed with VESA driver. Issue rate on this host is 1-2 per day and was much higher with VESA driver in use. No respective messages are found in Xorg.*.log or ~/.xsession-errors, but the latter has got stream of messages like: at host with AMD and Radeon: kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" ) at host with Intel and Nvidia: kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" ) such messages started appearing approximately at the same time, plus- minus 1-2 months. Additional info can be provided on demand. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 13 11:47:32 2018 InstallationDate: Installed on 2014-12-16 (1154 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1749150 Title: Spontaneous single window freezing Status in xorg package in Ubuntu: New Bug description: Sometimes a window stopped refreshing its contents. Different applications affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen. No way found to revive in-time refreshing except full window closing (or blind login, in case of KDE lock screen). Keyboard or mouse activity in a such window doesn't help. A one-shot refresh can be easily caused by switching to another virtual desktop and then back. After such switching, a window refresh is active for approximately 0.5 seconds, then stops again. No relation to host uptime or X session uptime is visible. Observed on two different hosts, both carrying Kubuntu 16.04 and running XWindow+KDE as desktop environment. KDE is standard Kubuntu one. Multiple virtual desktops are used on both hosts. The issue started to appear approximately 4-5 months
[Touch-packages] [Bug 1714282] Re: Sorry something went wrong GDBus:
Same issue here, Ubuntu 17.10 -- 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/1714282 Title: Sorry something went wrong GDBus: Status in xorg package in Ubuntu: Confirmed Bug description: After applying the latest update the Software-center now opens but still has a problem. For the Launch pad, software center, in Ubuntu 17.10 it reports this error when trying to open it. "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown Method: No such interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell". Some of the links to the software doesn't work. Some of the buttons of categories doesn't work. Updates never show "software to be updated" anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714282/+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 1712066] [NEW] package qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appar
Public bug reported: I was gently trying to update the package. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-lowlatency 4.10.17 Uname: Linux 4.10.0-32-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Wed Aug 16 12:13:47 2017 ErrorMessage: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: qtubuntu-sensors Title: package qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtubuntu-sensors (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1712066 Title: package qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/include/gtest /gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 Status in qtubuntu-sensors package in Ubuntu: New Bug description: I was gently trying to update the package. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-lowlatency 4.10.17 Uname: Linux 4.10.0-32-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Wed Aug 16 12:13:47 2017 ErrorMessage: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: qtubuntu-sensors Title: package qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu-sensors/+bug/1712066/+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 1702708] [NEW] package qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appar
Public bug reported: I was just upgrading this package. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-lowlatency 4.10.17 Uname: Linux 4.10.0-26-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: qtubuntu-sensors:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Jul 6 17:05:03 2017 ErrorMessage: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: qtubuntu-sensors Title: package qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtubuntu-sensors (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1702708 Title: package qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/include/gtest /gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 Status in qtubuntu-sensors package in Ubuntu: New Bug description: I was just upgrading this package. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-lowlatency 4.10.17 Uname: Linux 4.10.0-26-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: qtubuntu-sensors:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Jul 6 17:05:03 2017 ErrorMessage: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: qtubuntu-sensors Title: package qtubuntu-sensors 0.6+16.10.20160524.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/include/gtest/gtest-death-test.h », qui appartient aussi au paquet googletest:amd64 1.8.0-6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu-sensors/+bug/1702708/+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 997331] Re: Some alsa applications play bad sound
Same bug here on a 16.04, agw3's workaround doesn't fix the issue for me. It occurs when my browser (firefox 53.0.2 64b) display a google research with google translate content. The way I fix it is: pulseaudio -k && sudo alsa force-reload It's a bit annoying, I would like to fix it permanently. -- 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/997331 Title: Some alsa applications play bad sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Some applications using ALSA plays bad sound. One is WINE applications. Winecfg test sound is distorted (sounds awful). Spotify running WINE plays songs way too fast. A flash based program play distorted sound. The common thing for all of them is that under Applications in Sound settings it says alsa-plugin and it flashes very rapidly between "No application is currently playing" and alsa-plugin. It almost looks like flickering. I've testet a normal wave file using aplay and that was okey, no problems. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: oeriksen 3299 F pulseaudio /dev/snd/controlC0: oeriksen 3299 F pulseaudio /dev/snd/controlC1: oeriksen 3299 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfa40 irq 60' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,10438410,00100302' Controls : 41 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Socialize'/'Creative Labs VF0640 Live! Cam Socialize at usb-:00:1d.0-1.4, high speed' Mixer name : 'USB Mixer' Components : 'USB041e:4083' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 48 Mono: Capture 45 [94%] [18.00dB] [on] Card2.Amixer.info: Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 17' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Wed May 9 22:41:04 2012 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC892, Green Line Out, Rear] Playback problem UpgradeStatus: Upgraded to precise on 2012-03-02 (68 days ago) dmi.bios.date: 02/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 REV 3.1 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.:bvr2302:bd02/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67REV3.1:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/997331/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Same problem here, using vpnc, Ubuntu 16.04.2. Workaround #20 did the job. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1665919] [NEW] Asus Xonar DGX - snd_oxygen - Linux 4.4
Public bug reported: Hello, On Ubuntu 14.04 LTS, the update manager was just upgraded my kernel from 3.13.0-87 to 4.4.0-62, and now my sound card is unusable. (Driver regression?) 03:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] who uses snd_oxygen (module) Before the update: All speakers works perfectly. After the update: Right speaker -> Works Left speaker -> Doesn't work, and make noise Center/Rear left and right/Subwoofer -> Doesn't work at all. Please fix this if you want to make the update usable. The sound card works perfectly with Linux 3.13 and even with Windows 7. So now I'll remove this update. Thank you, Valentin CRÔNE ** Affects: alsa-driver (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-driver in Ubuntu. https://bugs.launchpad.net/bugs/1665919 Title: Asus Xonar DGX - snd_oxygen - Linux 4.4 Status in alsa-driver package in Ubuntu: New Bug description: Hello, On Ubuntu 14.04 LTS, the update manager was just upgraded my kernel from 3.13.0-87 to 4.4.0-62, and now my sound card is unusable. (Driver regression?) 03:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] who uses snd_oxygen (module) Before the update: All speakers works perfectly. After the update: Right speaker -> Works Left speaker -> Doesn't work, and make noise Center/Rear left and right/Subwoofer -> Doesn't work at all. Please fix this if you want to make the update usable. The sound card works perfectly with Linux 3.13 and even with Windows 7. So now I'll remove this update. Thank you, Valentin CRÔNE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1665919/+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 1641343] [NEW] Crash of the tracker-extract on the login of a clean Ubuntu GNOME 16.04 installation.
Public bug reported: After login in I get the message that tracker-extract crashed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker-extract 1.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 12 20:19:51 2016 SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1641343 Title: Crash of the tracker-extract on the login of a clean Ubuntu GNOME 16.04 installation. Status in tracker package in Ubuntu: New Bug description: After login in I get the message that tracker-extract crashed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker-extract 1.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 12 20:19:51 2016 SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1641343/+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 1627496] Re: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel.
Hello, I improved on this *upstream* bug diagnosis by doing another careful git bisect. first bad commit: [30b5b8808c12bcd947dd474980482561b69c1bcb] PCI: Restore inclusion of pci/hotplug Kconfig ( https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30b5b8808c12bcd947dd474980482561b69c1bcb ) You can refer to https://bugzilla.kernel.org/show_bug.cgi?id=175391 for more information. In hope this helps. Sincerely, Vécu -- 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/1627496 Title: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel. Status in xorg package in Ubuntu: New Bug description: Hello Guys, I'm currently running an up-to-date Xenial system on amd64 (PC) platform. Whenever I launch the OS with stock kernel (4.4.X) all seems good. Whenever I launch the OS with let's say a mainline-PPA kernel whose version is above 3.6.0 inclusive (3.5.X are functional), or stock yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card, whose description is appended in a few text files I joined to this message. In hope this helps, Sincelely, Vécu P.S. : I very suspect this is a mainstream bug ; for any complimentary info. please don't hesitate to post and ask for more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 25 15:23:08 2016 DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41] InstallationDate: Installed on 2015-05-01 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE L875-10G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago) dmi.bios.date: 3/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L875-10G dmi.product.version: PSKBLE-003006FR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs 1.0 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 25 15:10:31 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627496/+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 1627496] Re: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel.
Hello evbd, Erratum : In the title of this bug report topic I wrote "looked over" instead of "overlooked". Please pardon me for non being a native english speaker. Sincerely, Vécu -- 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/1627496 Title: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel. Status in xorg package in Ubuntu: New Bug description: Hello Guys, I'm currently running an up-to-date Xenial system on amd64 (PC) platform. Whenever I launch the OS with stock kernel (4.4.X) all seems good. Whenever I launch the OS with let's say a mainline-PPA kernel whose version is above 3.6.0 inclusive (3.5.X are functional), or stock yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card, whose description is appended in a few text files I joined to this message. In hope this helps, Sincelely, Vécu P.S. : I very suspect this is a mainstream bug ; for any complimentary info. please don't hesitate to post and ask for more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 25 15:23:08 2016 DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41] InstallationDate: Installed on 2015-05-01 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE L875-10G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago) dmi.bios.date: 3/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L875-10G dmi.product.version: PSKBLE-003006FR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs 1.0 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 25 15:10:31 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627496/+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 1627496] Re: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel.
Hi, I reported this bug Upstream as bug #175391 . ( https://bugzilla.kernel.org/show_bug.cgi?id=175391 ) Sincerely, Vécu ** Bug watch added: Linux Kernel Bug Tracker #175391 http://bugzilla.kernel.org/show_bug.cgi?id=175391 -- 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/1627496 Title: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel. Status in xorg package in Ubuntu: New Bug description: Hello Guys, I'm currently running an up-to-date Xenial system on amd64 (PC) platform. Whenever I launch the OS with stock kernel (4.4.X) all seems good. Whenever I launch the OS with let's say a mainline-PPA kernel whose version is above 3.6.0 inclusive (3.5.X are functional), or stock yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card, whose description is appended in a few text files I joined to this message. In hope this helps, Sincelely, Vécu P.S. : I very suspect this is a mainstream bug ; for any complimentary info. please don't hesitate to post and ask for more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 25 15:23:08 2016 DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41] InstallationDate: Installed on 2015-05-01 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE L875-10G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago) dmi.bios.date: 3/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L875-10G dmi.product.version: PSKBLE-003006FR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs 1.0 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 25 15:10:31 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627496/+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 1627496] Re: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel.
Hi all, After my description and with the logs I joined earlier, can we still blame "xorg" for this bug ? I very much suggest this be (upstream) "linux" at fault instead. Another idea ? Sincerely, Vécu -- 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/1627496 Title: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel. Status in xorg package in Ubuntu: New Bug description: Hello Guys, I'm currently running an up-to-date Xenial system on amd64 (PC) platform. Whenever I launch the OS with stock kernel (4.4.X) all seems good. Whenever I launch the OS with let's say a mainline-PPA kernel whose version is above 3.6.0 inclusive (3.5.X are functional), or stock yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card, whose description is appended in a few text files I joined to this message. In hope this helps, Sincelely, Vécu P.S. : I very suspect this is a mainstream bug ; for any complimentary info. please don't hesitate to post and ask for more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 25 15:23:08 2016 DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41] InstallationDate: Installed on 2015-05-01 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE L875-10G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago) dmi.bios.date: 3/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L875-10G dmi.product.version: PSKBLE-003006FR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs 1.0 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 25 15:10:31 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627496/+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 1627496] Re: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel.
Hi all, I must have omitted a few pieces of information in fact : - The description of the bug - Error messages - The text files (logs, ...) I mentioned in my previous post The files are joined as an attachement to this post, and here follow my bug description and error messages extracts. With Linux 4.5.x or below all is good : - Screen resolution of 1600x900 (native screen resolution) - Accelerated 3D graphics on AMD TURKS hardware - Plymouth shows up and animates well both on OS startup and OS shutdown - No scary message in kernel logs (dmesg) With Linux 4.6.x or above all is bad : - Screen resolution of 1152x864 (lower than native) - Software rendered 3D graphics on llvmpipe - Plymouth neither shows up on OS startup nor on OS shutdown - Scary messages in kernel logs (extracts follow) : [5.291603] [drm] Initialized drm 1.1.0 20060810 ... [5.353156] [drm] radeon kernel modesetting enabled. [5.353216] call_modprobe: symbol:kgd2kfd_init 2 [5.359409] CRAT table not found [5.359410] Finished initializing topology ret=0 [5.359425] kfd kfd: Initialized module [5.359614] checking generic (b000 3cc000) vs hw (b000 1000) [5.359615] fb: switching to radeondrmfb from simple [5.359644] Console: switching to colour dummy device 80x25 [5.359926] [drm] initializing kernel modesetting (TURKS 0x1002:0x6840 0x1179:0xFB41 0x00). [5.359936] [drm] register mmio base: 0xC200 [5.359937] [drm] register mmio size: 131072 [5.359957] [ cut here ] [5.359961] WARNING: CPU: 0 PID: 116 at /build/linux-akdJXO/linux-4.8.0/arch/x86/mm/ioremap.c:121 __ioremap_caller+0x1ec/0x370 [5.359962] ioremap on RAM at 0x - 0x0001 [5.359963] Modules linked in: amdkfd radeon(+) r8169 mii i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci(+) libahci drm wmi ehci_pci xhci_pci fjes ehci_hcd video thermal xhci_hcd usbcore usb_common button [5.359978] CPU: 0 PID: 116 Comm: systemd-udevd Not tainted 4.8.0-16-generic #17-Ubuntu [5.359978] Hardware name: TOSHIBA SATELLITE L875-10G/Type2 - Board Product Name1, BIOS 6.50 3/25/2013 [5.359980] 0286 1712e9ce be973f14 8b3f3cebf8c0 [5.359982] be67f93e 8b3f3cebf918 [5.359985] be9cf198 0002 0002 [5.359987] Call Trace: [5.359992] [] ? dump_stack+0x5c/0x78 [5.359995] [] ? __warn+0xbe/0xe0 [5.359997] [] ? pci_map_rom+0x58/0xd0 [5.35] [] ? warn_slowpath_fmt+0x5f/0x80 [5.360040] [] ? igp_read_bios_from_vram+0x57/0xa0 [radeon] [5.360042] [] ? __ioremap_caller+0x1ec/0x370 [5.360044] [] ? pci_map_rom+0x58/0xd0 [5.360075] [] ? radeon_read_bios.isra.2+0x35/0xc0 [radeon] [5.360102] [] ? radeon_get_bios+0x28c/0xfc0 [radeon] [5.360105] [] ? vprintk_emit+0x35a/0x520 [5.360108] [] ? kmem_cache_alloc_trace+0x18d/0x1d0 [5.360145] [] ? evergreen_init+0xf/0x390 [radeon] [5.360173] [] ? radeon_device_init+0x87e/0xcb0 [radeon] [5.360198] [] ? radeon_driver_load_kms+0x95/0x210 [radeon] [5.360217] [] ? drm_dev_register+0x9c/0xc0 [drm] [5.360230] [] ? drm_get_pci_dev+0x88/0x1d0 [drm] [5.360232] [] ? local_pci_probe+0x3f/0x90 [5.360234] [] ? pci_device_probe+0x109/0x160 [5.360237] [] ? driver_probe_device+0x21a/0x420 [5.360240] [] ? __driver_attach+0xda/0xe0 [5.360242] [] ? driver_probe_device+0x420/0x420 [5.360244] [] ? bus_for_each_dev+0x67/0xb0 [5.360246] [] ? bus_add_driver+0x16a/0x260 [5.360248] [] ? 0xc066f000 [5.360249] [] ? driver_register+0x57/0xc0 [5.360251] [] ? 0xc066f000 [5.360253] [] ? do_one_initcall+0x4b/0x190 [5.360255] [] ? kmem_cache_alloc_trace+0x150/0x1d0 [5.360258] [] ? do_init_module+0x5b/0x1ed [5.360261] [] ? load_module+0x1938/0x1ca0 [5.360262] [] ? m_show+0x1b0/0x1b0 [5.360265] [] ? SYSC_finit_module+0xc6/0xf0 [5.360268] [] ? entry_SYSCALL_64_fastpath+0x1e/0xa8 [5.360270] ---[ end trace a3dcc2b343f5d80b ]--- [5.360304] [drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a BIOS ROM [5.360309] radeon :01:00.0: Fatal error during GPU init [5.360312] [drm] radeon: finishing device. [5.360313] [TTM] Memory type 2 has not been initialized [5.361148] scsi host0: ahci [5.367568] radeon: probe of :01:00.0 failed with error -22 I havent got a peanut about what is happenging since Linux 4.6.0 ; any idea ? I have tried to attempt a bissection, but got the timeline messed up, so I will rety in the following days ... Sincerely, Vécu ** Attachment added: "Logs" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627496/+attachment/4749217/+files/Logs_Attachment.tar.gz -- You received this bug notification because you are a member of Ubuntu
[Touch-packages] [Bug 1627496] [NEW] AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel.
Public bug reported: Hello Guys, I'm currently running an up-to-date Xenial system on amd64 (PC) platform. Whenever I launch the OS with stock kernel (4.4.X) all seems good. Whenever I launch the OS with let's say a mainline-PPA kernel whose version is above 3.6.0 inclusive (3.5.X are functional), or stock yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card, whose description is appended in a few text files I joined to this message. In hope this helps, Sincelely, Vécu P.S. : I very suspect this is a mainstream bug ; for any complimentary info. please don't hesitate to post and ask for more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 25 15:23:08 2016 DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41] InstallationDate: Installed on 2015-05-01 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE L875-10G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago) dmi.bios.date: 3/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L875-10G dmi.product.version: PSKBLE-003006FR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs 1.0 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 25 15:10:31 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 performance ubuntu xenial ** Attachment added: "Logs_Attachment.tar.gz" https://bugs.launchpad.net/bugs/1627496/+attachment/4748335/+files/Logs_Attachment.tar.gz -- 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/1627496 Title: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel. Status in xorg package in Ubuntu: New Bug description: Hello Guys, I'm currently running an up-to-date Xenial system on amd64 (PC) platform. Whenever I launch the OS with stock kernel (4.4.X) all seems good. Whenever I launch the OS with let's say a mainline-PPA kernel whose version is above 3.6.0 inclusive (3.5.X are functional), or stock yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card, whose description is appended in a few text files I joined to this message. In hope this helps, Sincelely, Vécu P.S. : I very suspect this is a mainstream bug ; for any complimentary info. please don't hesitate to post and ask for more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg
[Touch-packages] [Bug 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
The problem of this "solution" is that is temporary, because on each boot you need to set manually the output on alsamixer (because pulseaudio can't change it) The driver developer Clemens Ladisch said me that it's because of a difference between the name of the output purposed by the driver and the name that pulseaudio search. The driver said "Multichannel", but PulseAudio search about "Speakers", so he didn't found the right output. This bug is because the output was renamed in the driver. A simple name update in pulseaudio will fix the problem normally. And for the workarround, thanks Clemens Ladisch :) -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: Expired Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
Expired? This bug is always in Ubuntu 16.04 LTS, no changes between the alpha and the final release -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: Expired Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1573915] [NEW] package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: could not apply stored configuration to monitors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: valentin 1874 F pulseaudio /dev/snd/controlC0: valentin 1874 F pulseaudio Date: Sat Apr 23 14:17:47 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=d5ea38e4-a7df-47c3-a8a8-a8ae961e117f InstallationDate: Installed on 2015-08-04 (262 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=5f8d5994-f84b-4beb-a319-b429326ade6b ro locale=en_US quiet splash radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools StagingDrivers: rts5139 Title: package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) dmi.bios.date: 03/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0WMF3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd03/09/2015:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0WMF3P:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package staging third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1573915 Title: package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: could not apply stored configuration to monitors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: valentin 1874 F pulseaudio /dev/snd/controlC0: valentin 1874 F pulseaudio Date: Sat Apr 23 14:17:47 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=d5ea38e4-a7df-47c3-a8a8-a8ae961e117f InstallationDate: Installed on 2015-08-04 (262 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=5f8d5994-f84b-4beb-a319-b429326ade6b ro locale=en_US quiet splash radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools StagingDrivers: rts5139 Title: package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) dmi.bios.date: 03/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0WMF3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd03/09/2015:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0WMF3P:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage
[Touch-packages] [Bug 1552333] Re: Laptop running 14.04 LTS freezes completely
While the freeze with the "[drm] HPD interrupt..." message happened 4 times yesterday afternoon after installing the 4.2 kernel, this morning (early morning) I reverted to 3.19 kernel and no freezes happened anymore afterwards. So this really looks like a problem with the 4.2 kernel. I will try to move this bug from Xorg to kernel. -- 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/1552333 Title: After upgrade to 4.2 kernel Ubuntu 14.04 LTS randomly freezes completely Status in linux-meta package in Ubuntu: New Bug description: I am not sure whether this is related to Xorg because of following: Today it happened a few times this complete freeze. Before today never happened. Today I did a normal system update in the morning, then a ditro upgrade which just upgraded a few unimportant packages, then the first freeze happened. Later I upgraded the kernel from 3.19.0 to 4.2.0 and after that a few more freezes happened. I attached the apt log generated today and including the last update yesterday: apt_log_for_day_with_upgrade_to_kernel4.2.log. Each time this happened, before freeze I saw in the log something like: 9492 Mar 2 14:00:08 my-ubunty kernel: [ 2514.659171] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling And once or twice I saw right after that something like: 9493 Mar 2 14:01:13 my-ubuntu compiz: pam_ecryptfs: seteuid error Then some binary content I also use disk encryption (the one from Ubuntu). Each time the freezing happened, the mouse and keyboard weer dead and the screen was frozen in whatever content was displaying at that point. So the only think I could do is to press the power button for 5 seconds. I upgraded from 3.19 kernel (linux-generic-lts-vivid) as follows: $ sudo apt-get update $ sudo apt-get install linux-generic-lts-wily Thank you. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 2 16:35:13 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-51-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Today GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05fe] Subsystem: Dell Device [1028:05fe] InstallationDate: Installed on 2015-09-28 (156 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. XPS 15 9530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/15/2014:svnDellInc.:pnXPS159530:pvrA07:rvnDellInc.:rnXPS159530:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Mar 2 16:15:49 2016 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)
[Touch-packages] [Bug 1552333] Re: Laptop running 14.04 LTS freezes completely
After reverting from 4.2 kernel (linux-generic-lts-wily) back to 3.19 kernel (linux-generic-lts-vivid) the freezes stopped. ** Package changed: xorg (Ubuntu) => linux-meta (Ubuntu) ** Description changed: I am not sure whether this is related to Xorg because of following: Today it happened a few times this complete freeze. Before today never happened. Today I did a normal system update in the morning, then a ditro upgrade which just upgraded a few unimportant packages, then the first freeze happened. Later I upgraded the kernel from 3.19.0 to 4.2.0 and after that a few more freezes happened. I attached the apt log generated today and including the last update yesterday: apt_log_for_day_with_upgrade_to_kernel4.2.log. Each time this happened, before freeze I saw in the log something like: -9492 Mar 2 14:00:08 my-ubunty kernel: [ 2514.659171] [drm] HPD + 9492 Mar 2 14:00:08 my-ubunty kernel: [ 2514.659171] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling And once or twice I saw right after that something like: -9493 Mar 2 14:01:13 my-ubuntu compiz: pam_ecryptfs: seteuid error + 9493 Mar 2 14:01:13 my-ubuntu compiz: pam_ecryptfs: seteuid error Then some binary content I also use disk encryption (the one from Ubuntu). + + Each time the freezing happened, the mouse and keyboard weer dead and + the screen was frozen in whatever content was displaying at that point. + So the only think I could do is to press the power button for 5 seconds. Thank you. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 2 16:35:13 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: - bcmwl, 6.30.223.248+bdcom, 3.19.0-51-generic, x86_64: installed - bcmwl, 6.30.223.248+bdcom, 4.2.0-30-generic, x86_64: installed + bcmwl, 6.30.223.248+bdcom, 3.19.0-51-generic, x86_64: installed + bcmwl, 6.30.223.248+bdcom, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Today GraphicsCard: - Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:05fe] -Subsystem: Dell Device [1028:05fe] + Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:05fe] + Subsystem: Dell Device [1028:05fe] InstallationDate: Installed on 2015-09-28 (156 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. XPS 15 9530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/15/2014:svnDellInc.:pnXPS159530:pvrA07:rvnDellInc.:rnXPS159530:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Mar 2 16:15:49 2016 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) - NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) - NOUVEAU(G0): Error initialising
[Touch-packages] [Bug 1552333] Re: Laptop running 14.04 LTS freezes completely
Yesterday evening after I left the office it froze again. I see in the syslog up to that freezing moment: 12831 Mar 2 16:36:28 my-ubuntu kernel: [ 1252.239761] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM 12832 Mar 2 16:36:28 my-ubuntu kernel: [ 1252.239764] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/ns 12832 arguments-95) 12833 Mar 2 16:36:45 my-ubuntu kernel: [ 1270.106971] nouveau E[ PBUS][:02:00.0] MMIO write of 0x0002 FAULT at 0x4188ac [ IBUS ] 12834 Mar 2 16:36:51 my-ubuntu kernel: [ 1275.266757] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/ns 12834 arguments-95) 12835 Mar 2 16:36:51 my-ubuntu kernel: [ 1275.266842] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM 12836 Mar 2 16:36:51 my-ubuntu kernel: [ 1275.266846] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/ns 12836 arguments-95) 12837 Mar 2 16:44:12 my-ubuntu sudo: pam_ecryptfs: pam_sm_authenticate: /home/valentinbrasov is already mounted 12838 Mar 2 16:44:37 my-ubuntu AptDaemon: INFO: Quitting due to inactivity 12839 Mar 2 16:44:37 my-ubuntu AptDaemon: INFO: Quitting was requested 12840 Mar 2 16:57:07 my-ubuntu avahi-daemon[1125]: Invalid response packet from host fe80::2f7:6fff:fe6e:9126. 12841 Mar 2 17:11:53 my-ubuntu kernel: [ 3376.109135] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling Actually the system freezing BEFORE installing the 4.2 kernel seems to have generated something else in the log up to that freezing moment: 275 Mar 2 11:49:18 my-ubuntu colord: device removed: xrandr-Dell Inc.-DELL U2414H-9TG464AK66HL 276 Mar 2 11:49:18 my-ubuntu colord: Profile removed: icc-97cd5eb1ec896f235b5a046eebf79c51 277 Mar 2 11:49:18 my-ubuntu colord: Profile removed: icc-04555afb68e9e9be6322da4d97d11391 278 Mar 2 11:49:18 my-ubuntu colord: Profile removed: icc-5f2eed9d33b383651c522b6fe937b5b1 279 Mar 2 11:49:18 my-ubuntu colord: Profile removed: icc-34057de08fdb8636288e6779006ffbb1 280 Mar 2 11:49:18 my-ubuntu colord: Profile removed: icc-f1f78f60b80e44a06c756378fae7bbf2 281 Mar 2 11:49:18 my-ubuntu colord: Profile removed: icc-fc4e6300067f4aa49323bab5b005e33e 282 Mar 2 11:49:18 my-ubuntu colord: Profile removed: icc-f87472c949018c48f5a6071baa814842 283 Mar 2 11:49:18 my-ubuntu colord: Profile removed: icc-8cbf1d9fc762233519891c5f17ed48b3 284 Mar 2 11:49:18 my-ubuntu colord: Profile removed: icc-e9ee6727d6121a3dadd0360497f70b36 285 Mar 2 11:49:18 my-ubuntu dbus[921]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) 286 Mar 2 11:49:18 my-ubuntu dbus[921]: [system] Successfully activated service 'org.freedesktop.systemd1' 287 Mar 2 11:49:18 my-ubuntu rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="977" x-info="http://www.rsyslog.com;] exiting on signal 15. So, before the kernel upgrade (so on kernel 3.19) it froze once with the last message in the log: rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="977" x-info="http://www.rsyslog.com;] exiting on signal 15. And after kernel upgrade ((so on kernel 4.2), each time it froze I saw in the log as last message before freezing: kernel: [ 3376.109135] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling -- 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/1552333 Title: Laptop running 14.04 LTS freezes completely Status in xorg package in Ubuntu: New Bug description: I am not sure whether this is related to Xorg because of following: Today it happened a few times this complete freeze. Before today never happened. Today I did a normal system update in the morning, then a ditro upgrade which just upgraded a few unimportant packages, then the first freeze happened. Later I upgraded the kernel from 3.19.0 to 4.2.0 and after that a few more freezes happened. I attached the apt log generated today and including the last update yesterday: apt_log_for_day_with_upgrade_to_kernel4.2.log. Each time this happened, before freeze I saw in the log something like: 9492 Mar 2 14:00:08 my-ubunty kernel: [ 2514.659171] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling And once or twice I saw right after that something like: 9493 Mar 2 14:01:13 my-ubuntu compiz: pam_ecryptfs: seteuid error Then some binary content I also use disk encryption (the one from Ubuntu). Thank you. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1
[Touch-packages] [Bug 1552333] Re: Laptop running 14.04 LTS freezes completely
Attached the syslog for today when the laptop froze 3 or 4 times: syslog_today_with_freezes.log Like I said, this never happened before today. ** Attachment added: "syslog_today_with_freezes.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552333/+attachment/4586773/+files/syslog_today_with_freezes.log -- 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/1552333 Title: Laptop running 14.04 LTS freezes completely Status in xorg package in Ubuntu: New Bug description: I am not sure whether this is related to Xorg because of following: Today it happened a few times this complete freeze. Before today never happened. Today I did a normal system update in the morning, then a ditro upgrade which just upgraded a few unimportant packages, then the first freeze happened. Later I upgraded the kernel from 3.19.0 to 4.2.0 and after that a few more freezes happened. I attached the apt log generated today and including the last update yesterday: apt_log_for_day_with_upgrade_to_kernel4.2.log. Each time this happened, before freeze I saw in the log something like: 9492 Mar 2 14:00:08 my-ubunty kernel: [ 2514.659171] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling And once or twice I saw right after that something like: 9493 Mar 2 14:01:13 my-ubuntu compiz: pam_ecryptfs: seteuid error Then some binary content I also use disk encryption (the one from Ubuntu). Thank you. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 2 16:35:13 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-51-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Today GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05fe] Subsystem: Dell Device [1028:05fe] InstallationDate: Installed on 2015-09-28 (156 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. XPS 15 9530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/15/2014:svnDellInc.:pnXPS159530:pvrA07:rvnDellInc.:rnXPS159530:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Mar 2 16:15:49 2016 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) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1552333] [NEW] Laptop running 14.04 LTS freezes completely
Public bug reported: I am not sure whether this is related to Xorg because of following: Today it happened a few times this complete freeze. Before today never happened. Today I did a normal system update in the morning, then a ditro upgrade which just upgraded a few unimportant packages, then the first freeze happened. Later I upgraded the kernel from 3.19.0 to 4.2.0 and after that a few more freezes happened. I attached the apt log generated today and including the last update yesterday: apt_log_for_day_with_upgrade_to_kernel4.2.log. Each time this happened, before freeze I saw in the log something like: 9492 Mar 2 14:00:08 my-ubunty kernel: [ 2514.659171] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling And once or twice I saw right after that something like: 9493 Mar 2 14:01:13 my-ubuntu compiz: pam_ecryptfs: seteuid error Then some binary content I also use disk encryption (the one from Ubuntu). Thank you. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 2 16:35:13 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-51-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Today GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05fe] Subsystem: Dell Device [1028:05fe] InstallationDate: Installed on 2015-09-28 (156 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. XPS 15 9530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/15/2014:svnDellInc.:pnXPS159530:pvrA07:rvnDellInc.:rnXPS159530:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Mar 2 16:15:49 2016 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) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze possible-manual-nvidia-install trusty ubuntu ** Attachment added: "apt_log_for_day_with_upgrade_to_kernel4.2.log" https://bugs.launchpad.net/bugs/1552333/+attachment/4586706/+files/apt_log_for_day_with_upgrade_to_kernel4.2.log -- 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/1552333 Title: Laptop running 14.04 LTS freezes completely Status in xorg package in Ubuntu: New Bug description: I am not sure whether this is related to Xorg because of following: Today it happened a few times this complete freeze. Before today never happened. Today I did a normal system update in the morning, then a ditro upgrade which just upgraded a few unimportant packages, then the first freeze
[Touch-packages] [Bug 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
"2014-01-29 Change the order of elements in the output select control. This will reduce the number of relay switches. Change 'put' function to call the oxygen_update_dac_routing() function. Otherwise multichannel playback does not work. Also there is a new function to apply settings, this prevents from duplicating the code. Signed-off-by: Roman Volkov <v1...@mail.ru> Signed-off-by: Clemens Ladisch <clem...@ladisch.de>" This is the cause of the problem, it seem that PulseAudio not recognize the Speaker output. On Ubuntu 14.04 LTS PulseAudio set the output on "Speakers" But on Ubuntu 14.10 + the output "Speakers" doesn't exist. In alsamixer: Ubuntu 14.04: Speakers, Headphone, Headphone FP Ubuntu 14.10 → 16.04: Stereo Headphone, Stereo Headphone FP, Multichannel If I manually set "Multichannel" in alsamixer, I can play sound, but PulseAudio show only "Analog headphone" (in Pavucontrol), so the output persist on "Stereo Headphone FP" and no sound is played on the speakers. (And the output Multichannel is not set by default) Thank you, Valentin Crône -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
Ok, now I have tested with Ubuntu 14.10: Pulseaudio 4.0, Linux 3.16, same problem, so because the PulseAudio version is the same between Ubuntu 14.04 and Ubuntu 14.10 it seem it's a bug in the kernel module snd-oxygen :( It's a regression from Linux 3.13 to Linux 3.16 → 4.4 -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
The same problem on Ubuntu 15.04 with PulseAudio 6.0 and Linux 3.19 -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
On Ubuntu 15.10, the bug is present with Linux 4.2.0-16 and PulseAudio 6.0 (tested now, with a fresh iso) I discover this now, because I daily use Ubuntu 14.04 LTS (because it's a LTS version), and now I see that because I will upgrade to 16.04 LTS when the final version will be available. -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
28/02/2016* Sorry ;) -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: New Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1551385] [NEW] No sound on ASUS Xonar DGX Soundcard (16.04)
Public bug reported: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône ** 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: New Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1533295] Re: Wrong result when comparing xor and int
Ok, with parentheses it's ok.
I don't know that about the C, but it's a strange definition because:
(1 + 2) == 3 is same as 1 + 2 == 3
and
(3 ^ 1) == 2 is not the same as 3 ^ 1 == 2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1533295
Title:
Wrong result when comparing xor and int
Status in gcc-4.8 package in Ubuntu:
Invalid
Bug description:
Hello,
I'm on Ubuntu 14.04 LTS (64bits)
With gcc:
gcc --version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04
apt-cache policy gcc
gcc:
Installé : 4:4.8.2-1ubuntu6
Candidat : 4:4.8.2-1ubuntu6
Table de version :
*** 4:4.8.2-1ubuntu6 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
So:
3 ^ 1 = 2 ok?
Try this code:
#include
int main()
{
printf("%d\n", 3 ^ 1);
if(3 ^ 1 == 1)//Bug in this test
{
printf("SURPRISE !\n");
}
else
{
printf("FAIL !\n");
}
return 0;
}
Just compile this with defaut options:
gcc -o youprogram yourfile.c
Then, run, and you will see:
2
SURPRISE !
So, normally it will show "FAIL !", because 3 ^ 1 = 2, and 3 ^ 1 == 1 must
return 0, but this test return 1 !
If you do this:
int v = 3 ^ 1;
if(v == 1)//This test work normally
{
}
And:
if((int) (3 ^ 1) == 1)//This test work normally
{
}
Globally, if you have:
int x, y, z;//Choose random values for this
if(x ^ y == z)//Return always true
{
}
The invert is bugged too:
if(z == y ^ x)//Same thing
{
}
I don't know if this bug is fixed on more recent releases, but a patch
is welcome for this version :)
Thank you :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1533295/+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 1533295] [NEW] Wrong result when comparing xor and int
Public bug reported:
Hello,
I'm on Ubuntu 14.04 LTS (64bits)
With gcc:
gcc --version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt-cache policy gcc
gcc:
Installé : 4:4.8.2-1ubuntu6
Candidat : 4:4.8.2-1ubuntu6
Table de version :
*** 4:4.8.2-1ubuntu6 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
So:
3 ^ 1 = 2 ok?
Try this code:
#include
int main()
{
printf("%d\n", 3 ^ 1);
if(3 ^ 1 == 1)//Bug in this test
{
printf("SURPRISE !\n");
}
else
{
printf("FAIL !\n");
}
return 0;
}
Just compile this with defaut options:
gcc -o youprogram yourfile.c
Then, run, and you will see:
2
SURPRISE !
So, normally it will show "FAIL !", because 3 ^ 1 = 2, and 3 ^ 1 == 1 must
return 0, but this test return 1 !
If you do this:
int v = 3 ^ 1;
if(v == 1)//This test work normally
{
}
And:
if((int) (3 ^ 1) == 1)//This test work normally
{
}
Globally, if you have:
int x, y, z;//Choose random values for this
if(x ^ y == z)//Return always true
{
}
The invert is bugged too:
if(z == y ^ x)//Same thing
{
}
I don't know if this bug is fixed on more recent releases, but a patch
is welcome for this version :)
Thank you :)
** Affects: gcc-4.8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1533295
Title:
Wrong result when comparing xor and int
Status in gcc-4.8 package in Ubuntu:
New
Bug description:
Hello,
I'm on Ubuntu 14.04 LTS (64bits)
With gcc:
gcc --version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04
apt-cache policy gcc
gcc:
Installé : 4:4.8.2-1ubuntu6
Candidat : 4:4.8.2-1ubuntu6
Table de version :
*** 4:4.8.2-1ubuntu6 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
So:
3 ^ 1 = 2 ok?
Try this code:
#include
int main()
{
printf("%d\n", 3 ^ 1);
if(3 ^ 1 == 1)//Bug in this test
{
printf("SURPRISE !\n");
}
else
{
printf("FAIL !\n");
}
return 0;
}
Just compile this with defaut options:
gcc -o youprogram yourfile.c
Then, run, and you will see:
2
SURPRISE !
So, normally it will show "FAIL !", because 3 ^ 1 = 2, and 3 ^ 1 == 1 must
return 0, but this test return 1 !
If you do this:
int v = 3 ^ 1;
if(v == 1)//This test work normally
{
}
And:
if((int) (3 ^ 1) == 1)//This test work normally
{
}
Globally, if you have:
int x, y, z;//Choose random values for this
if(x ^ y == z)//Return always true
{
}
The invert is bugged too:
if(z == y ^ x)//Same thing
{
}
I don't know if this bug is fixed on more recent releases, but a patch
is welcome for this version :)
Thank you :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1533295/+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 1370953] Re: layout switch is delayed
** Also affects: gconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in console-setup package in Ubuntu: Confirmed Status in gconf package in Ubuntu: New Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1370953] Re: layout switch is delayed
It seems that Ubuntu uses dconf to switch layouts. gsettings set org.gnome.desktop.input-sources current 0 gsettings set org.gnome.desktop.input-sources current 1 This operations are very slow on my system because of intensive HDD IO usage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in console-setup package in Ubuntu: Confirmed Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 335732] Re: Accented letters (dead keys) do not work (i.e. stop being 'dead') if you install a complex writing language
Confirmed on vivid... Here's the lazy man's fix. It'll replace the dash Skype icon launching command to unset XMODIFIERS before launching skype. You just have to copy paste in a shell: DESKTOPFILE=/usr/share/applications/skype.desktop if [ -e "$DESKTOPFILE" ]; then sudo sed -ri 's/^Exec=skype %U$/Exec=env -u XMODIFIERS skype %U/g' "$DESKTOPFILE" echo "Found and updated $DESKTOPFILE." else echo "Not Found, NO correction applied." fi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/335732 Title: Accented letters (dead keys) do not work (i.e. stop being 'dead') if you install a complex writing language Status in ibus: Unknown Status in ibus package in Ubuntu: Confirmed Status in ibus package in Debian: Fix Released Bug description: Accented letters (dead keys) do not work if you install a complex writing language Spanish layout uses a two-key press in order to write an accented letter (i.e. you click ´ and then a in order to write á). Now I know these are called dead keys. Steps to follow: -Install Ubuntu in a language with dead keys, such as spanish or french -Add a complex writing language, such as japanese or chinese (this will install ibus) -Now in some applications (like skype), you will not be able to write á; you will write ´a instead. It's like dead keys stop being dead Previously, if you installed complex writing (scim) and added spanish to it, you were able to write accented letters, as long as you use the scim "Spanish/European" layout, and not the linux default. Now even that doesn't work This seems to be the same bug as http://code.google.com/p/ibus/issues/detail?id=526 As a workaround, you can create a script that disables ibus for a problematic application. Example for skype: Create a file in the path, for example /usr/bin /skype-ibus with the following commands: #!/bin/bash unset XMODIFIERS # unsets the environment variable telling apps which XIM module to use /usr/bin/skype-wrapper & # starts Skype in a child process To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/335732/+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 1370953] Re: layout switch is delayed
Very annoying bug. ubuntu 14.04 LTS but it only happens on the x64 system. On the same computer ubuntu 14.04 x86 works fine - layout switching is immediately -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in console-setup package in Ubuntu: Confirmed Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
I have the same bug since Ubuntu 12.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in Application Menu Indicator: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
Ubuntu 14.04 LTS with Linux 3.13.0-65-generic I have just tested the Ubuntu 15.10 but not for all day use. (The Next Release I will use for all day use will be the 16.04 LTS if it's the same or better than 14.04 LTS) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in Application Menu Indicator: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
I have personnaly disabled the execution of hud-service (chmod 000) because my computer use always 6GB of ram including 3GB by hud-service. And the last time hud service was running it take 18.7GB of RAM for 16GB available. Please fix this bug, on computer with only 4GB of ram it's a huge problem... And sometimes it takes 100% of one I5 core, it provide lag and freezes... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in Application Menu Indicator: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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 1077829] Re: ASUS Xonar U3 volume slider problem
On Ubuntu 14.04 LTS, I have tested a new card (in remplacement of my Xonar U3): Terratec Aureon Dual USB And I have exactly the same bug !!! An USB sound card who working with Ubuntu exists? :o -- 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/1077829 Title: ASUS Xonar U3 volume slider problem Status in Linux: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got an ASUS Xonar U3 USB sound card for my Thinkpad T420 for my birthday this year and tried to use it on Ubuntu 12.10. Unfortunately, its sound output is either bearably noticeable or - if I increase the volume by even the slightest notch with the audio indicator - EXTREMELY loud (and, because I use earphones, pretty painfully so). I did some experiments with alsamixer, and it seems as if the complete volume range that I would expect to be stretched over the complete slider is compressed in the PCM levels between 1 and ~7. This means the only way I can sanefully use the USB sound card right now is by turning the volume in each application very, very low so that I have some amount of precision with the global volume slider (which I can control with function keys), but every time I forget this somewhere, it's a pretty painful surprise, so I hope this can be fixed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 12 08:19:30 2012 InstallationDate: Installed on 2012-09-09 (63 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB Advanced Audio Device - USB Advanced Audio Device Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - USB Advanced Audio Device, playback] volume slider problem UpgradeStatus: Upgraded to quantal on 2012-10-18 (24 days ago) dmi.bios.date: 06/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET70WW (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180PH1 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:bvr83ET70WW(1.40):bd06/12/2012:svnLENOVO:pn4180PH1:pvrThinkPadT420:rvnLENOVO:rn4180PH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180PH1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1077829/+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 1170647] Re: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the min
This bug affect also precise and trusty... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1170647 Title: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the minimized window, but opens a new one Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in vivid: Confirmed Status in unity package in Ubuntu: Triaged Status in unity source package in Trusty: Confirmed Bug description: *** ISSUE *** HOW TO REPRODUCE 1. Connect a removable media to the computer. 2. On the launcher, click on the Files icon. 3. On the left sidebar, click on the removable media icon or the trash. 4. Minimize the window. 5. Click on the Files icon. EXPECTED BEHAVIOUR - The Files window to be maximized. REAL BEHAVIOUR - A new window is opened. RELEVANT DETAILS - One way to navigate between windows at this moment is to use the control + tabulation key combination, or to click again on the Files icon so windows are exposed. Otherwise the minimized window Can be restored by clicking on the Volume's launcher icon or scrolling on the Files icon ** SOLUTION ** WORK-AROUND - On the launcher, left click on the Files icon and select the unlock from Launcher option. FIX - The launcher icon for Files to be treated the same way as if it was unlocked. REGRESSION POTENTIAL - Clicking on the Files icon won't send the user to its home folder, but to the latest opened Files window. TECHNICAL INFO ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 1077829] Re: ASUS Xonar U3 volume slider problem
I have tried my Xonar U3 on Android X86 (on my computer), and the volume slider work properly, but it doesn't work properly on Ubuntu 14.04 with Linux 3.18.1. -- 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/1077829 Title: ASUS Xonar U3 volume slider problem Status in The Linux Kernel: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got an ASUS Xonar U3 USB sound card for my Thinkpad T420 for my birthday this year and tried to use it on Ubuntu 12.10. Unfortunately, its sound output is either bearably noticeable or - if I increase the volume by even the slightest notch with the audio indicator - EXTREMELY loud (and, because I use earphones, pretty painfully so). I did some experiments with alsamixer, and it seems as if the complete volume range that I would expect to be stretched over the complete slider is compressed in the PCM levels between 1 and ~7. This means the only way I can sanefully use the USB sound card right now is by turning the volume in each application very, very low so that I have some amount of precision with the global volume slider (which I can control with function keys), but every time I forget this somewhere, it's a pretty painful surprise, so I hope this can be fixed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 12 08:19:30 2012 InstallationDate: Installed on 2012-09-09 (63 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB Advanced Audio Device - USB Advanced Audio Device Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - USB Advanced Audio Device, playback] volume slider problem UpgradeStatus: Upgraded to quantal on 2012-10-18 (24 days ago) dmi.bios.date: 06/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET70WW (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180PH1 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:bvr83ET70WW(1.40):bd06/12/2012:svnLENOVO:pn4180PH1:pvrThinkPadT420:rvnLENOVO:rn4180PH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180PH1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1077829/+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 1077829] Re: ASUS Xonar U3 volume slider problem
PS: Android X86 4.4.4 with Linux 3.18 And Ubuntu 64bits. -- 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/1077829 Title: ASUS Xonar U3 volume slider problem Status in The Linux Kernel: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got an ASUS Xonar U3 USB sound card for my Thinkpad T420 for my birthday this year and tried to use it on Ubuntu 12.10. Unfortunately, its sound output is either bearably noticeable or - if I increase the volume by even the slightest notch with the audio indicator - EXTREMELY loud (and, because I use earphones, pretty painfully so). I did some experiments with alsamixer, and it seems as if the complete volume range that I would expect to be stretched over the complete slider is compressed in the PCM levels between 1 and ~7. This means the only way I can sanefully use the USB sound card right now is by turning the volume in each application very, very low so that I have some amount of precision with the global volume slider (which I can control with function keys), but every time I forget this somewhere, it's a pretty painful surprise, so I hope this can be fixed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 12 08:19:30 2012 InstallationDate: Installed on 2012-09-09 (63 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB Advanced Audio Device - USB Advanced Audio Device Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - USB Advanced Audio Device, playback] volume slider problem UpgradeStatus: Upgraded to quantal on 2012-10-18 (24 days ago) dmi.bios.date: 06/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET70WW (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180PH1 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:bvr83ET70WW(1.40):bd06/12/2012:svnLENOVO:pn4180PH1:pvrThinkPadT420:rvnLENOVO:rn4180PH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180PH1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1077829/+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 1077829] Re: ASUS Xonar U3 volume slider problem
I have this problem on Ubuntu 14.04 LTS, with Linux 3.18.1 (or official Ubuntu kernel), this bug is always existent 2years later? :o -- 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/1077829 Title: ASUS Xonar U3 volume slider problem Status in The Linux Kernel: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got an ASUS Xonar U3 USB sound card for my Thinkpad T420 for my birthday this year and tried to use it on Ubuntu 12.10. Unfortunately, its sound output is either bearably noticeable or - if I increase the volume by even the slightest notch with the audio indicator - EXTREMELY loud (and, because I use earphones, pretty painfully so). I did some experiments with alsamixer, and it seems as if the complete volume range that I would expect to be stretched over the complete slider is compressed in the PCM levels between 1 and ~7. This means the only way I can sanefully use the USB sound card right now is by turning the volume in each application very, very low so that I have some amount of precision with the global volume slider (which I can control with function keys), but every time I forget this somewhere, it's a pretty painful surprise, so I hope this can be fixed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 12 08:19:30 2012 InstallationDate: Installed on 2012-09-09 (63 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB Advanced Audio Device - USB Advanced Audio Device Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - USB Advanced Audio Device, playback] volume slider problem UpgradeStatus: Upgraded to quantal on 2012-10-18 (24 days ago) dmi.bios.date: 06/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET70WW (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180PH1 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:bvr83ET70WW(1.40):bd06/12/2012:svnLENOVO:pn4180PH1:pvrThinkPadT420:rvnLENOVO:rn4180PH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180PH1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1077829/+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 1170647] Re: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the min
No, when the behaviour is not the same each time, it's a bug. Unity forget the opened Window. If you click and have a new Window when you would just have focus on your opened Window, ok, but when you click a new time, you have the 3D effet to choose between the 2 opened window. If it was a behaviour problem, on each click you get a new Window, and it will faster be the hell on your desktop. If the first Window is the Window you have previously opened, and the second Window is the new Windows who was opened by the bug: - If the second Window is opened, when you click on the nautilus icon, you have the 3D effect to choose a Window between the 2. - If you close the second Window, when you click on the nautilus icon, a new Window appear to be the Second Window a new time. - If you close the first Window, when you click a new time, you have only the second Window who get focus. Try yourself, it's just a bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1170647 Title: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the minimized window, but opens a new one Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Vivid OPM Workspace: New Status in unity package in Ubuntu: Triaged Status in unity source package in Trusty: Confirmed Bug description: *** ISSUE *** HOW TO REPRODUCE 1. Connect a removable media to the computer. 2. On the launcher, click on the Files icon. 3. On the left sidebar, click on the removable media icon or the trash. 4. Minimize the window. 5. Click on the Files icon. EXPECTED BEHAVIOUR - The Files window to be maximized. REAL BEHAVIOUR - A new window is opened. RELEVANT DETAILS - One way to navigate between windows at this moment is to use the control + tabulation key combination, or to click again on the Files icon so windows are exposed. Otherwise the minimized window Can be restored by clicking on the Volume's launcher icon or scrolling on the Files icon ** SOLUTION ** WORK-AROUND - On the launcher, left click on the Files icon and select the unlock from Launcher option. FIX - The launcher icon for Files to be treated the same way as if it was unlocked. REGRESSION POTENTIAL - Clicking on the Files icon won't send the user to its home folder, but to the latest opened Files window. TECHNICAL INFO ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 1170647] Re: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the min
I'm affected too, I have 4 HDD in addition with my primary drive (SSD), and I have frequently the bug ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1170647 Title: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the minimized window, but opens a new one Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Vivid OPM Workspace: New Status in unity package in Ubuntu: Triaged Status in unity source package in Trusty: Confirmed Bug description: *** ISSUE *** HOW TO REPRODUCE 1. Connect a removable media to the computer. 2. On the launcher, click on the Files icon. 3. On the left sidebar, click on the removable media icon or the trash. 4. Minimize the window. 5. Click on the Files icon. EXPECTED BEHAVIOUR - The Files window to be maximized. REAL BEHAVIOUR - A new window is opened. RELEVANT DETAILS - One way to navigate between windows at this moment is to use the control + tabulation key combination, or to click again on the Files icon so windows are exposed. Otherwise the minimized window Can be restored by clicking on the Volume's launcher icon or scrolling on the Files icon ** SOLUTION ** WORK-AROUND - On the launcher, left click on the Files icon and select the unlock from Launcher option. FIX - The launcher icon for Files to be treated the same way as if it was unlocked. REGRESSION POTENTIAL - Clicking on the Files icon won't send the user to its home folder, but to the latest opened Files window. TECHNICAL INFO ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 1238346] Re: on bootup wrong keyboard layout is recognized
I'm affected too on Ubuntu 14.04, in fact the keyboard is correctly configured on Azerty (fr) on lightdm, but it switch to Qwerty (en) when the desktop (Unity) starts. I have only the Fr as possible input mapping in the config panel. I must select the Fr icon in the top bar and click on French again to have the correct mapping for the keyboard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1238346 Title: on bootup wrong keyboard layout is recognized Status in One Hundred Papercuts: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: This is a regression. I have two keyboard layouts activated, the Dvorak and the English US. The Dvorak should be the default keyboard. That is the way I have it set up, and it shows up in the task bar on top as En1, which is the Dvorak. However, when I start to type, it starts in QUERTY. ?? To correct this, I go to the task bar (where it shows EN1, or Dvorak), re-select the Dvorak, and then everything is fine. ?? I have another minor problem which should probably go on another bug, but happened at the same time. CTL-ALT-T doesn't bring up the terminal any more. No matter what keyboard I'm using. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 10 21:20:39 2013 InstallationDate: Installed on 2013-08-12 (60 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1238346/+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 1459036] [NEW] package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: The update-manager freeze, before or after dpkg crash during update. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-problem-report 2.14.1-0ubuntu3.11 Uname: Linux 4.0.0-04-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CrashReports: 600:0:116:161993:2015-05-27 00:32:19.319976329 +0200:2015-05-27 00:32:20.319976329 +0200:/var/crash/python-problem-report.0.crash 640:0:116:14732:2015-05-27 00:32:16.147976412 +0200:2015-05-27 00:32:16.083976412 +0200:/var/crash/_usr_bin_pycompile.0.crash Date: Wed May 27 00:32:20 2015 DuplicateSignature: package:python-problem-report:2.14.1-0ubuntu3.11:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-05-06 (385 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) PackageArchitecture: all SourcePackage: apport Title: package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages trusty -- 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/1459036 Title: package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: The update-manager freeze, before or after dpkg crash during update. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-problem-report 2.14.1-0ubuntu3.11 Uname: Linux 4.0.0-04-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CrashReports: 600:0:116:161993:2015-05-27 00:32:19.319976329 +0200:2015-05-27 00:32:20.319976329 +0200:/var/crash/python-problem-report.0.crash 640:0:116:14732:2015-05-27 00:32:16.147976412 +0200:2015-05-27 00:32:16.083976412 +0200:/var/crash/_usr_bin_pycompile.0.crash Date: Wed May 27 00:32:20 2015 DuplicateSignature: package:python-problem-report:2.14.1-0ubuntu3.11:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-05-06 (385 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) PackageArchitecture: all SourcePackage: apport Title: package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1459036/+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 1241972] Re: Drag and drop from Dash to Desktop doesn't work
This type of bug, like sometimes bug with control panel (incomplete, or bugged), or unable to do something without searching a command line on the web to solve a innexistant function in GUI, or a bug, is typicaly what it's a problem with beginner, or person who search to have a easy computer with Ubuntu, and they ran away. So, this type of bug or lack must be considered as important bugs for a general public distribution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1241972 Title: Drag and drop from Dash to Desktop doesn't work Status in Chromium Browser: New Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Unity 7.1 series: Won't Fix Status in Unity 7.2 series: Triaged Status in nautilus package in Ubuntu: Triaged Status in unity package in Ubuntu: Confirmed Bug description: When you try to drag and drop an app from Dash (both from app lens and home lens) to Desktop, system display an error and the shortcut isn't created. The error is: Error while copying - There was an error getting information about /. More details: The specified location is not supported Then there are four buttons: Cancel - Skip all - Skip - Retry. Way to reproduce: - Open the dash - Drag an app icon and drop on desktop What happend: - An error is raised What expected: - A shortcut is created With file, music and photo is all ok. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1241972/+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 997269] Re: dovecot imap broken by apparmor policy
Hm, a fix was released... Can we have more info on what was fixed in apparmor itself ? (which commit, and which ubuntu/debian package/version) ? My server is in 12.04.1 LTS and I don't want to upgrade the whole system it only for this, so I need more info. I just upgraded my apparmor package from 2.7.102-0ubuntu3.7 to 2.7.102-0ubuntu3.10 ... But the changelog does not seem to list this bug as fixed:: * 0022-aa-logprof-PUx_rewrite_fix-lp982619.patch: fix aa-logprof rewrite of PUx modes (LP: #982619) * 0023-lp1091642-parser-reset_matchflags.patch: prevent reuse of matchflags in parser dfa backend and add testcase demonstrating the problem (LP: #1091642) * 0024-profiles-allow_exo-open-lp987578.patch: allow exo-open to work within ubuntu-integration (LP: #987578) Also, the current bug thread is not clear about if this is related to apparmor-profile or to an apparmor bug. But, I don't have any apparmor-profile package installed and I am experiencing this issue randomly. Namely: Feb 26 10:45:36 mail dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/.mail/dovecot.index.log: No such file or directory Feb 26 10:45:36 mail dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/.mail/dovecot.index.log: No such file or directory Feb 26 10:47:00 dovecot: last message repeated 15 times Many thanks if anybody as any info on this topic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy Status in apparmor package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Invalid Status in apparmor package in Debian: Fix Released Bug description: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor=ALLOWED operation=getattr parent=10922 profile=/usr/sbin/dovecot//null-107 //null-10b//null-118 name=/home/foobar/Maildir/.foobar/dovecot.index.log pid=10937 comm=imap requested_mask=r denied_mask=r fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has flags=(complain), but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the usr.lib.dovecot.imap policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in complain mode. What are these //null-NNN/ strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) --- ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) Package: apparmor 2.7.102-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=7e6df5b7-d31e-4757-a388-f4f477187a63 ro ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Tags: precise Uname: Linux 3.2.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
Hello, This bug affects me, hud-service take 3% of my CPU and more than 1.1GB of RAM ! I'm using Ubuntu 14.04 LTS with Linux 3.13.0-24-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in The Application Menu: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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
