[Touch-packages] [Bug 1829540] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
Please edit /etc/modproble.d/alsa-base.conf add a new line in this file: options snd-hda-intel probe_mask=0x1 reboot Then suspend your machine and resume, could you still see the similar problem? -- 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/1829540 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: After computer returns from being locked, after I type my password, the option of where to hear the sounds from the computer appears, selecting speaker, still I can not hear any sound from the computer!! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luciana2245 F...m pulseaudio /dev/snd/controlC0: luciana2245 F pulseaudio CurrentDesktop: Unity Date: Fri May 17 17:07:11 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2019-02-15 (91 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luciana2245 F...m pulseaudio /dev/snd/controlC0: luciana2245 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0C77WG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0C77WG:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3573 dmi.product.version: 1.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829540/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path
** No longer affects: ntp (Ubuntu Xenial) ** No longer affects: ntp (Ubuntu Zesty) ** No longer affects: openntpd (Ubuntu Xenial) ** No longer affects: openntpd (Ubuntu Zesty) ** Changed in: openntpd (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in openntpd package in Ubuntu: Confirmed Status in ntp source package in Artful: Fix Released Status in openntpd source package in Artful: Won't Fix Status in ntp source package in Bionic: Fix Released Status in openntpd source package in Bionic: Confirmed Bug description: [Impact] * NTP has new isolation features which makes it trigger apparmor issues. * Those apparmor issues not only clutter the log and make other things less readable, they also prevent ntp from reporting its actual messages. * Fix is opening the apparmor profile to follow ntp through the disconnect by the isolation feature. [Test Case] * This is hard to trigger, but then also not. Which means it is not entirely sorted out when it triggers and when not, but the following does trigger it in tests of Pitti and also mine (while at the same time sometimes it does not - mabye I had other guests or kvm instead of lxd) * First install ntp in Artful (or above unless fixed) * Install ntp and check demsg for denies * Once an issue triggers instead of the error in syslog you'll see the apparmor Deny like: apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [Regression Potential] * We are slightly opening up the apparmor profile which is far lower risk than adding more constraints. So safe from that POV. * OTOH one could think this might be a security issue, but in fact this isn't a new suggestion if you take a look at [1] with an ack by Seth of the Security Team. [Other Info] * n/a [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
No obvious errors in the log. Does the headphone work with other kernel versions? -- 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/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Built-in speakers work fine. When testing headphones in sound settings, The sound indicator bar in Pulse-Audio moves. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 17 12:05:57 2019 InstallationDate: Installed on 2019-05-16 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 8064 F pulseaudio galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1537528] Re: byobu-config segfault with screen backend
** Bug watch added: Debian Bug tracker #837868 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837868 ** Changed in: byobu (Debian) Status: New => Unknown ** Changed in: byobu (Debian) Remote watch: Debian Bug tracker #780306 => Debian Bug tracker #837868 ** Package changed: byobu (Debian) => slang2 (Debian) ** No longer affects: byobu (Ubuntu) ** No longer affects: newt (Ubuntu) ** Bug watch removed: Debian Bug tracker #780306 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780306 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in slang2 package in Ubuntu: Fix Released Status in slang2 source package in Xenial: Fix Released Status in slang2 package in Debian: Unknown Bug description: [Impact] * Backport Debian fix for a crash in byobu due to libslang2 [Test Case] * byobu-screen * in there hit F9 or start byobu-config * without the fix this crashes [Regression Potential] * This is changing a libs implementation and $ reverse-depends src:slang2 -r xenial is quite a long list. OTOH this is somewhat ok as the change is in Debian and Ubuntu for more than three releases now and nothing around it seems to have totally broken. Never the less the biggest risk I see is something unexpected in one of the other libslang2 users. [Other Info] * n/a --- When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slang2/+bug/1537528/+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 1495688] Re: system-image-cli tool fails on dangling symlink
** No longer affects: livecd-rootfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1495688
Title:
system-image-cli tool fails on dangling symlink
Status in Snappy:
Fix Released
Status in Ubuntu system image:
Fix Released
Status in system-image package in Ubuntu:
Fix Released
Bug description:
(amd64)ubuntu@localhost:~$ system-image-cli -i
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 253, in
last_update_date
timestamp = datetime.fromtimestamp(os.stat(LAST_UPDATE_FILE).st_mtime)
FileNotFoundError: [Errno 2] No such file or directory:
'/userdata/.last_update'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/system-image-cli", line 9, in
load_entry_point('system-image==3.0.1', 'console_scripts',
'system-image-cli')()
File "/usr/lib/python3/dist-packages/systemimage/main.py", line 289, in main
last_update=last_update_date(),
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 258, in
last_update_date
for path in config.ini_files)
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 258, in
for path in config.ini_files)
File "/usr/lib/python3.4/pathlib.py", line 1048, in stat
return self._accessor.stat(self)
File "/usr/lib/python3.4/pathlib.py", line 326, in wrapped
return strfunc(str(pathobj), *args)
FileNotFoundError: [Errno 2] No such file or directory:
'/etc/system-image/config.d/00_default.ini'
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1495688/+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 1673817] Re: update-secure-boot-policy behaving badly with unattended-upgrades
** No longer affects: unattended-upgrades (Ubuntu) ** No longer affects: unattended-upgrades (Ubuntu Trusty) ** No longer affects: unattended-upgrades (Ubuntu Xenial) ** No longer affects: unattended-upgrades (Ubuntu Yakkety) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1673817 Title: update-secure-boot-policy behaving badly with unattended-upgrades Status in shim-signed package in Ubuntu: Fix Released Status in shim-signed source package in Trusty: Fix Released Status in shim-signed source package in Xenial: Fix Released Status in shim-signed source package in Yakkety: Fix Released Bug description: [Impact] Any user with unattended upgrades enabled and DKMS packages in a Secure Boot environment might be prompted to change Secure Boot policy, which will fail and crash in unattended-upgrades. [Test case] = unattended upgrade = 1) Create /var/lib/dkms/TEST-DKMS 2) Install new package 3) Trigger unattended-upgrades: unattended-upgrades -d Upgrade should run smoothly for all the processing but fail to complete; shim-signed should end the unattended upgrade with a error as unattended change of the Secure Boot policy can not be done. Upgrade should not hang in high CPU usage. = standard upgrade = 1) Create /var/lib/dkms/TEST-DKMS 2) install new package. 3) Verify that the upgrade completes normally. [Regression Potential] Any failure to prompt for or change Secure Boot policy in mokutil while in an *attended* upgrade scenario would constitute a regression of this SRU. Any other issues related to booting in Secure Boot mode should instead be directed to bug 1637290 (shim update). --- Currently, unattended-upgrades will automatically install all updates for those running development releases of Ubuntu (LP: #1649709) Today, my computer was acting very sluggish. Looking at my process list, I saw/ usr/sbin/update-secureboot-policy was using a log of CPU. I killed the process. I have a /var/crash/shim-signed.0.crash but since it's 750 MB, I didn't bother submitting it or looking at it more. Maybe it crashed because I killed the process. Also, I see that unattended-upgrades-dpkg.log is 722 MB. Today's update included both VirtualBox and the linux kernel. I am attaching an excerpt of /var/log/unattended-upgrades/unattended- upgrades-dpkg.log This message was repeated a very large number of times (but I only included it once in the attachment: "Invalid password The Secure Boot key you've entered is not valid. The password used must be between 8 and 16 characters." ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: shim-signed 1.23+0.9+1474479173.6c180c6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 17 11:15:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-23 (21 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219) SourcePackage: shim-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1673817/+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 1829588] [NEW] make it easy to add proposed; help text outdated
Public bug reported: I want to do some SRU testing but I have to look up how to add the -proposed lines to apt sources every time I want to do this task. The wiki page for it is pretty verbose and includes text like: "Replace "xenial" with "trusty", "vivid", "utopic", "precise", or "lucid" depending on which release you are on. " Adding -proposed should be as easy as running: sudo add-apt-repository proposed But this doesn't work: $ sudo add-apt-repository proposed Error: 'proposed' invalid The help text includes a bunch of examples of things that users almost never need to do any more: $ add-apt-repository -h [...] Examples: apt-add-repository 'deb http://myserver/path/to/repo stable myrepo' apt-add-repository 'http://myserver/path/to/repo myrepo' apt-add-repository 'https://packages.medibuntu.org free non-free' apt-add-repository http://extras.ubuntu.com/ubuntu apt-add-repository ppa:user/repository apt-add-repository ppa:user/distro/repository apt-add-repository multiverse https://packages.medibuntu.org is now owned by a commerce site, or squatter, or something similar. It also fails certificate validation. This should be removed. http://extras.ubuntu.com/ubuntu/dists/ has precise through utopic. Maybe we shouldn't remove this yet, but someday we may want to revisit this one. It'd be great to have examples of adding proposed, universe, security, updates, etc. Maybe it'd be nice to put a reference to whatever tool would also enable ESM. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-common 0.96.24.32.7 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Fri May 17 18:32:49 2019 InstallationDate: Installed on 2012-10-18 (2402 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-05-02 (381 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1829588 Title: make it easy to add proposed; help text outdated Status in software-properties package in Ubuntu: New Bug description: I want to do some SRU testing but I have to look up how to add the -proposed lines to apt sources every time I want to do this task. The wiki page for it is pretty verbose and includes text like: "Replace "xenial" with "trusty", "vivid", "utopic", "precise", or "lucid" depending on which release you are on. " Adding -proposed should be as easy as running: sudo add-apt-repository proposed But this doesn't work: $ sudo add-apt-repository proposed Error: 'proposed' invalid The help text includes a bunch of examples of things that users almost never need to do any more: $ add-apt-repository -h [...] Examples: apt-add-repository 'deb http://myserver/path/to/repo stable myrepo' apt-add-repository 'http://myserver/path/to/repo myrepo' apt-add-repository 'https://packages.medibuntu.org free non-free' apt-add-repository http://extras.ubuntu.com/ubuntu apt-add-repository ppa:user/repository apt-add-repository ppa:user/distro/repository apt-add-repository multiverse https://packages.medibuntu.org is now owned by a commerce site, or squatter, or something similar. It also fails certificate validation. This should be removed. http://extras.ubuntu.com/ubuntu/dists/ has precise through utopic. Maybe we shouldn't remove this yet, but someday we may want to revisit this one. It'd be great to have examples of adding proposed, universe, security, updates, etc. Maybe it'd be nice to put a reference to whatever tool would also enable ESM. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-common 0.96.24.32.7 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Fri May 17 18:32:49 2019 InstallationDate: Installed on 2012-10-18 (2402 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on
[Touch-packages] [Bug 1829580] [NEW] package libpython2.7-minimal:amd64 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
Public bug reported: N/A ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpython2.7-minimal:amd64 2.7.15~rc1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_36_39_generic_50 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri May 17 17:41:09 2019 DpkgHistoryLog: Start-Date: 2019-05-17 17:41:08 Commandline: apt-get install -f Requested-By: deandre (1000) DpkgTerminalLog: dpkg: error processing package libpython2.7-minimal:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-09-26 (233 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: python2.7 Title: package libpython2.7-minimal:amd64 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1829580 Title: package libpython2.7-minimal:amd64 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in python2.7 package in Ubuntu: New Bug description: N/A ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpython2.7-minimal:amd64 2.7.15~rc1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_36_39_generic_50 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri May 17 17:41:09 2019 DpkgHistoryLog: Start-Date: 2019-05-17 17:41:08 Commandline: apt-get install -f Requested-By: deandre (1000) DpkgTerminalLog: dpkg: error processing package libpython2.7-minimal:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-09-26 (233 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: python2.7 Title: package libpython2.7-minimal:amd64 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1829580/+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 645404] Re: Support Private PPAs
@carlfk, can you elaborate on: > deploy a private key (or similarly sensitive secret) file and a publicly > readable script (apt-add-repository...) and it just runs, no browser, > no user, no typing for a private ppa, the script will only generate 3 files (e.g. for ppa:ddstreet/private on disco): 1) /etc/apt/sources.list.d/ddstreet-ubuntu-private-disco.list 2) /etc/apt/auth.conf.d/ddstreet_ubuntu_private.conf 3) /etc/apt/trusted.gpg.d/ddstreet_ubuntu_private.gpg you could just copy those directly to whatever system you want, and not have to run anything at all on the system (besides 'sudo apt update' and then upgrade/install). Are you asking for something different? -- 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/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Cosmic: In Progress Status in software-properties source package in Disco: In Progress Status in software-properties source package in Eoan: In Progress Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 645404] Re: Support Private PPAs
** Changed in: software-properties (Ubuntu Eoan) Importance: Low => Medium -- 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/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Cosmic: In Progress Status in software-properties source package in Disco: In Progress Status in software-properties source package in Eoan: In Progress Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1829450] Re: test_systemd_fsck_with_plymouth_failure passes but marked expected failure
** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Cosmic) Status: New => In Progress ** Changed in: systemd (Ubuntu Disco) Status: New => In Progress ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Cosmic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Status: New => Invalid -- 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/1829450 Title: test_systemd_fsck_with_plymouth_failure passes but marked expected failure Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] this test case was marked as expected failure in the past to try to ignore failures, but it now passes and so causes autopkgtest failures. [test case] run autopkgtest and check for the 'test_systemd_fsck_with_plymouth_failure' test, e.g.: test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest) Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... bash: line 1: 786 Killed /tmp/autopkgtest.84SCbj/build.1op/src/debian/tests/systemd-fsckd 2> >(tee -a /tmp/autopkgtest.84SCbj/systemd-fsckd-stderr >&2) > >(tee -a /tmp/autopkgtest.84SCbj/systemd-fsckd-stdout) autopkgtest [16:47:57]: test process requested reboot with marker test_systemd_fsck_with_plymouth_failure:0 Connection to 10.44.40.6 closed by remote host. autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest) Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... unexpected success -- Ran 1 test in 17.952s FAILED (unexpected successes=1) [regression potential] low; test case expectation fix only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829450/+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 1828749] Re: ifconfig dummy0 : Device not found
Contrasting attachment, as discussed in previous comment. ** Attachment added: "bionic: insmod and modprobe behave differently" https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+attachment/5264585/+files/dummy-bionic.logg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found Status in ifupdown package in Ubuntu: New Status in net-tools package in Ubuntu: New Bug description: Desired behavior: The ifconfig command should be able to deal with the dummy device. This worked fine until recently. Observed behavior: :; ifconfig dummy0 dummy0: error fetching interface information: Device not found This problem appeared when I upgraded to bionic. Highly informative workaround: :; ip link add dummy0 type dummy That command works, and makes the problem go away permanently. The ifconfig command works fine after that. The ifup and ifdown commands also work fine after that. For convenient debugging, you can use the command: :; ip link del dummy0 type dummy which makes the problem come back. You can also experiment with dummy1 et cetera. Package ownership issues: Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204 That report was filed against ippusbxd, which is almost certainly not the relevant package. For that matter, I have no idea whether the root cause is in the net-tools package or the kernel networking stack. All I know is the ip command plays nicely with the kernel while the ifconfig command does not. Notes: The kernel module for the dummy interface is preloaded in all situations described here. That's not the issue. An apport file is attached, to describe the environment. Also, since you asked: :; apt-cache policy net-tools net-tools: Installed: 1.60-26ubuntu1 Candidate: 1.60-26ubuntu1 Version table: *** 1.60-26ubuntu1 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status :; lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1828749/+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 1828749] Re: ifconfig dummy0 : Device not found
I have conducted more investigation into the cause, resulting in a significant restatement of the issue. As far as this bug is concerned, it appears there has been no regression, indeed no change in behavior in ifconfig (net-tools package) or ifup (ifupdown package). However it could be argued that all along they have not handled dummy devices very well. The big change appears to be in modprobe (kmod package). As of xenial it behaved the same is insmode (also kmod package) but as of bionic it behaves differently. In particular, insmod tickles the device in such a way that dummy0 comes into existence (in a down state) whereas bionic modprobe leaves it nonexistent. (Higher-numbered devices such as dummy1 are nonexistent in all cases, when the module is newly installed.) The "ip link add" command is fully capable of bringing a dummy device into existence, but apparently neither ifconfig nor ifup has ever had this capability. This is a problem for dummy1 (always) and, what's worse, for dummy0 (as of bionic). You can see the gory details by comparing the typescripts attached to this comment (for xenial) and the next (for bionic). So ... even though the change in behavior occurred in modprobe, it could be argued that the new modprobe behavior is more logical, because it treats dummy0 and dummy1 the same now. By the same token, since dummy1 was never handled well by ifconfig or ifup, it could be argued that the best way to proceed would be to make those programs more robust. Crib the code from "ip link add" to bring the device into existence when appropriate. ** Attachment added: "xenial: insmod and modprobe behave the same" https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+attachment/5264584/+files/dummy-xenial.logg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found Status in ifupdown package in Ubuntu: New Status in net-tools package in Ubuntu: New Bug description: Desired behavior: The ifconfig command should be able to deal with the dummy device. This worked fine until recently. Observed behavior: :; ifconfig dummy0 dummy0: error fetching interface information: Device not found This problem appeared when I upgraded to bionic. Highly informative workaround: :; ip link add dummy0 type dummy That command works, and makes the problem go away permanently. The ifconfig command works fine after that. The ifup and ifdown commands also work fine after that. For convenient debugging, you can use the command: :; ip link del dummy0 type dummy which makes the problem come back. You can also experiment with dummy1 et cetera. Package ownership issues: Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204 That report was filed against ippusbxd, which is almost certainly not the relevant package. For that matter, I have no idea whether the root cause is in the net-tools package or the kernel networking stack. All I know is the ip command plays nicely with the kernel while the ifconfig command does not. Notes: The kernel module for the dummy interface is preloaded in all situations described here. That's not the issue. An apport file is attached, to describe the environment. Also, since you asked: :; apt-cache policy net-tools net-tools: Installed: 1.60-26ubuntu1 Candidate: 1.60-26ubuntu1 Version table: *** 1.60-26ubuntu1 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status :; lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1828749/+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 1829533] Re: Doubled desktop icons
** Package changed: xorg (Ubuntu) => gnome-shell-extension-desktop-icons (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829533 Title: Doubled desktop icons Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: I customized my icons by changing the folder image. That worked fine in Ubuntu 18.04. When I upgraded to 19.04 my customized icons no longer showed the new image, and to fix that I did... something. Install Nemo deskop, I think, but I can't find a configuration or uninstall option for it. Then the old icons with the customized images worked fine... but now the folders have a doubles that are "dummies" (not working -- not customized -- don't respond to being clicked). In the Gnome Tweak Took Desktop icons is "off" but the toggle for "Desktop Icons Switch" has an ! meaning can't be turned on or off. I'm moderately techy in Windows, but still pretty stupid about Linux, sorry. But I can probably run tests, find logs, paste commands into Terminal Window or whatever. THANKS!!! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 17 09:27:05 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T520 [17aa:21cf] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4243AV5 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=a8ac701e-a37a-41b7-aa12-0816bd937e33 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET49WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243AV5 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:bvr8AET49WW(1.29):bd07/11/2011:svnLENOVO:pn4243AV5:pvrThinkPadT520:rvnLENOVO:rn4243AV5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4243AV5 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1829533/+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 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint
** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Cosmic) Status: New => Invalid -- 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/1825378 Title: systemd-networkd doesn't set wireguard peer endpoint Status in systemd package in Ubuntu: In Progress Status in systemd source package in Cosmic: Invalid Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] systemd does not set endpoints for wireguard interfaces correctly. This makes wireguard unusable. [test case] install a disco or eoan system and set up a wireguard interface: $ sudo add-apt-repository ppa:wireguard/wireguard $ sudo apt install wireguard ...(this does a lot of stuff)... create a file as below; There is no need to setup remote server to reproduce this issue, but PublicKey/PrivateKey should be valid one (used instructions from https://www.linode.com/docs/networking/vpn /set-up-wireguard-vpn-on-ubuntu/#configure-wireguard-server): $ cat /etc/systemd/network/wg0.netdev [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=uMuCbguKYdKanRYMbDSriIdgxGxJR57Us1zEy8wRc1M= ListenPort=51820 [WireGuardPeer] PublicKey=ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 $ sudo systemctl restart systemd-networkd $ sudo wg show wg0 interface: wg0 public key: BnvFgvPiVb5xURfzZ5liV1P77qeGeJDIX3C1iNquA2k= private key: (hidden) listening port: 51820 peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= allowed ips: 10.0.0.0/8 the last command should print remote endpoint address, e.g.: peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 [regression potential] any changes to systemd contain the potential for serious regressions. However, this is cherry picked directly from upstream, with the releases requiring patching (disco and eoan) being at exactly the same version and very close to upstream already. Additionally, while this does add 2 new functions (from upstream commit https://github.com/systemd/systemd/pull/11580/commits/abd48ec87f2ac5dd571a99dcb4db88c4affdffc8), they are only used - and code is only changed in - wireguard.c, so any regressions should be limited to wireguard interfaces (unless systemd crashes completely). [other info] this bug is not present in cosmic and earlier, and is already fixed in upstream systemd, so this is needed only for disco and eoan. original description: --- systemd/disco 240 shipped with Ubuntu 19.04 beta does not set endpoints for [WireguradPeer] properly. This regression was introduced in v241 and merged into v240. systemd 241 doesn't set wireguard peer endpoint https://github.com/systemd/systemd/issues/11579 Revert of the regression was landed on v240 stable branch https://github.com/systemd/systemd-stable/pull/39 1)2) confirmed with, systemd/disco 240-6ubuntu5 amd64 3) put a netdev file /etc/systemd/network/wg0.netdev --- [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=** ListenPort=51820 [WireGuardPeer] PublicKey=* AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 and run --- # systemctl restart systemd-networkd # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * allowed ips: 10.0.0.0/8 4) the last command should print remote endpoint address. --- # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825378/+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 1825997] Re: boot-smoke fails due to running jobs
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Status: New => Invalid -- 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/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services are started. This confuses the boot-smoke test, because it sees that 'is-system-running' is done, but then it sees running jobs, which fails the test. What is starting jobs after systemd reaches running state appears to be X inside the test system. There are various services started by gnome-session and dbus-daemon. Additionally, from the artifacts of one example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz the artifacts/journal.txt shows that after the boot-smoke test causes the reboot and then re-ssh into the system after the reboot, it only gives the test system 9 seconds before deciding it has failed, and only 4 seconds after ssh'ing into the rebooted test system. Another wait is needed when checking for remaining running jobs. Or, the running jobs check could be removed entirely, and we can just trust that systemd correctly knows when it has reached running|degraded state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+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 1767172] Re: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one
Kees,
I the fix in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766052 sufficient
to address the situation? Do we still need to do more to systemd (note,
the GH issue was closed upstream following Dimitri's input)?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1767172
Title:
Regression: /etc/modules checked against blacklist or it's really hard
to load blacklisted watchdog modules when one really wants one
Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Impossible / hard to force the system to load a watchdog module
because it is blacklisted by the kernel auto-generated list of
"watchdog" modules.
/etc/modules used to "just work" before.
e.g. bcm2835_wdt module on arm64
===
Before systemd-modules-load, /etc/init.d/kmod would load modules
directly with "modprobe" (and _not_ "modprobe -b"):
load_module() {
local module args
module="$1"
args="$2"
if [ "$VERBOSE" != no ]; then
log_action_msg "Loading kernel module $module"
modprobe $module $args || true
else
modprobe $module $args > /dev/null 2>&1 || true
fi
}
However, under 18.04, systemd-modules-load will _ignore_ modules that
are manually listed in /etc/modules and process them with the
blacklist (the same as "modprobe -b" would). This means that it is not
possible to manually load modules that are blacklisted (like watchdog
modules):
systemd-238/src/modules-load/modules-load.c:
static int load_module(struct kmod_ctx *ctx, const char *m) {
const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
...
default:
err = kmod_module_probe_insert_module(mod,
probe_flags,
NULL, NULL,
NULL, NULL);
if (err == 0)
log_info("Inserted module '%s'",
kmod_module_get_name(mod));
else if (err == KMOD_PROBE_APPLY_BLACKLIST)
log_info("Module '%s' is blacklisted",
kmod_module_get_name(mod));
Blacklists should _not_ be applied by systemd-modules-load.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1823761] Re: [SRU] Move Livepatch in a different tab as in Disco
** Tags removed: rls-bb-incoming -- 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/1823761 Title: [SRU] Move Livepatch in a different tab as in Disco Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: * Impact The livepatch graphical interfaces are currently limited in bionic, there is no easy way to know the current status and the details of the changes applied. The new design improves the user experience and we want that to benefit the LTS users * Test case Open software-properties-gtk, you should see a livepatch new tab which has the detail of the status (including the CVEs fixes with the applied livepatch where there is one) * Regression potential The changes are mostly new code so check that the livepatch tab works correctly. There is some UI refactoring so it's best to check that the other tabs still look the same. Note that the changes include some new strings. Those are translated in disco and have been announced to the translators in march as coming to bionic for a SRU (https://lists.ubuntu.com/archives/ubuntu-translators/2019-March/007530.html). Launchpad shares translations between series so we should get those translations included in the next bionic langpacks export. --- Backport the new Livepatch tab from Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823761/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
hah, ok that makes more sense then. Looks like this works, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1537635] Re: Reduce zlib compression level for massive performance increase
https://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/3240 ** Changed in: apport Status: In Progress => Fix Released -- 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/1537635 Title: Reduce zlib compression level for massive performance increase Status in Apport: Fix Released Status in apport package in Ubuntu: In Progress Status in apport source package in Eoan: In Progress Bug description: When apport takes a core dump of a large application, it uses 100% CPU for a _long_ time (often 30 seconds or more) to compress the core dump. The system is virtually unusable during this time, especially if the application was the window manager and won’t be restarted until the core dump is complete. This is a longstanding known problem; it motivated the switch from bzip2 to zlib level 9 back in apport 0.24. That made it much better, but it’s still quite bad. So why not switch from zlib level 9 to zlib level 1? I tested this on a core dump of gnome-shell, and while it increased the size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased the needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3 seconds). This tradeoff seems more than worthwhile for this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1537635/+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
Re: [Touch-packages] [Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
On Fri, May 17, 2019 at 07:44:50PM -, Paul Larson wrote: > Ok, yeah I see it running: > /usr/bin/python3 /tmp/ubuntu-release-upgrader-n98wh3a9/bionic --mode=server > --frontend=DistUpgradeViewNonInteractive > and > $ sudo cat /tmp/ubuntu-release-upgrader-n98wh3a9/DistUpgradeVersion.py > VERSION = '18.04.33' > > after letting it run a while, I did see it seemed to be stuck on ntp and > asking me what I wanted to do. I Switched windows but I was pretty sure > I didn't press anything else. It had progressed when I went back, but I > wouldn't have expected it to be asking at all. I'll try to reproduce > again, but it takes a while to get there. There's a 5 second sleep or so after the dialog appears before a response is given and the comment indicates that is due to a race condition. I wasn't brave enough to mess with that. ;-) -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to:
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
from the mailing list discussion (linked above by @racb), this response from an upstream sudo developer Todd C. Miller: On Thu, 16 May 2019 07:48:40 -0400, Dan Streetman wrote: > I've cc'ed sudo-users, so the question to the upstream sudo list can > be summarized as: > How likely would it be for upstream sudo to add HOME to env_keep by default? Extremely unlikely. Prior to sudo 1.7.4 the HOME and MAIL environment variables were preserved in the environment by default. This can lead to programs using config files the original user's home directory, which has security implications, so the default was changed in 1.7.4. In the old days, sudo did little more than change the uid. These days sudo tries to run the command in an environment that closely matches what you would get by logging in as that user. This has proven to be safer as it more closely matches the assumptions other programs make. > We ask because Ubuntu carries a patch that adds HOME to env_keep, > unlike the default upstream, or any other Linux/Unix. We are > considering removing that patch, to match upstream defaults, of *not* > including HOME in env_keep. I would be supportive of that. I believe that resetting HOME is the safer default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Ok, yeah I see it running: /usr/bin/python3 /tmp/ubuntu-release-upgrader-n98wh3a9/bionic --mode=server --frontend=DistUpgradeViewNonInteractive and $ sudo cat /tmp/ubuntu-release-upgrader-n98wh3a9/DistUpgradeVersion.py VERSION = '18.04.33' after letting it run a while, I did see it seemed to be stuck on ntp and asking me what I wanted to do. I Switched windows but I was pretty sure I didn't press anything else. It had progressed when I went back, but I wouldn't have expected it to be asking at all. I'll try to reproduce again, but it takes a while to get there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1537635] Re: Reduce zlib compression level for massive performance increase
** Branch linked: lp:~ubuntu-core-dev/ubuntu/eoan/apport/ubuntu -- 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/1537635 Title: Reduce zlib compression level for massive performance increase Status in Apport: In Progress Status in apport package in Ubuntu: In Progress Status in apport source package in Eoan: In Progress Bug description: When apport takes a core dump of a large application, it uses 100% CPU for a _long_ time (often 30 seconds or more) to compress the core dump. The system is virtually unusable during this time, especially if the application was the window manager and won’t be restarted until the core dump is complete. This is a longstanding known problem; it motivated the switch from bzip2 to zlib level 9 back in apport 0.24. That made it much better, but it’s still quite bad. So why not switch from zlib level 9 to zlib level 1? I tested this on a core dump of gnome-shell, and while it increased the size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased the needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3 seconds). This tradeoff seems more than worthwhile for this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1537635/+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 1803993] Re: Password appears on the VT1 screen
Use CVE-2018-20839. Thanks ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-20839 -- 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/1803993 Title: Password appears on the VT1 screen Status in gdm3 package in Ubuntu: Invalid Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [Impact] * The keyboard on the graphical login screen started on VT1 may stop working and or keypresses including passwords are leaked to the terminal console running 'behind' the graphical login screen or environment. [Test Case] * Reboot after installing the fixed systemd package. * Install sysdig * Start sysdig on a remote connection or on a terminal console: $ sudo sysdig evt.type=ioctl | grep request=4B4 * While sysdig is running log in and out 3 times in GDM and press a few keys in the graphical session to see if keyboard still works * Log in and out on an other terminal console, too, running a few commands while being logged in to ensure that keyboard is working. * Observe that on terminal consoles the monitored keyboard setter ioctl is called with argument=3, but where the graphical screen is active only argument=4 is used, unlike with the buggy version observed in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14 [Regression Potential] * The fix checks the current keyboard mode of the VT and allows only safe mode switches. The potential regression could be not allowing a valid mode switch keeping a keyboard in a non-operational mode. Testing covers that by typing the keyboard. (continued from bug 1767918) This was found when an administrative error made /home directory inaccessible. Any users that tried to login after that, were not able to (which is expected) but their password appears on the VT1 screen. Under normal circumstances, VT1 is not visible. But once the system was sent into this compromised mode, one can press ctrl+alt+F1 and then ctrl+alt+F2 and get a momentary glance at VT1. One can keep toggling between these key combinations in order to make out the password(s) on VT1. As a further test, I wanted to see if a non-super user could cause this condition, and it is in fact possible. As a regular user, I made their own home directory not writable and then removed ~/.config and logged out. Then logged in as that user again, and although that user can't login the system does go into that mode where passwords appear on VT1 and are viewable with the key combinations mentioned herein. Further, any other users that login will see no problem, but when they logon their passwords also appear on VT1 and are viewable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.3 Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 08:32:59 2018 InstallationDate: Installed on 2018-08-25 (85 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+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 1824002] Re: python3-launchpadlib needs promotion from suggests
** Branch linked: lp:~ubuntu-core-dev/ubuntu/eoan/apport/ubuntu -- 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/1824002 Title: python3-launchpadlib needs promotion from suggests Status in apport package in Ubuntu: In Progress Status in apport source package in Eoan: In Progress Bug description: If one wants to apport-collect, one gets an error about python3-launchpadlib needing to be installed. One can easily install it, but it really should be a Recommend, if not a Depend so one doesn't have to go through this trouble. Right now, it's a Suggest. It seems that during the whole Python2/3 transition some things got switched around, but it had been a Depend for a long time before that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824002/+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 1829568] [NEW] [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
Public bug reported: Built-in speakers work fine. When testing headphones in sound settings, The sound indicator bar in Pulse-Audio moves. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 17 12:05:57 2019 InstallationDate: Installed on 2019-05-16 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 8064 F pulseaudio galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Built-in speakers work fine. When testing headphones in sound settings, The sound indicator bar in Pulse-Audio moves. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 17 12:05:57 2019 InstallationDate: Installed on 2019-05-16 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 8064 F pulseaudio galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
The command do-release-upgrade downloads a tarball of ubuntu-release- upgrader from the release to which you are upgrading e.g. http://archive.ubuntu.com/ubuntu/dists/bionic-proposed/main/dist- upgrader-all/current/bionic.tar.gz. That tarball is then extracted into /tmp/ubuntu-release-upgrader-$TEMP/. To confirm you are getting the right version of the tarball you can check DistUpgradeVersion.py in that folder. It should contain 18.04.33. It looks right to me: bdmurray@clean-xenial-amd64:~$ cd /tmp/ubuntu-release-upgrader-pn4lfyfj/ bdmurray@clean-xenial-amd64:/tmp/ubuntu-release-upgrader-pn4lfyfj$ cat DistUpgradeVersion.py VERSION = '18.04.33' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1729491] Re: [UIFe] ubuntu-bug says that snap packages are not installed
** Branch linked: lp:apport -- 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/1729491 Title: [UIFe] ubuntu-bug says that snap packages are not installed Status in apport package in Ubuntu: Fix Released Status in ubuntu-docs package in Ubuntu: New Status in apport source package in Bionic: Fix Released Bug description: User Interface Freeze Exception Justification = The interface for ubuntu-bug/apport-bug is super confusing if was installed as a snap. List Notifications == https://lists.ubuntu.com/archives/ubuntu-translators/2018-April/007471.html Original Bug Description 1. I installed the package gnome-recipes, tried to send an error report program in response to the received message:you cannot report a problem: The report belongs to a package that was not installed. 2. Expected that the program will be identified as installed. 3. sudo apt -f install [sudo] password for Alexander: Reading package lists... Done Building dependency tree Reading state information... Ready 0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 packages are not updated. sudo gnome-sudo recipes: gnome-recipes: command not found sudo apt install gnome-recipes Reading package lists... Done Building dependency tree Reading state information... Ready E: unable to locate package gnome-recipes I installed via software-center gnome-recipes snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks ubuntu-bug gnome-recipes dpkg-query: template gnome-recipes no corresponding package Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ^C^Z [1]+ Stopped ubuntu-bug gnome-recipes https://youtu.be/AXtR5m2uqUg --- 1. произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке программы, в ответ получил сообщение:Не удаётся сообщить о неполадке: Отчёт относится к пакету , который не был установлен. 2. Ожидал что программа будет идентифицироваться как установленная. 3. sudo apt -f install [sudo] пароль для alexandr: Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено. sudo gnome-recipes sudo: gnome-recipes: команда не найдена sudo apt install gnome-recipes Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово E: Не удалось найти пакет gnome-recipes произвёл установку через software-center gnome-recipes snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks ubuntu-bug gnome-recipes dpkg-query: шаблону gnome-recipes не соответствует ни один пакет Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ^C^Z [1]+ Остановлено ubuntu-bug gnome-recipes https://youtu.be/AXtR5m2uqUg ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-center (not installed) Uname: Linux 4.14.0-041400rc7-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 2 08:06:48 2017 InstallationDate: Installed on 2017-10-29 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1729491/+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 1829566] [NEW] network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Public bug reported: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: network-manager systemd-resolved -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: New Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+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 1829561] [NEW] lenovo ideapad 330 15ich ubuntu problem
Public bug reported: i have a problem laptop freeze every time i click on shutdown or reboot and the only way to close system is to hold power bitten fir 5ec and the second problem is the touch pad not working please help me ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 17 18:20:12 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:38ec] Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:38ec] InstallationDate: Installed on 2019-05-17 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b629 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=177ac39c-c469-4e07-bf5c-a430cfad796b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN30WW:bd01/24/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829561 Title: lenovo ideapad 330 15ich ubuntu problem Status in xorg package in Ubuntu: New Bug description: i have a problem laptop freeze every time i click on shutdown or reboot and the only way to close system is to hold power bitten fir 5ec and the second problem is the touch pad not working please help me ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 17 18:20:12 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:38ec] Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:38ec] InstallationDate: Installed on 2019-05-17 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b629 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=177ac39c-c469-4e07-bf5c-a430cfad796b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor:
[Touch-packages] [Bug 1829077] Re: disco 19.04 doesn't shutdown
Hello, One more information : I looked on the motherboard which has a "debug" display. When I shutdown the system and the screen stay with the red dot, the motherboard display an error code : 05 = "OEM initialization before microcode loading"... (the computer is from 2011 and the Bios updated) -- 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/1829077 Title: disco 19.04 doesn't shutdown Status in systemd package in Ubuntu: New Bug description: I have a fresh install of Ubuntu 19.04 GNOME 64 bits. When I choose "Power Off", it closes the session screen but then the it displays the red dots who scroll under Ubuntu logo and it never stop completely. I can listen the hard disk containing my home directory which stops (the system is on a SSD). Each time, I have to switch off the computer. I can start it again without any problem. The command "sudo shutdown now" give the same result. This computer had not this problem with the previous version of Ubuntu. Proc : AMD Fx 8320 Motherboard : Asrock 970 Extreme 4 graphic card : Radeon 6850 Ram : 8Go Ubuntu 19.04 is the only OS on the SSD system drive /home is on a second hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829077/+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 1803993] Re: Password appears on the VT1 screen
** Description changed: + [Impact] + + * The keyboard on the graphical login screen started on VT1 may stop + working and or keypresses including passwords are leaked to the terminal + console running 'behind' the graphical login screen or environment. + + [Test Case] + + * Reboot after installing the fixed systemd package. + * Install sysdig + * Start sysdig on a remote connection or on a terminal console: + $ sudo sysdig evt.type=ioctl | grep request=4B4 + * While sysdig is running log in and out 3 times in GDM and press a few keys in the graphical session to see if keyboard still works + * Log in and out on an other terminal console, too, running a few commands while being logged in to ensure that keyboard is working. + * Observe that on terminal consoles the monitored keyboard setter ioctl is called with argument=3, but where the graphical screen is active only argument=4 is used, unlike with the buggy version observed in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14 + + [Regression Potential] + + * The fix checks the current keyboard mode of the VT and allows only + safe mode switches. The potential regression could be not allowing a + valid mode switch keeping a keyboard in a non-operational mode. Testing + covers that by typing the keyboard. + + (continued from bug 1767918) This was found when an administrative error made /home directory inaccessible. Any users that tried to login after that, were not able to (which is expected) but their password appears on the VT1 screen. Under normal circumstances, VT1 is not visible. But once the system was sent into this compromised mode, one can press ctrl+alt+F1 and then ctrl+alt+F2 and get a momentary glance at VT1. One can keep toggling between these key combinations in order to make out the password(s) on VT1. As a further test, I wanted to see if a non-super user could cause this condition, and it is in fact possible. As a regular user, I made their own home directory not writable and then removed ~/.config and logged out. Then logged in as that user again, and although that user can't login the system does go into that mode where passwords appear on VT1 and are viewable with the key combinations mentioned herein. Further, any other users that login will see no problem, but when they logon their passwords also appear on VT1 and are viewable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.3 Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 08:32:59 2018 InstallationDate: Installed on 2018-08-25 (85 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803993 Title: Password appears on the VT1 screen Status in gdm3 package in Ubuntu: Invalid Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [Impact] * The keyboard on the graphical login screen started on VT1 may stop working and or keypresses including passwords are leaked to the terminal console running 'behind' the graphical login screen or environment. [Test Case] * Reboot after installing the fixed systemd package. * Install sysdig * Start sysdig on a remote connection or on a terminal console: $ sudo sysdig evt.type=ioctl | grep request=4B4 * While sysdig is running log in and out 3 times in GDM and press a few keys in the graphical session to see if keyboard still works * Log in and out on an other terminal console, too, running a few commands while being logged in to ensure that keyboard is working. * Observe that on terminal consoles the monitored keyboard setter ioctl is called with argument=3, but where the graphical screen is active only argument=4 is used, unlike with the buggy version observed in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14 [Regression Potential] * The fix checks the current keyboard mode of the VT and allows only safe mode switches. The potential regression could be not allowing a valid mode switch keeping a keyboard in a non-operational mode. Testing covers that by typing the keyboard. (continued from bug 1767918) This was found when an administrative error made /home directory inaccessible. Any users that tried to login after that, were not able to (which is expected) but their password appears on the VT1 screen. Under normal circumstances, VT1 is not visible.
[Touch-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
Michael Neuffer, this report has been missing key information since 2014 -> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/comments/33 . Hence, could you please test http://cdimage.ubuntu.com/daily-live/current/ and if reproducible please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information: apport-collect 1268151 -- 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/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: xset dpms force off; sleep 30; xset dpms force on WORKAROUND: A restart of the Xserver will bring back the display. WORKAROUND: Don't allow DPMS to switch off the display: xset dpms 0 0 0 xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+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 1829540] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
Public bug reported: After computer returns from being locked, after I type my password, the option of where to hear the sounds from the computer appears, selecting speaker, still I can not hear any sound from the computer!! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luciana2245 F...m pulseaudio /dev/snd/controlC0: luciana2245 F pulseaudio CurrentDesktop: Unity Date: Fri May 17 17:07:11 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2019-02-15 (91 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luciana2245 F...m pulseaudio /dev/snd/controlC0: luciana2245 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0C77WG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0C77WG:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3573 dmi.product.version: 1.4.0 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1829540 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: After computer returns from being locked, after I type my password, the option of where to hear the sounds from the computer appears, selecting speaker, still I can not hear any sound from the computer!! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luciana2245 F...m pulseaudio /dev/snd/controlC0: luciana2245 F pulseaudio CurrentDesktop: Unity Date: Fri May 17 17:07:11 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2019-02-15 (91 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luciana2245 F...m pulseaudio /dev/snd/controlC0: luciana2245 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0C77WG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0C77WG:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3573 dmi.product.version: 1.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829540/+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 1829533] [NEW] Doubled desktop icons
Public bug reported: I customized my icons by changing the folder image. That worked fine in Ubuntu 18.04. When I upgraded to 19.04 my customized icons no longer showed the new image, and to fix that I did... something. Install Nemo deskop, I think, but I can't find a configuration or uninstall option for it. Then the old icons with the customized images worked fine... but now the folders have a doubles that are "dummies" (not working -- not customized -- don't respond to being clicked). In the Gnome Tweak Took Desktop icons is "off" but the toggle for "Desktop Icons Switch" has an ! meaning can't be turned on or off. I'm moderately techy in Windows, but still pretty stupid about Linux, sorry. But I can probably run tests, find logs, paste commands into Terminal Window or whatever. THANKS!!! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 17 09:27:05 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T520 [17aa:21cf] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4243AV5 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=a8ac701e-a37a-41b7-aa12-0816bd937e33 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET49WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243AV5 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:bvr8AET49WW(1.29):bd07/11/2011:svnLENOVO:pn4243AV5:pvrThinkPadT520:rvnLENOVO:rn4243AV5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4243AV5 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829533 Title: Doubled desktop icons Status in xorg package in Ubuntu: New Bug description: I customized my icons by changing the folder image. That worked fine in Ubuntu 18.04. When I upgraded to 19.04 my customized icons no longer showed the new image, and to fix that I did... something. Install Nemo deskop, I think, but I can't find a configuration or uninstall option for it. Then the old icons with the customized images worked fine... but now the folders have a doubles that are "dummies" (not working -- not customized -- don't respond to being clicked). In the Gnome Tweak Took Desktop icons is "off" but the toggle for "Desktop Icons Switch" has an ! meaning can't be turned on or off. I'm moderately techy in Windows, but still pretty stupid about Linux, sorry. But I can probably run tests, find logs, paste commands into Terminal Window or whatever. THANKS!!! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27
[Touch-packages] [Bug 1829364] Re: Will not play sound via HDMI unless you run pavucontrol first
** Description changed: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. + + Workaround: + Set + alternate-sample-rate = 44100 + in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jarnos 1283 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard -- 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/1829364 Title: Will not play sound via HDMI unless you run pavucontrol first Status in pulseaudio package in Ubuntu: New Bug description: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+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 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
I'm not sure if this is actually the same bug, but I fixed an issue with the same symptoms, documenting here for the sake of those who come after me: The NetworkManager tool asks you to input a subnet mask in "dotted-quad" format, however, if you look at the config file created for the connection in /etc/NetworkManager/system-connections, you see that it converts it to /CIDR notation. However, I had input some routes which didn't actually properly map to a CIDR network specification, which was causing the ip-route add command to fail with an "RTNETLINK answers: Invalid argument" error message. Correcting or removing these routes fixed my issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection Status in network-manager package in Ubuntu: Confirmed Bug description: lsb_release -rd: Description: Ubuntu 16.04.1 LTS Release: 16.04 Network Settings package version in Software Center: 15.04.0+16.04.20160705-0ubuntu1 Prior to upgrading to 16.04 LTS I was running 14.04 LTS. Using the "Edit Connections..." menu option I had created a custom Ethernet connection that had some custom routes added. These routes are required for me to connect to certain resources on a local network while using Wifi for basic internet. (Physical network locked down, no Internet access available) I've attached a screenshot showing the routes. These routes were working great in 14.04 (And prior releases of Ubuntu). However, upon upgrading to 16.04, I noticed this connection would no longer "connect". It would just silently fail. I noticed that if I deleted my custom routes, it would work, but I need those in order to connect to my required network services. When I try to connect with the routes in place, the connection silently fails in the NetworkManager UI (I get no error message in the UI) but I took a look at syslog and found these: Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7271] platform-linux: do-add-ip4-route[2: 10.105.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7272] platform-linux: do-add-ip4-route[2: 10.51.35.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7273] platform-linux: do-add-ip4-route[2: 10.140.76.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7281] device (enp0s31f6): state change: ip-config -> failed (reason 'config-failed') [70 120 4] Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7289] device (enp0s31f6): Activation: failed for connection 'Windstream' Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7309] device (enp0s31f6): state change: failed -> disconnected (reason 'none') [120 30 0] Now, if I remove the custom routes from the UI, then I can connect. I them manually add the routes using the "ip" command: sudo /sbin/ip route add 10.104.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.105.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.51.35.0/24 dev enp0s31f6 sudo /sbin/ip route add 10.140.76.0/24 dev enp0s31f6 This is able to add the routes successfully. So there has to be some problem in the new implementation of NetworkManager in 16.04, because these routes worked in 14.04 and they still work in 16.04 if I just manually add them from the command line. For now I can work around this issue by manually adding these routes from the command line every time I connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
** Tags added: id-5cde5f8331588344774efccb -- 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/1811471 Title: local resolver stub fails to handle multiple TCP dns queries Status in systemd: Fix Released Status in resolvconf package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in resolvconf source package in Bionic: Triaged Status in systemd source package in Bionic: Fix Released Status in resolvconf source package in Cosmic: Triaged Status in systemd source package in Cosmic: Fix Released Status in resolvconf source package in Disco: Triaged Status in systemd source package in Disco: Fix Released Bug description: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection, and so a simple change to systemd to flush the input buffer is not enough to fix the bug (and would also not actually fix the bug since glibc would never get the response). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo() - such as ssh, telnet, ping, etc - or with a simple C program that uses getaddrinfo(). The dns name looked up must have enough A records to overflow
[Touch-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
With BIOS A25 and eoan it is still not fixed. -- 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/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: xset dpms force off; sleep 30; xset dpms force on WORKAROUND: A restart of the Xserver will bring back the display. WORKAROUND: Don't allow DPMS to switch off the display: xset dpms 0 0 0 xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+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 1829484] Re: krb5-multidev dependency broken with ESM Trusty Repo
Thanks for the fast reply. According to my knowledge I did not disable the repo but it seems that it has actually vanished from /etc/apt/sources.list.d I will investigate further to find out why its gone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1829484 Title: krb5-multidev dependency broken with ESM Trusty Repo Status in krb5 package in Ubuntu: Incomplete Bug description: When trying to install 'krb5-multidev' on Ubuntu 14.04 (Trusty) with the ESM Repository enabled apt responds with this: ``` /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install krb5-multidev ... The following packages have unmet dependencies: krb5-multidev : Depends: libkrb5-3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libk5crypto3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libgssapi-krb5-2 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed ``` I assume, due to the equality matches here this means the appropriate dependencies cannot be installed because ESM already delivers newer ones. System Information: $lsb_release -rd Description:Ubuntu 14.04.6 LTS Release:14.04 $ apt-cache policy krb5-multidev krb5-multidev: Installed: (none) Candidate: 1.12+dfsg-2ubuntu5.4 $ apt-cache policy libk5crypto3 libk5crypto3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libgssapi-krb5-2 libgssapi-krb5-2: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libkrb5-3 libkrb5-3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1829484/+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 1828892] Re: systemctl - alias service reports inactive while aliased is active
@ddstreet There is no need to include the manpage correction (commit 71c9f49d730c8e) since it reverts commit c7612b2 which does not exist in xenial systemd. Initially issue #7875 was classified as feature request and not as a bug. Upstream added modified the manpage (https://github.com/systemd/systemd/commit/c7612b20052d9151f60a96623b8743cbac88390d) to clarify that 'is-active' command does not load units and therefore explain why an alias unit is reported inactive while the aliased is reported active. Later, when they realised it is a bug and fixed it they reverted c7612b2 with 71c9f49d730c8e. -- 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/1828892 Title: systemctl - alias service reports inactive while aliased is active Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Bug description: [Impact] 'systemctl is-active' command reports an alias service as inactive even though the aliased service is active. Currently the 'systemctl is-active' command does not load units to minimise its effect on the system (i.e. that a monitoring command does not itself alter the state of the system). However, this behaviour leads to inconsistencies when services are aliased. [Test case] - Test case 1 - libvirtd alias service : libvirtd aliased service : libvirt-bin /etc/systemd/system$ ls -la libvirtd.service lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> /lib/systemd/system/libvirt-bin.service $ systemctl is-active libvirtd inactive $ systemctl is-active libvirt-bin active - Test case 2 - sshd alias service : sshd aliased service : ssh /ect/systemd/system$ ls -la sshd.service lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> /lib/systemd/system/ssh.service $ systemctl is-active sshd inactive $ systemctl is-active ssh active [Regression Potential] This fix may result into systemctl reporting inconsistent information concerning the status of a service. [Other] Upstream issue : https://github.com/systemd/systemd/issues/7875 Upstream fix : https://github.com/systemd/systemd/pull/7997 Xenial is affected, fix exists on Bionic onward. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.21 Candidate: 229-4ubuntu21.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+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 1742063] Re: Systemd taking long time to boot into desktop 18.04
I fresh installed 18.04.2 with kernel 4.18 and now its finally fixed lotuspsychje@RootBoX:~$ systemd-analyze Startup finished in 2.948s (kernel) + 22.106s (userspace) = 25.055s graphical.target reached after 22.098s in userspace -- 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/1742063 Title: Systemd taking long time to boot into desktop 18.04 Status in systemd package in Ubuntu: Confirmed Bug description: ubuntu desktop 18.04 development branch with gnome/xorg @ 9/1/2018 Systemd takes a long time to boot both from start to login and from login to desktop systemd-analyze blame showed apt daily services taking up to 1min and i disabled auto updates but it still takes a long time to boot to desktop, on a fast ssd here's the analyze log after apt.daily disabled: 18.598s plymouth-quit-wait.service 6.544s NetworkManager-wait-online.service 6.302s dev-sda1.device 1.126s udisks2.service 1.097s fwupd.service 1.092s systemd-udev-trigger.service 1.028s apparmor.service 786ms keyboard-setup.service 770ms systemd-journald.service 752ms swapfile.swap 750ms upower.service 743ms systemd-rfkill.service 731ms accounts-daemon.service 697ms ModemManager.service 679ms systemd-journal-flush.service 635ms grub-common.service 580ms apport.service 568ms preload.service 566ms networking.service 555ms NetworkManager.service 554ms systemd-resolved.service 503ms systemd-logind.service 412ms snapd.service ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 07:57:20 2018 InstallationDate: Installed on 2017-12-18 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215) Lsusb: Bus 002 Device 002: ID 0402:7675 ALi Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AO722 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=b20f465f-45a3-49da-b5ea-8351b8e94c03 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08: dmi.product.family: Type1Family dmi.product.name: AO722 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742063/+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 1829484] Re: krb5-multidev dependency broken with ESM Trusty Repo
krb5-multidev is built from the krb5 source package, and https://esm.ubuntu.com/ubuntu/dists/trusty-security/main/binary- amd64/Packages.gz shows the 1.12+dfsg-2ubuntu5.4+esm1 version of this package available in the esm trusty-security pocket. But this does not show up in your apt-cache policy for this package. Did you *disable* the esm repository on this system, after installing the libraries from there? That would certainly be unsupported; you either need to keep the esm repository enabled and install the other packages from there, or if you are (for some reason) disabling esm you will need to manually downgrade the library packages. ** Changed in: krb5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1829484 Title: krb5-multidev dependency broken with ESM Trusty Repo Status in krb5 package in Ubuntu: Incomplete Bug description: When trying to install 'krb5-multidev' on Ubuntu 14.04 (Trusty) with the ESM Repository enabled apt responds with this: ``` /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install krb5-multidev ... The following packages have unmet dependencies: krb5-multidev : Depends: libkrb5-3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libk5crypto3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libgssapi-krb5-2 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed ``` I assume, due to the equality matches here this means the appropriate dependencies cannot be installed because ESM already delivers newer ones. System Information: $lsb_release -rd Description:Ubuntu 14.04.6 LTS Release:14.04 $ apt-cache policy krb5-multidev krb5-multidev: Installed: (none) Candidate: 1.12+dfsg-2ubuntu5.4 $ apt-cache policy libk5crypto3 libk5crypto3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libgssapi-krb5-2 libgssapi-krb5-2: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libkrb5-3 libkrb5-3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1829484/+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 1376017] Re: Dell 1908fpt VGA monitor has max resolution of 1280 x 768
** Tags removed: vivid -- 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/1376017 Title: Dell 1908fpt VGA monitor has max resolution of 1280 x 768 Status in xorg package in Ubuntu: Triaged Bug description: My Dell 1908fpt monitor connected via VGA has a max resolution of 1280 x 768. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None CurrentDesktop: GNOME Date: Tue Sep 30 23:27:42 2014 DistUpgraded: 2014-09-28 23:56:30,883 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-36-generic, i686: installed GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3039] InstallationDate: Installed on 2014-09-25 (5 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=cabc1f0e-dcf0-472a-aa34-db7305dbf8a5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-09-28 (1 days ago) dmi.bios.date: 08/20/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 2RKT54AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr2RKT54AUS:bd08/20/2008:svnLENOVO:pn6071BFG:pvrThinkCentreM57:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6071BFG dmi.product.version: ThinkCentre M57 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Sep 30 23:11:48 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1376017/+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 1352374] Re: changing backlight color on saitek eclipse 2 keyboard causes mouse failure
** Tags removed: vivid -- 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/1352374 Title: changing backlight color on saitek eclipse 2 keyboard causes mouse failure Status in xorg package in Ubuntu: Confirmed Bug description: This has apparently been ongoing for a long time. I have a Saitek Eclipse ii keyboard and I and others report that when you click the keyboard button to change the back light color, it triggers mouse events. These end up disabling the mouse, in my case Microsoft Intellimouse. Unplugging and replugging the USB cable for the keyboard resets function to normal with the default blue back light color. If you try to change the color, the problem returns. I am now running 64 bit 14.04 and the problem has been with me since at least 12.04. If I change the backlight color while the system is booting up but before the log in screen appears, I can select the color I want the keyboard to be, but if I wait till after the log in screen appears, then the mouse is non-functional when the desktop loads until I log off and back on. Here is some relevant data from a report on Ubuntu forums (http://ubuntuforums.org/showthread.php?t=2174670) about this exact problem... /dev/input/event5 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input0" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP /dev/input/event6 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input1" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC The feature that causes the problem here is the button to turn on/off/change the kb backlight color. input-events for /dev/input/event6: First press (backlight off->blue): emulates left click 19:43:40.885931: EV_MSC MSC_SCAN -16646143 19:43:40.885936: EV_KEY BTN_0 (0x100) pressed 19:43:40.885941: EV_MSC MSC_SCAN -16646140 19:43:40.885942: EV_KEY BTN_3 (0x103) released 19:43:40.885943: EV_SYN code=0 value=0 Second press (blue->red): emulates middle click 19:43:43.101984: EV_MSC MSC_SCAN -16646143 19:43:43.101989: EV_KEY BTN_0 (0x100) released 19:43:43.101992: EV_MSC MSC_SCAN -16646142 19:43:43.101992: EV_KEY BTN_1 (0x101) pressed 19:43:43.101996: EV_SYN code=0 value=0 Third press (red->purple): emulates right click 19:43:38.005865: EV_MSC MSC_SCAN -16646142 19:43:38.005869: EV_KEY BTN_1 (0x101) released 19:43:38.005871: EV_MSC MSC_SCAN -16646141 19:43:38.005872: EV_KEY BTN_2 (0x102) pressed 19:43:38.005874: EV_SYN code=0 value=0 Fourth press (purple->off) emulates ??? 19:43:39.765915: EV_MSC MSC_SCAN -16646141 19:43:39.765921: EV_KEY BTN_2 (0x102) released 19:43:39.765925: EV_MSC MSC_SCAN -1664614019 19:43:39.765926: EV_KEY BTN_3 (0x103) pressed 19:43:39.765928: EV_SYN code=0 value=0 So, the backlight changing on a keyboard act as different types of mouse clicks based on what color you switch to. Apparently this problem is also present in PCLinuxOS. Is this possibly a Udev issue? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,snap,move,vpswitch,regex,place,animation,session,imgpng,grid,gnomecompat,wall,resize,expo,unitymtgrabhandles,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Aug 4 09:47:36 2014 DistUpgraded: 2014-08-02 23:43:24,960 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1556] InstallationDate: Installed on 2009-11-04 (1733 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=59092ad5-f628-4cfa-859e-9236256eac88 ro quiet splash SourcePackage:
[Touch-packages] [Bug 1386834] Re: Second display stops working on repeated detection
** Tags removed: vivid -- 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/1386834 Title: Second display stops working on repeated detection Status in xorg package in Ubuntu: Triaged Bug description: The first time a secondary display/projector is connected to my laptop, it is detected and works in mirrored mode. However, once I open System Settings > Displays, the seconday display gets disabled. Loging out and rebooting doesn't solve the problem. At least not right away. A few reboots later secondary display starts working again. Occasioally I'm able to use Fn+F4 to switch between different modes (mirrored, extended), but it usually doesn't last long. As soon as System Settings is activated, the secondary display is disable and no longer detected. Additional clues: 1) If I leave a display plugged in and reboot, it is activated on login screen, but shuts off as soon as I login. Pressing 'Detect Displays' button is Displays settings does not bring it back. 2) Every time I open System Settings (even without external displayed plugged in) there is a short lag and even the moust stops moving for about a second. The following shows up in the log: Oct 28 11:34:12 hostname kernel: [ 649.193034] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 Oct 28 11:34:12 hostname kernel: [ 649.193038] [drm] PCIE gen 2 link speeds already enabled Oct 28 11:34:12 hostname kernel: [ 649.197195] [drm] PCIE GART of 1024M enabled (table at 0x00276000). Oct 28 11:34:12 hostname kernel: [ 649.197453] radeon :03:00.0: WB enabled Oct 28 11:34:12 hostname kernel: [ 649.197455] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880432d0cc00 Oct 28 11:34:12 hostname kernel: [ 649.197457] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880432d0cc04 Oct 28 11:34:12 hostname kernel: [ 649.197458] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880432d0cc08 Oct 28 11:34:12 hostname kernel: [ 649.197459] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880432d0cc0c Oct 28 11:34:12 hostname kernel: [ 649.197460] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880432d0cc10 Oct 28 11:34:12 hostname kernel: [ 649.198991] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90012535a18 Oct 28 11:34:12 hostname kernel: [ 649.388989] [drm] ring test on 0 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388994] [drm] ring test on 1 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388998] [drm] ring test on 2 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.389009] [drm] ring test on 3 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.389016] [drm] ring test on 4 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.574547] [drm] ring test on 5 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.574553] [drm] UVD initialized successfully. Oct 28 11:34:12 hostname kernel: [ 649.574583] [drm] ib test on ring 0 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574610] [drm] ib test on ring 1 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574637] [drm] ib test on ring 2 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574664] [drm] ib test on ring 3 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574692] [drm] ib test on ring 4 succeeded in 0 usecs Oct 28 11:34:13 hostname kernel: [ 649.725287] [drm] ib test on ring 5 succeeded 3) Some plugging and unplugging of the display occasionally shows the same messages in the log followed by the following: Oct 28 11:34:13 hostname kernel: [ 649.734010] snd_hda_intel :03:00.1: Enabling via VGA-switcheroo Oct 28 11:34:13 hostname kernel: [ 649.734117] snd_hda_intel :03:00.1: irq 70 for MSI/MSI-X Oct 28 11:34:18 hostname kernel: [ 654.876455] snd_hda_intel :03:00.1: Disabling via VGA-switcheroo Oct 28 11:34:18 hostname kernel: [ 654.908444] snd_hda_intel :03:00.1: Cannot lock devices! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 28 11:26:19 2014 DistUpgraded: 2014-10-24
[Touch-packages] [Bug 1442967] Re: [xorg-edgers] provide virtual nvidia-current driver
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1442967 Title: [xorg-edgers] provide virtual nvidia-current driver Status in xorg package in Ubuntu: Won't Fix Bug description: Default settings of applications like `bumblebee` depend on a `nvidia- current` driver. It'd be great if `nvidia-xyz` would provide a virtual driver `nvidia-current` like the Ubuntu packages for `nvidia-xyz` do. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 Uname: Linux 4.0.0-04rc7-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 349.12 Sun Mar 22 08:07:53 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 11 22:52:22 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3904] Subsystem: Lenovo Device [17aa:3904] InstallationDate: Installed on 2015-04-02 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: LENOVO 20221 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.0.0-04rc7-generic root=UUID=e4233f00-8032-4bed-b251-b4a24970189d ro rootflags=subvol=@ SourcePackage: xorg UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150330-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150318.27bf37ba-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150318.27bf37ba-0ubuntu0ricotz version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150401.61d2baa4-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Apr 11 17:30:11 2015 xserver.configfile: /etc/X11/xorg.conf xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1442967/+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 1439440] Re: Laptop does not go to sleep when closing lid with external monitor connected
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1439440 Title: Laptop does not go to sleep when closing lid with external monitor connected Status in xorg package in Ubuntu: Won't Fix Bug description: Using Dell Inspiron 15 3521 with Intel HD 4000 and an external monitor on HDMI output, in 15.04 beta 2: when closing the lid of the laptop, the laptop does not go to sleep (suspend to ram) as expected, but instead stays on, with the external monitor still on. I excepted that the laptop goes to sleep and the external monitor was blanked and turned off. This was the behavior on 14.10 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu4 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: Thu Apr 2 01:17:27 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0597] InstallationDate: Installed on 2015-04-01 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed root=UUID=cxxx---- ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0X dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06XXX:rvrA02:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron 3521 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Thu Apr 2 00:14:49 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 939 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439440/+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 1404332] Re: Touchpad cursor loses precision after VGA monitor plugged in
** Tags removed: ubuntu vivid -- 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/1404332 Title: Touchpad cursor loses precision after VGA monitor plugged in Status in xorg package in Ubuntu: Triaged Bug description: I just plug in the VGA cable. The external monitor is detected acc.to dmesg. A USB mouse works OK. The problem lies somewhere with synaptic driver. If I simply put down a finger on the touchpad and hold it still, the cursor still fidgets in random directions by a couple millimeter increments. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Dec 19 19:12:28 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] InstallationDate: Installed on 2014-10-02 (78 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:1721): WARNING **: Failed to load user image: Failed to open file '/home/developer23/.face': No such file or directory ** (lightdm-gtk-greeter:1721): WARNING **: Failed to load user image: Failed to open file '/home/default2/.face': Permission denied LightdmGreeterLogOld: ** (lightdm-gtk-greeter:7293): WARNING **: Failed to load user image: Failed to open file '/home/developer23/.face': No such file or directory (lightdm-gtk-greeter:7293): Gdk-WARNING **: lightdm-gtk-greeter: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. MachineType: ASUSTeK COMPUTER INC. X401A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=720d9c60-9be6-4623-a0c4-42a8f269bb44 ro persistent quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X401A1.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X401A1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX401A1.212:bd12/03/2012:svnASUSTeKCOMPUTERINC.:pnX401A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX401A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X401A1 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Dec 14 19:25:35 2014 xserver.configfile: default xserver.errors: ETPS/2 Elantech Touchpad: Read error 19 ETPS/2 Elantech Touchpad: Read error 19 ETPS/2 Elantech Touchpad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5234 vendor CMN xserver.version: 2:1.15.1-0ubuntu2.5 --- .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 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 DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu
[Touch-packages] [Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- 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/1444268 Title: [Lenovo ThinkPad T400] Screen corruption Status in xorg package in Ubuntu: Won't Fix Bug description: I often perceive massive screen corruption, most prominently in Firefox / GMail, but it may happen with any application, including terminals. Sometimes oversized letters appear. I run video stress tests, but they run without errors. I suspect the problem presents when many text needs to be rendered on-screen, as odd as it sounds. I will attach screenshots. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 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 Apr 15 07:23:31 2015 DistUpgraded: 2014-11-11 12:36:03,224 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2014-06-10 (308 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-11-11 (154 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474B84 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Apr 11 00:20:40 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16435 vendor LEN xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+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 1409166] Re: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration
** Tags removed: vivid -- 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/1409166 Title: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration Status in xorg package in Ubuntu: Triaged Bug description: Every time I boot, while I'm trying to enter my password in the initial login screen (from Unity?), a dialog box pops up saying "Could not switch the monitor configuration could not set the configuration for CRTC 65". The dialog box also steals the keyboard focus, which is very confusing if for some reason you're entering the password on an external display while the normally unused laptop display is not visible. For example, three times in a row this morning I rebooted and tried unsuccessfully to log in. Since the dialog box is only displayed on the laptop display, which I never use when external monitors are available, I had no idea why my keyboard seemed broken. Background: My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector. I have the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned above the laptop display. I have a Samsung monitor to the right of the Viewsonic. Since my laptop seems to only support two displays (which also seems true in Windows), I normally disable and totally ignore my laptop display, and may have papers propped up in front of it etc. Note that when I initially configured the third display I saw the following highly confusing behavior. From Settings I tried to add a Samsung monitor to the right of the Viewsonic, via a DVI-to-HDMI passive connector, and got this dialog box when I hit "Apply": The selected configuration for displays could not be applied could not set the configuration for CRTC 65 I clicked "OK" and got another dialog box: Failed to apply configuration: %s Can't add monitor: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 65 It works if I disable my laptop monitor, so it looks like the problem is with adding a third display. I would think it would be a pretty common use case to use two nice external displays and disable the laptop display. Even when the hardware can't handle a third display, the error messages should not be so confusing, and the login process shouldn't result in the keyboard being mysteriously stolen by a dialog box on a display which may never be visible. This is on Trusty 64-bit, up-to-date with upgrades. This bug seems similar to bug 1304627, but it seemed cleanest to get all the right information reported via ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 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: Fri Jan 9 15:35:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2203] InstallationDate: Installed on 2015-01-01 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GCET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET96WW(2.56):bd10/22/2013:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle
** Tags removed: vivid -- 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/1434351 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: Confirmed Bug description: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1467602] Re: after screenlock and screen suspend, external display port monitor doesn't resume properly
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1467602 Title: after screenlock and screen suspend, external display port monitor doesn't resume properly Status in xorg package in Ubuntu: Won't Fix Bug description: I have a Dell XPS 13 9343 with external display link monitor which I use in non-mirrored mode as two different screens. If the screen locks and suspends (simply locking is not enough) if I tap a key/move the mouse/etc the laptop screen comes up and the external monitor flashes on, but then the external monitor goes blank (but I can see its backlight is on). If I login, the desktop seems to think it is off and all of open windows are rearranged (it even puts some on different workspaces). The only thing resembling a workaround is if I tap a key, watch when the external monitor is blank, then turn off the external monitor, then turn it on, then unlock the screen. This isn't great though-- some windows are invisible and rearranged and I have to cycle through the different workspaces to find them and put them back. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 22 11:29:08 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-06-13 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 10:53:54 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5153 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to:
[Touch-packages] [Bug 1493170] Re: Fullscreen window goes to the background
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1493170 Title: Fullscreen window goes to the background Status in xorg package in Ubuntu: Won't Fix Bug description: Look at this: https://code.google.com/p/chromium/issues/detail?id=529097 I'm almost sure that it's a bug in Ubuntu, not in Chrome, and that I observe it in Chrome just because it's the only application I ever use that goes fullscreen. Note that it's not systematically reproducible, it's just random. When it starts happening there's no workaround other than logging out and in to Xorg. I guess it's related with other window-foreground-background-order- is-a-complete-mess bugs. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Sep 8 01:33:32 2015 DistUpgraded: 2015-08-15 21:46:56,607 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-25-generic, x86_64: installed bbswitch, 0.7, 3.19.0-26-generic, x86_64: installed vboxhost, 4.3.14, 3.13.0-61-generic, x86_64: installed vboxhost, 4.3.14, 3.16.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (696 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-08-15 (23 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Sep 8 01:32:42 2015 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): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1493170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1503491] Re: Mouse button stops working
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- 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/1503491 Title: Mouse button stops working Status in xorg package in Ubuntu: Won't Fix Bug description: The left button may not work because the mouse generates a constant pressing a service button. My mouse have "hidden" button 20-21-23, that "click" when I switch profiles. When all button is released, then mouse work as expected. In other cases, left button does not work anywhere else, although its operation can be seen in xinput, for example. I was able to get out of situation just by turning off the service button in the xorg.conf (writing zeros in their place): Section "InputClass" Identifier "Mouse Remap" ... Option "ButtonMapping" "1 2 3 4 5 0 0 8 9 10 11 12 13 14 15 16 17 18 19 0 0 0 0 0" ... EndSection ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 355.06 Tue Jul 28 21:26:50 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 7 03:44:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DpkgLog: GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7917] NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3170] MachineType: MSI MS-7917 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=14ae1968-3ddd-4a72-94a4-41f681469efe ro nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 5 (MS-7917) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7917 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.65+git20150922.f3c6740f-0ubuntu0ricotz~vivid version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0~git20150916+11.0.c4bae579-0ubuntu0sarvatt~vivid version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0~git20150916+11.0.c4bae579-0ubuntu0sarvatt~vivid version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 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 Oct 7 03:39:42 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1503491/+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 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor
** Tags removed: vivid -- 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/1467595 Title: cursor sometimes disappears on XPS 13 9343 and external monitor Status in Dell Sputnik: New Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using an external display port monitor. Occasionally, the mouse cursor disappears (sometimes after screen lock, other times just normal usage). I saw something on stack exchange that said this might help: gsettings set org.gnome.settings-daemon.plugins.cursor active false I've done this and it sometimes helps and sometimes doesn't. I've also just seen the cursor come back on its own after a few minutes without doing anything. Trying to interact with the touch screen, then the mouse has no effect. Unplugging and replugging the mouse has no effect. Using the touchpad has no effect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 22 11:19:40 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-06-13 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 10:53:54 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5153 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1467595/+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 1485258] Re: Nvidia 340+NVidia Prime + external monitor = system unusable, continuous xorg crashes, external monitor never works
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-prime (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1485258 Title: Nvidia 340+NVidia Prime + external monitor = system unusable, continuous xorg crashes, external monitor never works Status in X.Org X server: New Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-prime package in Ubuntu: Won't Fix Status in xorg package in Ubuntu: Won't Fix Bug description: SUMMARY - laptop with NVidia card and Optimus technology - xorg configured ages ago to automatically switch between built-in and external monitor when plugging/unplugging - "clean" Ubuntu 15.04 after upgrading from 14.10 from 14.04 - no nvidia-* nor bumblebee-* was installed (that's what I mean by "clean") - everything was working perfectly fine while only using integrated intel GPU - I installed NVidia-340 and nvidia-prime (and whatever) via Software & Updates -> Additional Driver Result: * Boot with external monitor connected => keeps crashing forever at the login screen * Boot without external monitor connected => seems to work with built-in screen (at least for the few minutes I tested) * Connect external monitor after boot at login screen => xorg crashes once or twice, then both screens go black * Connect external monitor after logging in => both screens go black * Disconnect external monitor => built-in screen remains black, never turns on again, unless Xorg crashes Basically, the laptop is completely unusable. NVidia-prime and nvidia-340 screw everything up beyond imagination. I was lucky tojust be able to recover from that, uninstall all nvidia-stuff, and get my working system back. MORE DETAIL Until recently I had Ubuntu 14.04. I had nvidia-331 installed but unused since ages ago. I had disabled them (if I remember correctly) by going to Software & Updates -> Additional drivers (the same I had used to install them) and choosing to use Nouveau instead (back), because I had experiencing a lot of glitches with NVidia-331. This was even before I upgraded to 14.04. Because my laptop has Optimus technology, I was only using the integrated Intel GPU. At some point I had also installed bumblebee, but I had never figured out how to actually make any use of it. I had Xorg configured so that, when plugging an external monitor, only the external monitor would be used and the built-in one would turn off; and when unplugging the external monitor, the built-in monitor would automatically turn on. So I only use one monitor at a time. I guess I configured this via the System Settings -> Displays All this was working fine. When the fix for #1431753 was released, nvidia-340 got installed and, against my will and without notice, they were somehow enabled, so I started experiencing #1220426 and #1483388 (but nothing comparable to what I'm describing in this report). So, I apt-get removed nvidia-* and bumblebee. After that (and across several reboots) all was working perfectly fine again. Again, I was only using the shitty integrated Intel GPU (without even the hardware acceleration that it supports, btw, but that's another story), but I had no issues. Then today I upgraded to 14.10 and immediately after, to 15.04. Everything kept working smoothly, including automatic screen switching when plugging/unplugging the external monitor. Then I thoughy I'd give NVidia-340 another try. I thought maybe a fresh install on 15.04 would work. I went to Software & updates -> Additional Drivers and I selected "use NVidia-340" That installed nvidia-340, nvidia-settings, nvidia-prime, and something-nvidia-else. I rebooted. At the first reboot, I had the external screen already connected. After the boot completed, xorg started to crash again and again like crazy. The login screen would appear and disappear from both screen at a few seconds intervals, and I would hear the drum sound every time (and could not finish typing my password and logging in). THE SYSTEM WAS UNUSABLE, I COULD NOT LOG IN. So
[Touch-packages] [Bug 1538865] Re: display arrangement fails to load after login
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1538865 Title: display arrangement fails to load after login Status in xorg package in Ubuntu: Won't Fix Bug description: Only a dialog with could not assign CRTCs to outputs: Trying modes for CRTC 63 CRTC 63: trying mode 1366x768@60Hz with output at 1366x768@60Hz (pass 0) none of the selected modes were compatible with the possible modes: Trying modes for CRTC 63 CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 64 CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 65 CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 66 CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1280x720@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1024x768@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1024x576@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 960x540@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 800x600@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 800x600@56Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 864x486@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 640x480@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 720x405@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 680x384@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 640x360@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1366x768@60Hz with output at 1366x768@60Hz (pass 1) none of the selected modes were compatible with the possible modes: Trying modes for CRTC 63 CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 64 CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 65 CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 66 CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 1280x720@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 1024x768@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 1024x576@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 960x540@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 800x600@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 800x600@56Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 864x486@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 640x480@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 720x405@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 680x384@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 640x360@60Hz with output at 1366x768@60Hz (pass 1) Trying modes for CRTC 64 CRTC 64: trying mode 1366x768@60Hz with output at
[Touch-packages] [Bug 1473087] Re: QT_PLUGIN_PATH is set in Kubuntu 15.04
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1473087 Title: QT_PLUGIN_PATH is set in Kubuntu 15.04 Status in xorg package in Ubuntu: Won't Fix Bug description: QT_PLUGIN_PATH is set in Kubuntu 15.04 that results to mixing Qt 5 libraries when third party Qt installed in the system. I.e. I installed Qt 5.5.0 with Qt Online Installer to my home directory and binaries such as assistant, designer doesn't start because of mixing Qt libraries with system's Qt 5.4.1. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 9 16:47:07 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-03 (67 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1473087/+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 1448574] Re: Have to use nomodeset for install (new problem for new distro)
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1448574 Title: Have to use nomodeset for install (new problem for new distro) Status in xorg package in Ubuntu: Won't Fix Bug description: I haven't had this problem since around version 12.04 or before (can't recall which one precisely) where, during installation, I have to use nomodeset in order to get my Samsung television to stop turning on and off repeatedly during modeset problems. I would like to mention that my television doesn't support an automatic shutoff mode which would normally cause it to turn off in a powersave situation, so being able to do that would be considered a new feature to me (one maybe worth exploring later). However, this last distro of 15.04 seems to have brought back the old problems with modeset that were once fixed, brought back, fixed again, and now brought back once more. Unfortunately, I can't give a log of this error due to the nature of the problem causing no visuals and my system deleting any log files upon reboot of the live boot. So, all I can suggest is to look into what changed that would cause modeset to break like this and try to change it back or add-in the fix to the code that existed before, if possible. Thanks! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 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 Apr 26 01:52:38 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3988] LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- nomodeset Renderer: Software SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: X99 Professional 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.50:bd01/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Professional:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 26 01:33:12 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7
[Touch-packages] [Bug 1448958] Re: xorg crash on xdmcp query
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Incomplete => Won't Fix -- 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/1448958 Title: xorg crash on xdmcp query Status in xorg package in Ubuntu: Won't Fix Bug description: Its not possible to start an XDMCP session on 15.04 X :1 -query localhost reported here, with patch. http://comments.gmane.org/gmane.comp.freedesktop.xorg.devel/44756 On my system it looks like this: X.Org X Server 1.17.1 Release Date: 2015-02-10 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu Current Operating System: Linux mvogt-ESPRIMO-P900 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root= UUID=19b64a42-57df-4059-a35b-85a17f427da2 ro quiet splash vt.handoff=7 Build Date: 19 March 2015 09:26:59AM xorg-server 2:1.17.1-0ubuntu3 (For technical support please see http://www.ubunt u.com/support) Current version of pixman: 0.32.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Mon Apr 27 11:53:55 2015 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (II) [KMS] Kernel modesetting enabled. (EE) Fatal server error: (EE) (EE) BUG: triggered 'if (f[f_idx])' (EE) BUG: ../../os/log.c:475 in vpnprintf() (EE) Unsupported printf directive '*' (EE) (EE) Backtrace: (EE) 0: X (xorg_backtrace+0x56) [0x7feccddde556] (EE) 1: X (0x7feccdc2b000+0x1c015f) [0x7feccddeb15f] (EE) 2: X (LogVMessageVerbSigSafe+0x4d) [0x7feccddeb9ed] (EE) 3: X (FatalError+0xea) [0x7feccddeb4ca] (EE) 4: X (0x7feccdc2b000+0x1c2a52) [0x7feccddeda52] (EE) 5: X (0x7feccdc2b000+0x1c2e4d) [0x7feccddede4d] (EE) 6: X (WakeupHandler+0x6b) [0x7feccdc87ddb] (EE) 7: X (WaitForSomething+0x1c3) [0x7feccdddb843] (EE) 8: X (0x7feccdc2b000+0x57ec1) [0x7feccdc82ec1] (EE) 9: X (0x7feccdc2b000+0x5c29b) [0x7feccdc8729b] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7feccb911a4 0] (EE) 11: X (0x7feccdc2b000+0x4662e) [0x7feccdc7162e] (EE) XDMCP fatal error: Session declined %*.*s ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Mon Apr 27 11:50:42 2015 InstallationDate: Installed on 2015-04-24 (2 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB DDR3 [174b:e164] InstallationDate: Installed on 2015-04-24 (9 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: FUJITSU ESPRIMO P900 Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=19b64a42-57df-4059-a35b-85a17f427da2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Tags: vivid ubuntu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/16/2011 dmi.bios.vendor: FUJITSU // American Megatrends
[Touch-packages] [Bug 1446919] Re: Unable to login after installing kubuntu-full and restarting. I am only able to login using"Ubuntu with Upstart" in the GRUB bootloader screen. "
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1446919 Title: Unable to login after installing kubuntu-full and restarting. I am only able to login using"Ubuntu with Upstart" in the GRUB bootloader screen. " Status in xorg package in Ubuntu: Won't Fix Bug description: I recently installed Ubuntu 15.04 in my system and then upgraded using "apt-get dist-upgrade" command. After upgrading, I restarted and then installed kubuntu-full package using "apt-get install kubuntu-full" command. I restarted after installing "kubuntu-full". I am not able to login after restarting my laptop. Laptop trackpad is not accessible and no mouse pointer is visible on login screen. Laptop keyboard is accessible only for issuing "REISUB" command. I am not able to access any virtual terminal. I am only able to login correctly by selecting "Ubuntu with Upstart" in the GRUB bootloader screen. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 21 19:57:24 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05f9] InstallationDate: Installed on 2015-04-20 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=d479ac04-b258-40bb-a3ec-828a28781860 ro quiet splash init=/sbin/upstart SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0TVJ73 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/24/2014:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0TVJ73:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Apr 21 01:35:21 2015 xserver.configfile: default xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 0 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1038 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1446919/+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 1678521] Re: package x11-common 1:7.7+7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1678521 Title: package x11-common 1:7.7+7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in xorg package in Ubuntu: Won't Fix Bug description: not able to upgrade. Not able to open software center ProblemType: Package DistroRelease: Ubuntu 15.10 Package: x11-common 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-76.98~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-76-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 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 Date: Sun Apr 2 01:05:12 2017 DistUpgraded: 2017-04-02 01:02:53,971 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: wily DistroVariant: ubuntu DpkgHistoryLog: Start-Date: 2017-04-02 01:04:50 Commandline: apt-get install gksu Install: libgksu2-0:amd64 (2.0.13~pre1-6ubuntu7, automatic), libgtop2-10:amd64 (2.30.0.is.2.30.0-0ubuntu1, automatic), gksu:amd64 (2.0.2-9ubuntu1) DuplicateSignature: package:x11-common:1:7.7+7ubuntu4:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06c0] InstallationDate: Installed on 2015-07-28 (613 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Vostro 3558 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-76-generic root=UUID=c883152a-3d7a-4196-822b-f45b94fc6a3b ro quiet splash radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: xorg Title: package x11-common 1:7.7+7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2017-04-01 (0 days ago) dmi.bios.date: 02/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 05JF1T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/09/2015:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn05JF1T:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-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: Sat Apr 1 16:30:59 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1568 vendor BOE xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1678521/+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 1653727] Re: infectado con arcivos cript desde windows seven
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1653727 Title: infectado con arcivos cript desde windows seven Status in xorg package in Ubuntu: Won't Fix Bug description: dicsco compartido con windos seven ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-74.82-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jan 3 10:47:22 2017 DistUpgraded: 2016-09-22 00:37:21,126 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Device [1019:3184] InstallationDate: Installed on 2015-02-16 (686 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: ECS H61H2-CM ProcEnviron: LANGUAGE=es_VE:es PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic root=UUID=8426958f-20c8-4974-b61a-da41d6109d75 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2016-09-22 (103 days ago) dmi.bios.date: 08/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: H61H2-CM dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/12/2011:svnECS:pnH61H2-CM:pvr:rvnECS:rnH61H2-CM:rvr1.0:cvnECS:ct3:cvr: dmi.product.name: H61H2-CM dmi.sys.vendor: ECS version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Jan 3 10:33:48 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSIGMACHIP Usb Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 59776 vendor LCD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653727/+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 1641293] Re: system freeze
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1641293 Title: system freeze Status in xorg package in Ubuntu: Won't Fix Bug description: I'm experiencing sudden system freeze. don't know why and also i also had freezing in windows 10. I hope you can help me to find out where it came from. monitor freeze and i cant do anything. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-74.82-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.8 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: Sat Nov 12 16:15:50 2016 DistUpgraded: 2016-11-11 22:37:46,435 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:124d] Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d] InstallationDate: Installed on 2016-11-11 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic root=UUID=900b7ae5-ca9a-4e6d-96b4-31230865e373 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to vivid on 2016-11-11 (0 days ago) dmi.bios.date: 06/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.213:bd06/26/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Nov 12 15:49:18 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): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 927 vendor LGD xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1641293/+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 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
** Tags removed: precise utopic wily -- 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/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: xset dpms force off; sleep 30; xset dpms force on WORKAROUND: A restart of the Xserver will bring back the display. WORKAROUND: Don't allow DPMS to switch off the display: xset dpms 0 0 0 xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+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 1516531] Re: Fullscreen Freeze.
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1516531 Title: Fullscreen Freeze. Status in xorg package in Ubuntu: Won't Fix Bug description: Related?: http://askubuntu.com/questions/692405/ubuntu-15-10-unity-freezes-after-escaping-full-screen-video https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622 I've been having cases of unusual screen behavior, particularly when Kodi 16 is being used (maybe it's just a Kodi thing). There have been times before when coming out of fullscreen video using either Chrome or Kodi would drop me to a console screen with no input. I think I would be able to kill the gnome session in tty1. Now, after a bios upgrade as well as the latest display manager and kernel update, Kodi has frozen in fullscreen a couple of times and yet audio will still play from Kodi. I created the bug report in tty1. I've also been noticing that if I pause a Kodi video, other non-Kodi applications may not update their window content. For example, I may be in a webpage in Chrome and I try to mousewheel scroll, yet not see the scrolling effect. Or I will click on a different tab and the window doesn't show the switch. BUT, if I continue playing the Kodi video, Chrome will update it's screen, and if I switch back to the tab I scrolled, the scroll will have already occurred. I will say that I have at least not had a fullscreen GUI crash me out to console. Another peculiarity is when booting Ubuntu, I used to be able to press ESC to view the kernel/system booting output, but now it just shows a black screen with a cursor. The downside to that in 15.04 was I'd lose my mouse cursor when the GUI login screen came up. Let me know what other output you'd like (or whatever test you'd like me to try) "when" it happens again. --- .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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 DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:041e] InstallationDate: Installed on 2015-10-28 (26 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash elevator=cfq vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: wily ubuntu compiz-0.9 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H97M-ITX/ac 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.80:bd07/27/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Touch-packages] [Bug 1490229] Re: Brightness set to maximum after DPMS standby
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1490229 Title: Brightness set to maximum after DPMS standby Status in xorg package in Ubuntu: Won't Fix Bug description: After configuring screen energy saving in KDE, I noticed that after DPMS standby, my screen brightness is set to maximum. This is confirmed by `cat /sys/class/backlight/intel_backlight/brightness`. The problem can be easily reproduce by switching to standby manually using `xset dpms force standby`. Steps to reproduce: 1) echo "300" | sudo tee /sys/class/backlight/intel_backlight/brightness 2) cat /sys/class/backlight/intel_backlight/brightness This will report: 300 3) xset dpms force standby 4) Move mouse/press key 5) cat /sys/class/backlight/intel_backlight/brightness This will report 937 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Aug 29 21:26:27 2015 InstallationDate: Installed on 2015-08-10 (20 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150809) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 BootLog: enabled, not active CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: kubuntu DkmsStatus: virtualbox, 5.0.4, 4.2.0-10-generic, x86_64: installed virtualbox, 5.0.4, 4.2.0-7-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13bd] InstallationDate: Installed on 2015-08-10 (40 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150809) Lsusb: Bus 001 Device 005: ID 03eb:8a0c Atmel Corp. Bus 001 Device 004: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX301LAA Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic.efi.signed root=UUID=103e34fc-23b4-497c-ac6b-791d423bee52 ro quiet splash acpi_osi= i915.powersave=1 i915.semaphores=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 drm.vblankoffdelay=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Tags: wily kubuntu single-occurrence reproducible has-workaround has-fix UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section "Extensions" Option"Composite" "Disabled" EndSection _MarkForUpload: True dmi.bios.date: 05/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.209:bd05/08/2014:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2:
[Touch-packages] [Bug 1529932] Re: X session crashes with EQ overflowing
** Tags removed: wily -- 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/1529932 Title: X session crashes with EQ overflowing Status in X.Org X server: Unknown Status in xorg package in Ubuntu: Triaged Bug description: On my very old laptop, that is equipped with an Ati Mobility Radeon X700, sometimes (and, sadly, I have to use this word, because I found no regularity pattern for the occurrence of this bug) randomly the desktop session locks, that is I can only move the mouse pointer, but I cannot interact anymore with the desktop session. I am forced to login trough ssh from another pc and to restart the laptop. In Xorg.0.log I found these lines that are, in my opinion, related to the crash: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e] (EE) 1: /usr/bin/X (mieqEnqueue+0x253) [0x5608e5689373] (EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152] (EE) 3: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026] (EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322] (EE) 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2] (EE) 6: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8] (EE) 7: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb] (EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9] (EE) 13: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c] (EE) 14: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236] (EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b] (EE) 16: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f] (EE) 17: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x11953) [0x7f5e4d984953] (EE) 18: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xe770) [0x7f5e4d981770] (EE) 19: /usr/bin/X (0x5608e54f3000+0x13ca51) [0x5608e562fa51] (EE) 20: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xf74f) [0x7f5e4d98274f] (EE) 21: /usr/bin/X (0x5608e54f3000+0x1332a2) [0x5608e56262a2] (EE) 22: /usr/bin/X (0x5608e54f3000+0x5818f) [0x5608e554b18f] (EE) 23: /usr/bin/X (0x5608e54f3000+0x5c34b) [0x5608e554f34b] (EE) 24: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f5e522e9a40] (EE) 25: /usr/bin/X (_start+0x29) [0x5608e55396c9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e] (EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152] (EE) 2: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026] (EE) 3: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322] (EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2] (EE) 5: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8] (EE) 6: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9] (EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c] (EE) 13: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236] (EE) 14: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b] (EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f] (EE) 16: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x11953) [0x7f5e4d984953] (EE) 17: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xe770) [0x7f5e4d981770] (EE) 18: /usr/bin/X (0x5608e54f3000+0x13ca51) [0x5608e562fa51] (EE) 19: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xf74f) [0x7f5e4d98274f] (EE) 20: /usr/bin/X (0x5608e54f3000+0x1332a2) [0x5608e56262a2] (EE) 21: /usr/bin/X (0x5608e54f3000+0x5818f) [0x5608e554b18f] (EE) 22:
[Touch-packages] [Bug 1565541] Re: Focused window is not always brought to front
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1565541 Title: Focused window is not always brought to front Status in xorg package in Ubuntu: Won't Fix Bug description: The following steps will systematically reproduce the issue. Terminal is only an example, you can do the same with any other application that can open multiple windows. - open three terminal windows - hit Ctrl+Super+D to show the Desktop. All windows disappear as expected - click on the Terminal icon in Launcher. One of the three windows is selected and brought to front as expected - click on the Terminal icon again - when presented with the three miniature windows, click on any of them except the one you previously selected Expected result: the selected terminal window should get focus AND be brought to front Observed result: the selected window is given focus but is not brought to front. Instead, another random one of the three is brought to front. The mere fact that the focused window is not the one on the top of the stack (i.e. the one most on the front) is in itself an inconsistency that should never exist and should be forbidden at the lowest conceivable level. Note that this is a HUGE SECURITY ISSUE and as such should be marked as critical. You can be typing (or sending keystrokes) into a window without even seeing it. Since one window is brought to front, you may not realise that it is not focused (though you can tell the difference if you look at it carefully enough), and hence you may for example hit several keys including Enter thinking that the selected windows is not responding, while infact your keystrokes are all processed by the invisible focused window. You may do random stuff on the invisible focused window. You could *literally* (and I'm not abusing the word "literally") wipe out your hard drive or publish your password on Facebook; or more likely, delete files or do all kind of irreversible damages to some document of yours. Note that I reported a somewhat similar issue where a random window is focused instead of the clicked one but that's a different bug (it still happens, but I don't know how to reproduce it systematicall), and another one regarding the focused window not having the title bar and borders, but that's different too and that particular one seems to be fixed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 3 21:38:07 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (905 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2016-01-18 (76 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias:
[Touch-packages] [Bug 1560804] Re: kscreen reports change of primary screen without apparent reason
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1560804 Title: kscreen reports change of primary screen without apparent reason Status in xorg package in Ubuntu: Won't Fix Bug description: Screen blanks out to black frequently for no apparent reason no matter how short or long the session. Also, in the items attached below was created using "xdiagnose". It didn't include SDDM.log which I am using but instead LightDM which I am *not* using. = From Xorg.0.log: Mar 22 21:53:53 HINGE11 org.kde.KScreen[2724]: message repeated 15 times: [ kscreen: Primary output changed from KScreen::Output(Id: 591 , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 591 , Name: "HDMI-0" ) ( "HDMI-0" )] == ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Tue Mar 22 21:52:10 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:34d6] InstallationDate: Installed on 2012-09-14 (1286 days ago) InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120820.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic root=UUID=bfef49a0-28c1-480e-95b6-b010e6f905a8 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~wily version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~wily version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~wily version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Mar 22 21:31:59 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile:
[Touch-packages] [Bug 1506272] Re: Missing fonts and flickering font rendering
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- 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/1506272 Title: Missing fonts and flickering font rendering Status in xorg package in Ubuntu: Won't Fix Bug description: Nvidia GPU GTX 750, Intel CPU, running ubuntu mate daily ISO 2015-10-14 in live mode. WORKAROUND: Install the nvidia proprietary drivers. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 BootLog: Generating locales... en_US.UTF-8... done Generation complete. pwconv: failed to change the mode of /etc/passwd- to 0600 CasperVersion: 1.365 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Thu Oct 15 01:15:27 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3757] LiveMediaBuild: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20151014.1) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- Renderer: Software SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/12/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Oct 14 22:12:56 2015 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) AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506272/+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 1500387] Re: System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored
** Tags removed: wily -- 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/1500387 Title: System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored Status in Dell Sputnik: New Status in xorg package in Ubuntu: Incomplete Bug description: [Summary] System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored [Reproduce Steps] 1. System boots to a black screen 2. Close the lid and reopen it [Results] Expected: Normal boot Actual: Blank screen [Additional Information] CID: Base Image: Product Name: "Ubuntu 14.04.3 LTS" on Dell XPS 13 9343 BIOS Version: A05 Kernel Version: 3.13.0-63-generic CPU: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz GPU: Intel Corporation Broadwell-U Integrated Graphics (rev 09) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1500387/+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 1509697] Re: Black screen with mouse under 15.10
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1509697 Title: Black screen with mouse under 15.10 Status in xorg package in Ubuntu: Won't Fix Bug description: Whatver I use gdm or lightgdm and xfce, Unity, gnome, I always get a blackscreen after login under my user. Nothing to do then :-( ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: User Name 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Oct 24 20:19:47 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=c3822ccc-de24-4603-a0cc-72532e4f34c2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H77N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd07/31/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Oct 24 20:18:02 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputDELL DELL USB Laser Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509697/+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 1508407] Re: libre office impress display broken gradient in slide show
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1508407 Title: libre office impress display broken gradient in slide show Status in xorg package in Ubuntu: Won't Fix Bug description: While testing ubuntu gnome iso: 20151020, I have this issue: Libre office impress display broken gradient in slide show mode. When editing gradient displayed normally. attached screen shot i'm using Intel VGA ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libreoffice-impress 1:5.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 CurrentDesktop: GNOME Date: Wed Oct 21 10:27:37 2015 LiveMediaBuild: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151019) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5021] Subsystem: Lenovo Device [17aa:5021] LiveMediaBuild: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20DCA02WIA Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/iso/username-15.10-desktop-amd64.iso locale=en_US.UTF-8 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Tags: wily ubuntu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET46WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DCA02WIA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJ5ET46WW(1.17):bd07/15/2015:svnLENOVO:pn20DCA02WIA:pvrThinkPadE450:rvnLENOVO:rn20DCA02WIA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DCA02WIA dmi.product.version: ThinkPad E450 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Oct 26 03:07:28 2015 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1530 vendor BOE xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1508407/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1509792] Re: only function keys but not the regular keys working, acer aspire U5 620
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1509792 Title: only function keys but not the regular keys working, acer aspire U5 620 Status in xorg package in Ubuntu: Won't Fix Bug description: After installing Ubuntu on a new Acer aspire u5 620 I found that the wireless keyboard is not working properly (Keyboard: Acer KBRF96211). The mouse works just fine and I can use the arrow keys in the grub menu (so I am sure the usb plug is working). Moreover, I just realized, that while pressing Fn the function keys are working but not the regular keys (either with or without pressing the function key)?! I have tried it with 14.10 15.04 and 15.10. I disabled the touchscreen in the file 10-evdev.conf to make sure it does not interfere with the wireless keyboard but nothing changed. When I plug in a regular usb-keyboard it is recognized immediately and works fine. Did anyone experience this before? Can you think of a workaround to "establish contact" to the other keys on the keyboard? Or do you see a chance to obtain or adapt specific drivers? I really like Ubuntu and want to keep using it, any help would be appreciated ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 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 Oct 25 12:40:27 2015 DistUpgraded: 2015-10-25 08:41:39,601 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-31-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.2.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0859] Subsystem: Acer Incorporated [ALI] Device [1025:0859] InstallationDate: Installed on 2014-10-27 (363 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer Aspire U5-620 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=4b1b5f51-933c-44bc-a59b-9cd27b3a6af5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to wily on 2015-10-25 (0 days ago) dmi.bios.date: 03/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-A1 dmi.board.name: Aspire U5-620 dmi.board.vendor: Acer dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 13 dmi.chassis.vendor: Acer dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd03/28/2014:svnAcer:pnAspireU5-620:pvr:rvnAcer:rnAspireU5-620:rvr:cvnAcer:ct13:cvrToBeFilledByO.E.M.: dmi.product.name: Aspire U5-620 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sun Oct 25 12:17:19 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs:
[Touch-packages] [Bug 1509761] Re: Power management dims monitor when watching videos
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1509761 Title: Power management dims monitor when watching videos Status in xorg package in Ubuntu: Won't Fix Bug description: While watching a video either in a video player or in a browser, power management kicks in an shuts off the monitor after while when not using mouse/keyboard. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-17.20-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.93 Wed Aug 19 16:49:15 PDT 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 25 08:17:48 2015 DistUpgraded: 2015-10-22 21:48:58,435 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2847] InstallationDate: Installed on 2013-12-13 (680 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic root=UUID=cdd1103c-6c1d-4bd6-a0e3-f6be2698c7f5 ro nomdmonddf nomdmonisw SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to wily on 2015-10-22 (2 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: B75 Pro3 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.70:bd07/12/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB75Pro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sun Oct 25 07:55:54 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509761/+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 1512810] Re: laptop shows previous display after reopening the cover
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1512810 Title: laptop shows previous display after reopening the cover Status in xorg package in Ubuntu: Won't Fix Bug description: When the cover of my laptop is being closed while running it will show the previous display for some seconds after being reopened. Just after these seconds the lockscreen will show up. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 3 18:16:20 2015 DistUpgraded: 2015-10-28 00:03:04,139 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: wily DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3986] InstallationDate: Installed on 2015-08-13 (82 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 001 Device 003: ID 5986:055d Acer, Inc Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80ES ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=4842d481-f5d0-41c1-a614-769115c50b50 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-27 (6 days ago) dmi.bios.date: 06/06/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9CCN26WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo B50-30 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo B50-30 dmi.modalias: dmi:bvnLENOVO:bvr9CCN26WW(V2.04):bd06/06/2014:svnLENOVO:pn80ES:pvrLenovoB50-30:rvnLENOVO:rnLenovoB50-30:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoB50-30: dmi.product.name: 80ES dmi.product.version: Lenovo B50-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Nov 3 18:02:48 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5565 vendor CMN xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1512810/+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 1539046] Re: libGL error: failed to open drm device: Permission denied
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1539046 Title: libGL error: failed to open drm device: Permission denied Status in xorg package in Ubuntu: Won't Fix Bug description: After some update (unfortunately I'm not sure what) if I try to play a videofile (e.g. mpv movie.mkv) I get this error: libGL error: failed to open drm device: Permission denied I think from this message is not very clear why is that. I figured out I was not in "video" group: "id user_name" I had to do this: "usermod -aG video user_name " and then restart X (logout, login). After that it works again. So I suspect there is some problem there. Why libGL cannot be used without membership in video group or why a regular user is not in video group. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jan 28 12:54:51 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201, 4.2.0-25-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2248] InstallationDate: Installed on 2015-10-23 (96 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Hewlett-Packard HP ProBook 450 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic root=UUID=c9e0c6ee-c8a4-4d1a-a46e-a3b79c38f774 ro SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M74 Ver. 01.16 dmi.board.name: 2248 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 67.24 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM74Ver.01.16:bd11/26/2015:svnHewlett-Packard:pnHPProBook450G2:pvrA3008CD10003:rvnHewlett-Packard:rn2248:rvrKBCVersion67.24:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 450 G2 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Jan 27 22:49:34 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1125 vendor LGD xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1539046/+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 1535452] Re: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1535452 Title: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged Status in xorg package in Ubuntu: Won't Fix Bug description: I used to have my display settings so that only one external monitor would be used when available, and the laptop's builtin monitor would be disabled. When plugging and unplugging the external monitor (whether in the VGA or HDMI port), monitors would switch automatically, as is obviously expected. After upgrading from 15.04 to 15.10, as per bug #1535436, these settings were lost, and after reboot, the two monitors were both enabled in extended desktop mode (or whatever it's called). So I went to Settings -> Displays (while I had an HDMI monitor connected), and turned off the builtin display. That worked, but when unplugging the HDMI monitor, the builtin one remains turned off despite being the only available monitor. No matter how many times I plug and unplug the external HDMI monitor, the builtin one never turns on (the external one does work). This is a HUGE regression as it may leave you without screen. By plugging a monitor via the VGA port, it works as expected. I'm testing with the same monitors and cables (and computer) as I was using in 15.04 when everything worked fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:18:48 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-43-generic, x86_64: installed bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed nvidia-340, 340.96, 3.19.0-43-generic, x86_64: installed nvidia-340, 340.96, 4.2.0-23-generic, x86_64: installed vboxhost, 4.3.14: added GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
[Touch-packages] [Bug 1539936] Re: Udev problem
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1539936 Title: Udev problem Status in xorg package in Ubuntu: Won't Fix Bug description: Nautilus crash when trying to transfert photos & files from smartphone to PC. Unable to open external device such as memory card or external disk. Please help. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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 Date: Sat Jan 30 19:06:05 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:f920] Subsystem: Toshiba America Info Systems Device [1179:f922] InstallationDate: Installed on 2015-01-18 (377 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: TOSHIBA SATELLITE S50-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=636ecf23-6c30-4e44-8b9a-bfbdbe7c9f04 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.70 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.:bvr1.70:bd08/14/2014:svnTOSHIBA:pnSATELLITES50-B:pvrPSPQ6E-00Q008GR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE S50-B dmi.product.version: PSPQ6E-00Q008GR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Jan 30 15:39:42 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1096 vendor LGD xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1539936/+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 1567400] Re: Xorg message
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1567400 Title: Xorg message Status in xorg package in Ubuntu: Won't Fix Bug description: Display problem in virtual BOx ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Apr 7 14:13:06 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 5.0.14, 4.2.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-04-07 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=8177ee31-8aeb-48ee-a2b1-5bf9617c30a7 ro plymouth:debug drm.debug=0xe Renderer: Software SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Apr 7 14:01:16 2016 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1567400/+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 1577871] Re: Why does taking a screenshot leave grey rectangles on my screen?
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1577871 Title: Why does taking a screenshot leave grey rectangles on my screen? Status in xorg package in Ubuntu: Won't Fix Bug description: Taking screenshots results in grey rectangles on the screen. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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 Date: Tue May 3 13:12:40 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04ed] InstallationDate: Installed on 2016-04-16 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 620s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=9dd402f9-2db1-450c-b58b-a065f4bcb04f ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0GDG8Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd04/12/2011:svnDellInc.:pnInspiron620s:pvr00:rvnDellInc.:rn0GDG8Y:rvrA00:cvnDellInc.:ct3:cvr00: dmi.product.name: Inspiron 620s dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Apr 30 07:39:01 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech M570MOUSE, id 8 inputBTC USB Multimedia Keyboard KEYBOARD, id 9 inputBTC USB Multimedia Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577871/+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 1589056] Re: HDMI does not work
** Tags removed: wily -- 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/1589056 Title: HDMI does not work Status in xorg package in Ubuntu: Triaged Bug description: xrandr displays "HDMI-1 disconnected (normal left inverted right x axis y axis)" even if it is connected using a HDMI cable to a Samsung monitor (model S27B350H) that has both HDMI and VGA connectors. WORKAROUND: Use the Nvidia proprietary driver. Graphics by lspci -vvv: 01:00.0 VGA compatible controller: NVIDIA Corporation G84GLM [Quadro FX 570M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 30c5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: nouveau --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: root: clean, 247512/1281120 files, 1867600/512 blocks [[0;1;31mFAILED[0m] Failed to start Automatically refresh installed snaps. See 'systemctl status snapd.refresh.service' for details. [[0;32m OK [0m] Started Authenticate and Authorize Users to Run Privileged Tasks. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: 2016-06-24 18:11:48,939 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (228 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Tags: xenial ubuntu Uname: Linux 4.4.0-28-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-06-24 (12 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1589056/+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 1578027] Re: i cannot set hdmi second monitor correctly
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1578027 Title: i cannot set hdmi second monitor correctly Status in xorg package in Ubuntu: Won't Fix Bug description: it was working ok. I've moved to other hdmi device and after that couldn't configure the screen resolution again returning to the first hdmi tv that I was using ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 4 00:06:28 2016 InstallationDate: Installed on 2016-01-14 (110 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578027/+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 1455788] Re: key is repeated, but keyboard does not send scancodessssssss
** Tags removed: wily -- 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/1455788 Title: key is repeated, but keyboard does not send scancode Status in xorg package in Ubuntu: Triaged Bug description: I have found the repeat-key and stuck-key issue in different bug-reports but no working solution. My problem is, that sometimes a key is stuck within software and the character is printed in the rate configure for the keyboard. catch of KeyPress event, KeyRelease event sequence with "l" with xev, "f" is pressed to stop sequence: c KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 632900, (38,-8), root:(632,311), state 0x100, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) "l" XmbLookupString gives 1 bytes: (6c) "l" XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633234, (38,-8), root:(632,311), state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) "l" XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633234, (38,-8), root:(632,311), state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) "l" XmbLookupString gives 1 bytes: (6c) "l" XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633481, (38,-8), root:(632,311), state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) "l" XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633500, (38,-8), root:(632,311), state 0x0, keycode 41 (keysym 0x66, f), same_screen YES, XLookupString gives 1 bytes: (66) "f" XmbLookupString gives 1 bytes: (66) "f" XFilterEvent returns: False showkey does not print any scancodes: ~$ sudo showkey -s KB-Modus war ?UNBEKANNT? [ Wenn Sie das unter X probieren, muss es nicht funktionieren, da der X Server ebenfalls von /dev/console liest. ] Drücken Sie eine Taste (Programmende 10 s nach dem letzten Tastendruck)... 0x9c 0x20 0xa0 .. 0x20 0x21 0xa0 0x21 0xa1 0x31 0xb1 0x2d 0x2f 0xad 0xaf 0x24 0x26 0xa4 0x26 << "0x26"= pressed, "0xa6"= released 0xa6 0x21 0xa1 << "0x21"= pressed, "0xa1"= released == === uname -or 3.16.0-30-generic GNU/Linux Description: Ubuntu 14.04.2 LTS Release: 14.04 Netbook Gigabyte T1005 CPU Intel Atom N570 --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:b100] Subsystem: Gigabyte Technology Co., Ltd Device [1458:b100] InstallationDate: Installed on 2015-05-01 (36 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1249): WARNING **: Failed to load user image: Datei »/home/klaus/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden init: indicator-power-main-Prozess (1392) wurde von TERM-Signal beendet init: indicator-application-main-Prozess (1398) wurde mit dem Status 1 beendet MachineType: GIGABYTE T1005M/P Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic root=/dev/mapper/xubuntu--vg-root ro clocksource=acpi_pm quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Tags: trusty ubuntu Uname: Linux 3.16.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/30/2010 dmi.bios.vendor: GIGABYTE dmi.bios.version: F09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: T1005M/P dmi.board.vendor: GIGABYTE dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor:
[Touch-packages] [Bug 1442378] Re: 1002:4337 radeon driver on lubuntu 14.04-15.10 displays white flickering scan lines and occasional parts of the windows on external monitor
** Tags removed: vivid wily -- 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/1442378 Title: 1002:4337 radeon driver on lubuntu 14.04-15.10 displays white flickering scan lines and occasional parts of the windows on external monitor Status in xorg package in Ubuntu: Triaged Bug description: On a Compaq Presario 2500 laptop with an Ati IGP 345M graphics card, when connected to an external monitor ( SAMSUNG P2470HD - FullHD monitor/tv ) through a VGA analog connection, and using the latest open radeon driver on Lubuntu 14.04.2 with all the latest updates, when using the native resolution ( 1920x1080@60 ) of the monitor, and even at lower ones, except the lowest, there are small white lines flickering all over the display especially when there is movement in the windows or menus, and sometimes even small fragments of the window contents appear momentarily across different parts of the monitor. This does not happen when using a Windows XP installation on the same laptop with the same monitor and with the same D-Sub cable. I've tried to install the fglrx driver, but there seems to be none available for this card either on the AMD website nor on the additional drivers repository of lubuntu. Installing the fglrx driver, the card was never recognised. The command "sudo amdconfig --initial" returns the error message: "amdconfig: No supported adapters detected". --- ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: 2014-08-20 18:45:34,637 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS200M [Radeon IGP 330M/340M/345M/350M] [1002:4337] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon IGP 345M [103c:0850] InstallationDate: Installed on 2014-05-11 (511 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1405): WARNING **: Failed to load user image: Failed to open file '/home/pai/.face': No such file or directory g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Presario 2500 (DP877E) Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: i386 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=14f7c35f-caf9-4149-b29a-3423e08c9b33 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Tags: trusty ubuntu Uname: Linux 3.13.0-49-generic i686 UpgradeStatus: Upgraded to trusty on 2014-08-20 (410 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/29/2003 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: KF_KH.F.13 dmi.board.name: 0850 dmi.board.vendor: Hewlett-Packard dmi.board.version: NS570 Version PQ1B56 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrKF_KH.F.13:bd08/29/2003:svnHewlett-Packard:pnPresario2500(DP877E):pvrKH.F.13:rvnHewlett-Packard:rn0850:rvrNS570VersionPQ1B56:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: Presario 2500 (DP877E) dmi.product.version: KH.F.13 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Oct 5 14:12:41 2015 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard
[Touch-packages] [Bug 1432413] Re: Synaptic Touchpad xevents are hijacked under X
** Tags removed: wily -- 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/1432413 Title: Synaptic Touchpad xevents are hijacked under X Status in xorg package in Ubuntu: New Bug description: Synaptic Touchpad xevents are hijacked under X11. I have a problem with the synaptic touch-pad on my Acer Aspire that started around a week ago. The problem can be described as that there is a massive amount of xevents being generated and appearing to originate from the touch-pad even though the touch-pad is not used. I have tested the HW which seems to work fine. The test performed is to start a terminal session (Ctrl + Alt + 2) before the fault occurs and check the xevents by running ~$ sudo evtest /dev/input/eventX where the X to use is found in /proc/bus/input/devices and found by running ~$ cat /proc/bus/input/devices |grep mouse No matter how much the touch-pad is used will the console show the corresponding events which indicates that HW and driver works OK as long it is not under X When the problem has occurred (in Desktop mode) is it easy (but inconvenient) to get back to normal by key combo Fn+F7 twice, turn off touch-pad and then turn on again. And more, one can get unlucky in the sense that the generated events could click somewhere one do not want to click. During the problem is it impossible to use the mouse since it flies around (mostly going in a bottom to top of screen direction) but one can check the generated events using evtest again. How can I help troubleshooting the problem? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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 Mar 15 19:51:13 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0933] InstallationDate: Installed on 2015-02-21 (22 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Acer Aspire E3-112 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=a97d0b51-4244-48ca-ba87-bc3a38a8b62d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-112 dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 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: Sun Mar 15 18:59:07 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1576 vendor BOE xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432413/+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 1313170] Re: systemsettings > Display Configuration shows bogus monitor
** Tags removed: vivid wily -- 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/1313170 Title: systemsettings > Display Configuration shows bogus monitor Status in xorg package in Ubuntu: Triaged Bug description: Starting from Kubuntu 14.04, when I open systemsettings > Monitor > Display Configuration, I see, additionally to my built-in monitor on my laptop (Samsung RF511 - monitor displayed as "Seiko Epson Corporation"...) an additional screen named "VGA-1-2" - which is enabled. This "monitor" is detected despite it does not exist. I discovered that because some apps I started did not appear on screen, and the mouse cursor somehow "vanished" behind the right screen edge, until I found out that they were placed on that second screen - I could "drag" the windows per Alt+LeftClick blindly from somewhere in the right to my actual monitor. a screnshot of systemsettings is attached. Then I attached a *real* second monitor to my laptop - systemsettings detects it correctly and expands the screen - but now tells me that I have *three* monitors... This is really a regression to 13.10, and as the monitor is detected *and* enabled by default, it is not really good to work with, as windows are "vanishing" somwehere. I can reproduce this behaviour with a Kubuntu live ISO on my system. So it is NOT my misconfiguration ;-) I before had Kubuntu 13.10 with KDE 4.12.5, running well without this bug. I am using a laptop with optimus graphics: intel/nvidia card, corresponding lspci lines: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 3D controller: NVIDIA Corporation GF108M [GeForce GT 540M] (rev a1) What else (log files etc) do you need from me to help resolve this bug? --- .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.5 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 DistUpgraded: 2015-05-21 14:12:51,319 DEBUG enabling apt cron job DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.30, 3.19.0-26-generic, x86_64: installed vboxhost, 4.3.30, 3.19.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0a5] InstallationDate: Installed on 2015-02-25 (213 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Tags: vivid ubuntu compiz-0.9 Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-21 (128 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 10HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr10HX.M034.20110426.SSH:bd04/26/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr10HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr10HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: RF511/RF411/RF711 dmi.product.version: 10HX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
[Touch-packages] [Bug 1501658] Re: 10de:1381 [Asus B85M-E] Missing fonts and flickering font rendering
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- 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/1501658 Title: 10de:1381 [Asus B85M-E] Missing fonts and flickering font rendering Status in xorg package in Ubuntu: Won't Fix Bug description: When starting from the live iso the fonts flicker and some are missing. When mousing over them they return but then they disappear as soon as you remove the mouse from the top of them. After installing xorg-edgers/ppa and applying the newest nvidia drivers with intel microcode the font issue disappears. --- ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84f0] InstallationDate: Installed on 2015-10-03 (0 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: ASUS All Series Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=d180a4a2-556c-4b1e-b6a5-7f1dd2ab746f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Renderer: Software Tags: wily ubuntu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2304 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2304:bd05/25/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Oct 3 18:12:03 2015 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) AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu7 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1501658/+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 1497264] Re: Upgrade from 15.04 breaks serial Wacom
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- 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/1497264 Title: Upgrade from 15.04 breaks serial Wacom Status in xorg package in Ubuntu: Won't Fix Bug description: Both a fresh install of Xubuntu 15.04 and upgrading from 14.10 break the Wacom and touchscreen functionality on my thinkpad X201 tablet. This function worked in both 14.04, and eventually in 14.10. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 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: XFCE Date: Fri Sep 18 08:43:22 2015 DistUpgraded: 2015-09-18 08:36:24,296 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:215a] InstallationDate: Installed on 2015-09-18 (0 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) LightdmGreeterLog: ** (lightdm-gtk-greeter:856): WARNING **: Failed to load user image: Failed to open file '/home/eight/.face': No such file or directory g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. upstart: indicator-power main process (880) killed by TERM signal upstart: indicator-application main process (882) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1426): WARNING **: Failed to load user image: Failed to open file '/home/eight/.face': No such file or directory g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: LENOVO 3093AH9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=d01d31f3-4ca6-4e5c-9a59-1ebebe22fbc9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-09-18 (0 days ago) dmi.bios.date: 12/17/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET62WW (1.32 ) dmi.board.name: 3093AH9 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:bvr6QET62WW(1.32):bd12/17/2010:svnLENOVO:pn3093AH9:pvrThinkPadX201Tablet:rvnLENOVO:rn3093AH9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3093AH9 dmi.product.version: ThinkPad X201 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 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: Fri Sep 18 08:37:03 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16401 vendor LEN xserver.version: 2:1.17.1-0ubuntu3~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1497264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1493921] Re: X server fails to set correct mode on resume from sleep (NVIDIA: Setting a mode on head 0 failed: An invalid mode was requested)
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Incomplete => Won't Fix -- 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/1493921 Title: X server fails to set correct mode on resume from sleep (NVIDIA: Setting a mode on head 0 failed: An invalid mode was requested) Status in xorg package in Ubuntu: Won't Fix Bug description: Using a really picky Dell P2415Q monitor through DP->mDP (displayport -> mini displayport) cable, nvidia binary driver version 352.30-0ubuntu1. This is not a laptop, so the Intel integrated VGA is disabled. (No other cards in sysfs.) Really nasty bug, as every time all the running applications detect that the X server went away and exit, logind terminates the session culling everyone, and so on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.30 Tue Jul 21 18:53:45 PDT 2015 GCC version: gcc version 5.2.1 20150825 (Ubuntu 5.2.1-15ubuntu5) ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Wed Sep 9 17:56:53 2015 DistUpgraded: 2014-08-06 01:18:55,244 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3614] MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fba348ec-fc7c-4c7f-b78b-026be76c4568 ro crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2014-08-05 (399 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F18 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF18:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Sep 9 15:10:08 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech G100s Optical Gaming Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1493921/+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 1610666] Re: Mouse cursor moves choppy/doesn't update its position as it should
** Tags removed: wily -- 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/1610666 Title: Mouse cursor moves choppy/doesn't update its position as it should Status in xorg package in Ubuntu: Triaged Bug description: Q. What I expected to happen? A. The mouse would run smoothly as it does run in windows. Q. What happened instead? A. The mouse lags moves choppy/doesn't update its position as it should Additional Information: Output of "xinput --list --short" ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ E-Signal USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ E-Signal USB Gaming Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Microsoft® LifeCam HD-3000 id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] Output of "xinput --list-props 11" Device 'E-Signal USB Gaming Mouse': Device Enabled (133):1 Coordinate Transformation Matrix (135): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (259): 0 Device Accel Constant Deceleration (260):1.00 Device Accel Adaptive Deceleration (261):1.00 Device Accel Velocity Scaling (262): 10.00 Device Product ID (251): 1241, 41132 Device Node (252): "/dev/input/event4" Evdev Axis Inversion (263): 0, 0 Evdev Axes Swap (265): 0 Axis Labels (266): "Rel X" (143), "Rel Y" (144), "Rel Horiz Wheel" (257), "Rel Vert Wheel" (258) Button Labels (267): "Button Left" (136), "Button Middle" (137), "Button Right" (138), "Button Wheel Up" (139), "Button Wheel Down" (140), "Button Horiz Wheel Left" (141), "Button Horiz Wheel Right" (142), "Button Side" (255), "Button Extra" (256), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254) Evdev Scrolling Distance (268): 1, 1, 1 Evdev Middle Button Emulation (269): 0 Evdev Middle Button Timeout (270): 50 Evdev Third Button Emulation (271): 0 Evdev Third Button Emulation Timeout (272): 1000 Evdev Third Button Emulation Button (273): 3 Evdev Third Button Emulation Threshold (274):20 Evdev Wheel Emulation (275): 0 Evdev Wheel Emulation Axes (276):0, 0, 4, 5 Evdev Wheel Emulation Inertia (277): 10 Evdev Wheel Emulation Timeout (278): 200 Evdev Wheel Emulation Button (279): 4 Evdev Drag Lock Buttons (280): 0 Output of "lsusb" Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 0bc2:3321 Seagate RSS LLC Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 04d9:a0ac Holtek Semiconductor, Inc. Bus 001 Device 003: ID 045e:0779 Microsoft Corp. LifeCam HD-3000 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note : Holtek Semiconductor, Inc. is my mouse Also found this in dmesg : [ 292.597380] usb 1-1.4: new full-speed USB device number 5 using ehci-pci [ 293.941408] usb 1-1.4: New USB device found, idVendor=04d9, idProduct=a0ac [ 293.941413] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 293.941416] usb 1-1.4: Product: USB Gaming Mouse [ 293.941418] usb 1-1.4: Manufacturer: E-Signal [ 294.241702] input: E-Signal USB Gaming Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:04D9:A0AC.0004/input/input16 [ 294.242160] hid-generic 0003:04D9:A0AC.0004: input,hidraw0: USB HID v1.10 Mouse [E-Signal USB Gaming Mouse] on usb-:00:1a.0-1.4/input0 [ 294.841559] input: E-Signal USB Gaming Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:04D9:A0AC.0005/input/input17 [ 294.897825] hid-generic 0003:04D9:A0AC.0005: input,hiddev0,hidraw1: USB HID v1.10 Keyboard [E-Signal USB Gaming Mouse] on usb-:00:1a.0-1.4/input1 [ 295.241685] hid-generic 0003:04D9:A0AC.0006:
[Touch-packages] [Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
** Changed in: xorg (Ubuntu) Status: Incomplete => Won't Fix -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Won't Fix Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1824864] Re: CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag 'verification-needed-disco' to 'verification-failed-disco'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-disco
--
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/1824864
Title:
CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
New
Status in linux source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
New
Status in linux source package in Cosmic:
Confirmed
Status in systemd source package in Cosmic:
New
Status in linux source package in Disco:
Fix Committed
Status in systemd source package in Disco:
New
Status in linux source package in Eoan:
Confirmed
Status in systemd source package in Eoan:
New
Bug description:
[Impact]
* Too small dmsg kernel buf ring size leads to loosing/missing early
boot kernel messages which happen before journald starts slurping them
up and storing them on disc. This results in messages similar to this
one on boot "missed NN kernel messages on boot". This is especially
pronounced on arm64 as the default setting there is way lower than any
other 32bit or 64bit architecture we ship. Also amd64 appears to have
the highest setting of 18 among all architectures we ship. The best
course of action to bump all 64bit arches to 18, and keep all 32bit
arches at the current & upstream default of 17.
[Test Case]
* $ cat /boot/config-`uname -r` | grep CONFIG_LOG_BUF_SHIFT
on 64bit arches result should be: CONFIG_LOG_BUF_SHIFT=18
on 32bit arches result should be: CONFIG_LOG_BUF_SHIFT=17
* run systemd adt test, the boot-and-services test case should not
fail journald tests with "missed kernel messages" visible in the error
logs.
[Regression Potential]
* Increasing the size of the log_buf, will increase kernel memory
usage which cannot be reclaimed. It will now become 256kb on arm64,
ppc64el, s390x instead of 8kB/128kb/128kb respectively. 32bit arches
remain unchanged at 128kb.
[Other Info]
* Original bug report
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on
amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux
kernel command line in the dmesg (journalctl -k -b). And it is
consistently failing on arm64 scalingstack KVM EFI machines with
messages of "missing 81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default
across 32-bit arches, and 18 is default on amd64.
On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT
policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el':
'13', 's390x': '13'}>
I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.
Please backport this to xenial and up.
=== systemd ===
systemd, boot-and-services test case can bump the ring buffer before
running the tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864/+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 1829484] [NEW] krb5-multidev dependency broken with ESM Trusty Repo
Public bug reported: When trying to install 'krb5-multidev' on Ubuntu 14.04 (Trusty) with the ESM Repository enabled apt responds with this: ``` /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install krb5-multidev ... The following packages have unmet dependencies: krb5-multidev : Depends: libkrb5-3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libk5crypto3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libgssapi-krb5-2 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed ``` I assume, due to the equality matches here this means the appropriate dependencies cannot be installed because ESM already delivers newer ones. System Information: $lsb_release -rd Description:Ubuntu 14.04.6 LTS Release:14.04 $ apt-cache policy krb5-multidev krb5-multidev: Installed: (none) Candidate: 1.12+dfsg-2ubuntu5.4 $ apt-cache policy libk5crypto3 libk5crypto3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libgssapi-krb5-2 libgssapi-krb5-2: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libkrb5-3 libkrb5-3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Tags: esm trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1829484 Title: krb5-multidev dependency broken with ESM Trusty Repo Status in krb5 package in Ubuntu: New Bug description: When trying to install 'krb5-multidev' on Ubuntu 14.04 (Trusty) with the ESM Repository enabled apt responds with this: ``` /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install krb5-multidev ... The following packages have unmet dependencies: krb5-multidev : Depends: libkrb5-3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libk5crypto3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libgssapi-krb5-2 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed ``` I assume, due to the equality matches here this means the appropriate dependencies cannot be installed because ESM already delivers newer ones. System Information: $lsb_release -rd Description:Ubuntu 14.04.6 LTS Release:14.04 $ apt-cache policy krb5-multidev krb5-multidev: Installed: (none) Candidate: 1.12+dfsg-2ubuntu5.4 $ apt-cache policy libk5crypto3 libk5crypto3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libgssapi-krb5-2 libgssapi-krb5-2: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libkrb5-3 libkrb5-3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1829484/+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 1829484] Re: krb5-multidev dependency broken with ESM Trusty Repo
Note that this affects all packages depending on this, e.g.: /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install percona-xtrabackup-24 Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: percona-xtrabackup-24 : Depends: libcurl4-openssl-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install percona-xtrabackup-24 libcurl4-openssl-dev ... libcurl4-openssl-dev : Depends: libkrb5-dev but it is not going to be installed $ /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install percona-xtrabackup-24 libcurl4-openssl-dev libkrb5-dev ... libkrb5-dev : Depends: krb5-multidev (= 1.12+dfsg-2ubuntu5.4) but it is not going to be installed $ /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install percona-xtrabackup-24 libcurl4-openssl-dev libkrb5-dev krb5-multidev ... The following packages have unmet dependencies: krb5-multidev : Depends: libkrb5-3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libk5crypto3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libgssapi-krb5-2 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1829484 Title: krb5-multidev dependency broken with ESM Trusty Repo Status in krb5 package in Ubuntu: New Bug description: When trying to install 'krb5-multidev' on Ubuntu 14.04 (Trusty) with the ESM Repository enabled apt responds with this: ``` /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install krb5-multidev ... The following packages have unmet dependencies: krb5-multidev : Depends: libkrb5-3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libk5crypto3 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed Depends: libgssapi-krb5-2 (= 1.12+dfsg-2ubuntu5.4) but 1.12+dfsg-2ubuntu5.4+esm1 is to be installed ``` I assume, due to the equality matches here this means the appropriate dependencies cannot be installed because ESM already delivers newer ones. System Information: $lsb_release -rd Description:Ubuntu 14.04.6 LTS Release:14.04 $ apt-cache policy krb5-multidev krb5-multidev: Installed: (none) Candidate: 1.12+dfsg-2ubuntu5.4 $ apt-cache policy libk5crypto3 libk5crypto3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libgssapi-krb5-2 libgssapi-krb5-2: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 $ apt-cache policy libkrb5-3 libkrb5-3: Installed: 1.12+dfsg-2ubuntu5.4+esm1 Candidate: 1.12+dfsg-2ubuntu5.4+esm1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1829484/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: Fix Released Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Released Status in libqmi source package in Bionic: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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
