[Touch-packages] [Bug 1830521] [NEW] package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: There is 1 error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apparmor 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: apparmor:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun May 26 12:20:33 2019 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2019-01-29 (116 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) KernLog: ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d069525a-3d3c-4c29-9f77-9e8a6233320d ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.1 SourcePackage: apparmor Syslog: Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.abstractions.dovecot-common: [modified] modified.conffile..etc.apparmor.d.abstractions.enchant: [modified] modified.conffile..etc.apparmor.d.abstractions.fcitx: [modified] modified.conffile..etc.apparmor.d.abstractions.fcitx-strict: [modified] modified.conffile..etc.apparmor.d.abstractions.launchpad-integration: [modified] modified.conffile..etc.apparmor.d.abstractions.ldapclient: [modified] modified.conffile..etc.apparmor.d.abstractions.nis: [modified] modified.conffile..etc.apparmor.d.abstractions.openssl: [modified] modified.conffile..etc.apparmor.d.abstractions.orbit2: [modified] modified.conffile..etc.apparmor.d.abstractions.p11-kit: [modified] modified.conffile..etc.apparmor.d.abstractions.php5: #backwards compatibility include, actual abstraction moved from php5 to php #include modified.conffile..etc.apparmor.d.abstractions.postfix-common: [modified] mtime.conffile..etc.apparmor.d.abstractions.X: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.apache2-common: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.change_profile: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.examine: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.find_mountpoint: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.introspect: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.is_enabled: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.aspell: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.audio: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.authentication: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.base: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.bash: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.consoles: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.cups-client: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.dbus: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.dbus-accessibility: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.dbus-accessibility-strict: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.dbus-session: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.dbus-session-strict: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.dbus-strict: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.dconf: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.dovecot-common: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.enchant: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.fcitx: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.fcitx-strict: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.fonts: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.freedesktop.org: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.gnome: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.gnupg: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.ibus: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.kde: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.kerberosclient: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.launchpad-integration: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.ldapclient: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.libpam-systemd: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.likewise: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.mdns: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.mir: 2018-04-18T01:45:16 mtime.conffile..etc.apparmor.d.abstractions.mozc
[Touch-packages] [Bug 1830531] [NEW] .local domain look ups do not trigger name publication
Public bug reported: On my local network I find that with 18.04 network name lookups using .local domains no not work unless stimulated by a non-18.04 machine first. This is observed for ssh, http, https and ping, but probably not limited to those. To demonstrate this here is a ping example. ~ $ ping pi.local ping: pi.local: Name or service not known ~ $ ping pi.local ping: pi.local: Name or service not known # At this point head to another machine running 16.04.6 and execute ping pi.local. # This is immediately successful. Then head back to the 18.04 machine. ~ $ ping pi.local PING pi.local (192.168.108.28) 56(84) bytes of data. 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms ^C --- pi.local ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 7018ms rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms After a couple of minutes, the name resolution fails again, but can be brought back again by following the procedure above. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: avahi-daemon 0.7-3.1ubuntu1.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_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 26 20:04:58 2019 InstallationDate: Installed on 2019-05-22 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1830531 Title: .local domain look ups do not trigger name publication Status in avahi package in Ubuntu: New Bug description: On my local network I find that with 18.04 network name lookups using .local domains no not work unless stimulated by a non-18.04 machine first. This is observed for ssh, http, https and ping, but probably not limited to those. To demonstrate this here is a ping example. ~ $ ping pi.local ping: pi.local: Name or service not known ~ $ ping pi.local ping: pi.local: Name or service not known # At this point head to another machine running 16.04.6 and execute ping pi.local. # This is immediately successful. Then head back to the 18.04 machine. ~ $ ping pi.local PING pi.local (192.168.108.28) 56(84) bytes of data. 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms ^C --- pi.local ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 7018ms rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms After a couple of minutes, the name resolution fails again, but can be brought back again by following the procedure above. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: avahi-daemon 0.7-3.1ubuntu1.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_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 26 20:04:58 2019 InstallationDate: Installed on 2019-05-22 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1830531/+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 1830531] Re: .local domain look ups do not trigger name publication
~ $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1830531 Title: .local domain look ups do not trigger name publication Status in avahi package in Ubuntu: New Bug description: On my local network I find that with 18.04 network name lookups using .local domains no not work unless stimulated by a non-18.04 machine first. This is observed for ssh, http, https and ping, but probably not limited to those. To demonstrate this here is a ping example. ~ $ ping pi.local ping: pi.local: Name or service not known ~ $ ping pi.local ping: pi.local: Name or service not known # At this point head to another machine running 16.04.6 and execute ping pi.local. # This is immediately successful. Then head back to the 18.04 machine. ~ $ ping pi.local PING pi.local (192.168.108.28) 56(84) bytes of data. 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms ^C --- pi.local ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 7018ms rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms After a couple of minutes, the name resolution fails again, but can be brought back again by following the procedure above. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: avahi-daemon 0.7-3.1ubuntu1.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_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 26 20:04:58 2019 InstallationDate: Installed on 2019-05-22 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1830531/+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 1830473] Re: Does not handle glyphless fonts, as used by tesseract
This bug was fixed in the package poppler - 0.76.1-0ubuntu3 --- poppler (0.76.1-0ubuntu3) eoan; urgency=medium * d/p/glyphless-font.patch: Support Tesseract's glyphless font (LP: #1830473) -- Julian Andres Klode Sat, 25 May 2019 12:31:14 +0200 ** Changed in: poppler (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1830473 Title: Does not handle glyphless fonts, as used by tesseract Status in Poppler: New Status in poppler package in Ubuntu: Fix Released Bug description: [Impact] PDF documents OCRed with tesseract show black boxes when selecting text [Test case] Run ocrmypdf on a pdf, open it in evince, select some text. You should not see black boxes. [Regression potential] The patch is minimal invasive and only changes the behavior for the tesseract glyphless font. [Other info] Upstream is unhelpfully refusing to merge the patch in https://gitlab.freedesktop.org/poppler/poppler/merge_requests/208 because it's not abstract enough for them (as it only handles tesseract). To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1830473/+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 1830537] [NEW] missing max_match_rules_per_connection
Public bug reported: Hi, I'm currently trying to debug why my Bluetooth Barcode scanner (emulating a keyboard) with a USB bluetooth dongle does not work anymore with my 18.04, can't connect it anoymore (it used to work at lease occasionally months ago.) It pairs, but can't be connected as a HID. One of the problems was that error message in /var/log/syslog: Connection ":1.182" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=2048) After adding 1024 2048 to the busconfig struct in /etc/dbus-1/system.d/bluetooth.conf at least this error message vanished (while others persist, still does not work). However, this should be in /etc/dbus-1/system.d/bluetooth.conf as delivered from the package and not require the user to debug and change. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 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 CurrentDesktop: XFCE Date: Sun May 26 14:37:28 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:2128 acl:0 sco:0 events:126 errors:0 TX bytes:4712 acl:0 sco:0 commands:106 errors:0 mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2019-05-26T14:29:51.468868 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1830537 Title: missing max_match_rules_per_connection Status in bluez package in Ubuntu: New Bug description: Hi, I'm currently trying to debug why my Bluetooth Barcode scanner (emulating a keyboard) with a USB bluetooth dongle does not work anymore with my 18.04, can't connect it anoymore (it used to work at lease occasionally months ago.) It pairs, but can't be connected as a HID. One of the problems was that error message in /var/log/syslog: Connection ":1.182" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=2048) After adding 1024 2048 to the busconfig struct in /etc/dbus-1/system.d/bluetooth.conf at least this error message vanished (while others persist, still does not work). However, this should be in /etc/dbus-1/system.d/bluetooth.conf as delivered from the package and not require the user to debug and change. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 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 CurrentDesktop: XFCE Date: Sun May 26 14:37:28 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TI
[Touch-packages] [Bug 1830538] [NEW] Can't get HIDP connection info
Public bug reported: Hi, I'm trying to use a Teemi TMSL-50 bluetooth barcode scanner (in keyboard emulation mode) with a USB bluetooth dongle in an 18.04 machine, which used to work some months ago. Now I can still pair them, the ubuntu machine sees the devices and lists as paired, but can't connect with human interface device service (HID). /var/log/syslog says May 26 14:44:49 machine1 bluetoothd[1272]: Can't get HIDP connection info May 26 14:44:51 machine1 bluetoothd[1272]: connect error: Invalid exchange (52) Since the scanner and the usb dongle are unchanged, it must be a problem of the ubuntu machine. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 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 CurrentDesktop: XFCE Date: Sun May 26 14:48:12 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:3400 acl:0 sco:0 events:192 errors:0 TX bytes:5012 acl:0 sco:0 commands:142 errors:0 mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2019-05-26T14:29:51.468868 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1830538 Title: Can't get HIDP connection info Status in bluez package in Ubuntu: New Bug description: Hi, I'm trying to use a Teemi TMSL-50 bluetooth barcode scanner (in keyboard emulation mode) with a USB bluetooth dongle in an 18.04 machine, which used to work some months ago. Now I can still pair them, the ubuntu machine sees the devices and lists as paired, but can't connect with human interface device service (HID). /var/log/syslog says May 26 14:44:49 machine1 bluetoothd[1272]: Can't get HIDP connection info May 26 14:44:51 machine1 bluetoothd[1272]: connect error: Invalid exchange (52) Since the scanner and the usb dongle are unchanged, it must be a problem of the ubuntu machine. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 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 CurrentDesktop: XFCE Date: Sun May 26 14:48:12 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:3400 acl:0 sco:0 events:192 errors:0 TX bytes:5012 acl:0
[Touch-packages] [Bug 1642767] Re: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.
I'm running umask 027 (set in `.bashrc` for my user, which is copied to my root session after using `su`) and can report this issue still occurs for unprivileged containers under Debian 9 (stretch, stable) using LXC 2.0.7-2+deb9u2 and kernel 4.19.0-0.bpo.4-amd64. I can also confirm umask at container creation time does not matter. Another symptom of this issue is that after it occurred, `sync` (both the utility and system call) and `update-initramfs` (which calls `sync`) start hanging. The comments to the [launchpad bug](https://discuss.linuxcontainers.org/t/cannot-stop-unprivileged- container-not-even-kill-9-its-systemd-process-on-host/1079) by the original author of this issue and [this](https://discuss.linuxcontainers.org/t/cannot-stop-unprivileged- container-not-even-kill-9-its-systemd-process-on-host/1079) thread contain a few discussions with regards to possible reasons this occurs. Also, is #2277 perhaps related? It took a long time before I traced this down to the umask, because the symptoms are bewildering. My original issue: https://superuser.com/questions/1439108/lxc-start-stop-hangs-and-filesystem-sync-hangs/1440273 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs. Status in lxc package in Ubuntu: Confirmed Bug description: If I have umask 007 (or any other value that masks the world-execute bit) when I run lxc-start for the first time after logging in, my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down the host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I can reproduce this at will with a freshly-installed and fully- updated host OS in VirtualBox, and with either an old-ish container or a new one. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't s
[Touch-packages] [Bug 1642767] Re: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs. Status in lxc package in Ubuntu: Confirmed Bug description: If I have umask 007 (or any other value that masks the world-execute bit) when I run lxc-start for the first time after logging in, my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down the host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I can reproduce this at will with a freshly-installed and fully- updated host OS in VirtualBox, and with either an old-ish container or a new one. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+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 1322024] Re: Make Hexchat the default IRC client instead of XChat in Ubuntu 14.10 and later versions
xchat is back, and Gianfranco wants to keep it. Also, I see little value in a transitional package or similar when they can't be upgraded from one to the other seamlessly. I'm therefore closing both tasks. ** Changed in: hexchat (Ubuntu) Status: New => Invalid ** Changed in: xchat (Ubuntu) Status: New => Opinion ** Changed in: xchat (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1322024 Title: Make Hexchat the default IRC client instead of XChat in Ubuntu 14.10 and later versions Status in hexchat package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in xchat package in Ubuntu: Invalid Bug description: Since XChat is no longer in development by it's main developer, I was thinking that maybe you guys should make HexChat the default IRC client for Ubuntu 14.10, if it isn't already the default IRC client in Ubuntu 14.04. It's a great IRC client, and it's much better than XChat. So I would really appreciate it if you guys could make HexChat the default IRC client in the next release of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hexchat/+bug/1322024/+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 1776652] Re: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
If the problem is corrected as stated by Mauricio Grueso (Above) Why has this not been fixed? His note was dated June of LAST YEAR! This fix might also fix the MANY other bugs of the same type I have encountered. I am no programmer so I really don't know how to incorporate Grueso's fix. Thank you, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1776652 Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: greetings excuse me english , i thinking that special configuration ubuntu for selinux may be have any situation that not working for different scenaries, because always the error say context error when execute mknod , may be no matter but is curios ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 13 06:29:07 2018 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-01-07 (522 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: initramfs-tools Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1776652/+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 1513437] Re: Incorrect default routing after vpnc completes
Launchpad has imported 26 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=758772. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-11-28T12:29:20+00:00 zebul666 wrote: I am using Ubuntu 15.10 with - network-manager 1.0.4-0ubuntu5.1 - network-manager-openvpn 0.9.10.0-1ubuntu2 And I configured my ethernet connexion to automatically use my openvpn vpn setup when connecting. If I go to dnsleaktest.com, I found out that networkamanager leaks my dns of my FAI provider and don't use the DNS of the VPN. However if I close and reopen manually the VPN conenction from networkmanager applet, the DNS leak does not occur anymore. So the bug occurs only when the VPN connection is set-up automatically when login or coming from sleep state. The DNS are not updated to the ones of the VPN and stays the one previously defined. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1513437/comments/6 On 2015-11-28T13:02:14+00:00 zebul666 wrote: no. I was wrong to assume it's because the automatic connection. Once the connection is up, dns could be ok but leaks 5 minutes later withtout the connection ever changing !!! so wtf ! Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1513437/comments/7 On 2015-11-28T13:52:56+00:00 zebul666 wrote: to make things clear, connection uses the LAN DHCP DNS instead of DNS of the VPN tunnel connection setup by network manager but it seems heratic Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1513437/comments/8 On 2015-11-29T10:02:53+00:00 zebul666 wrote: >From the NetworkManager log, it's clear than the previous (before establishing the VPN connection) DNS settings is retained by dnsmasq and not removed. So you end up with 3 DNS servers settings defined in dnsmasq after the VPN connection is setup, one of which is still the LAN/ISP DNS that causes the random DNS leak. That DNS entry should have deleted. I don't know if it's upstream bug or ubuntu. I have opened https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/1520771 which shows a work-around for the bug Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1513437/comments/9 On 2016-03-11T00:13:56+00:00 Forest wrote: I have observed this problem as well. Related: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120 Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1513437/comments/10 On 2016-04-05T06:21:35+00:00 Mincho-gaydarov wrote: I've filled a bug in redhat's bugzilla as I was unable to find this in the beginning. https://bugzilla.redhat.com/show_bug.cgi?id=1322932 I also experience this problem and it is not limited to NetworkManager configuration with dnsmaq. This bug appears also when NetworkManager is managing /etc/resolv.conf directly. Additional info: I've tested to deny access to 1-st and 2-nd NS servers from the machine running OpenVPS server and the result was that the local NS server was used, despite the fact that the checkbox 'Use this connection only for resources on its network' is unchecked. This leads to DNS leak if the first 2 NS servers could not be reached. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1513437/comments/11 On 2016-04-05T08:36:47+00:00 Thomas Haller wrote: this DNS issue has some similarities with route-management, where users want that once VPN connects no traffic is routed via other devices (bug 749376). NetworkManager currently doesn't understand a concept that activating a certain connection "vpn0" should prevent DNS/routing via another connection "eth0". For NM, there are just two connections active, both have DNS/routing configured (with differing priorities) and such is the outcome. But the existence/priorities don't affect each other. As current workaround, you have to ensure that when activating "vpn0" the untrusted connection "eth0-no-dns" on it's own doesn't provide the conflicting DNS/routes. Which would for example mean, you cannot specify the VPN gateway via DNS (because "eth0-no-dns" could not resolve it). Anyway, this is certainly a valuable feature. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1513437/comments/12 --
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Can someone experiencing this bug please report it to the PulseAudio developers? https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/new and then tell us the new bug ID. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1830516] Re: Avahi Printer advertisements are wrong (Avahi or CUPS?)
This is a bug in CUPS ultimately, it's driving Avahi using the D-BUS API (as opposed to manual service files in /etc/avahi/services, this is only really used for a sysadmin to manually add services, most other types of advertisements such as printers are expected to use the API to advertise it). Marking this against cups instead, you may also wish to consider filing it upstream: https://github.com/apple/cups ** Also affects: cups (Ubuntu) Importance: Undecided Status: New ** Changed in: avahi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1830516 Title: Avahi Printer advertisements are wrong (Avahi or CUPS?) Status in avahi package in Ubuntu: Invalid Status in cups package in Ubuntu: New Bug description: First I do not know if this is a CUPS issue or an Avahi issue. I do not know whether Avahi or CUPS generates the files nor where they are. They are not in /etc/avahi/services, where I expected to find them, so they must lie somewhere in CUPS. I have a printer installed in CUPS. I must use the driver from a different model to make it work. Among other things I want avahi and CUPS to show the printer name, consistently unless related to the print driver used. avahi-browse shows Xerox_Phaser-6125 @ Hostname (correct) Later however in Txt fields avahi-browse shows "product=(DocuPrint C525 A-AP)" .. "ty=FX DocuPrint C525 A-AP v1.0" (incorrect printer model but is the driver in use. Those fields should relate to Product and type, not driver) The problem above I suppose is the "trickle down effect" from how CUPS names the printer. In the CUPS web GUI I see Queue Name Description LocationMake and Model Status Xerox_Phaser-6125 Xerox_Phaser-6125 HomeFX DocuPrint C525 A-AP v1.0 Idle - "Waiting for printer to finish." The Make and Model is not Make and model at all, rather it comes from the driver used. I know it is commonplace to use say an HP LaserJet PS driver when you want PostScript , like back in the day when I printed to a LaserWriter, so I am not the only one that sees this. Also, I think there should be a proper "representation" in the txt fields as well icon as is done with AirScan/eSCL scanners advertisements "representation=http://HOSTNAME./images/Icon.png"; as I believe some apps will use this icon of the actual printer. This field should not be required but optional. These days we connect many different OSs to Linux and expect Linux to "do it all", and we still want it to look pretty and correct. I know Apple in some cases uses the "representation" field. This "representation" field too would have to tricke down from CUPS to Avahi, as Avahi would only point to the file at http://HOSTNAME:631/images/Icon.png. So it needs to hosted on the CUPS web GUI. I also recently read that some distros are moving away from the GUI utilities to configure printers in favor of the CUPS web GUI , making this more relevant than ever. Description: Ubuntu 16.04.4 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1830516/+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 1830531] Re: .local domain look ups do not trigger name publication
The most likely cause for this is that you have packets outbound on port 5353 firewalled either locally or on your network device. When another host pings the address, the responses are sent via multicast and Avahi caches that response, and so can then use it without having to transmit a packet. Until someone else looks it up, the cache is empty and the query packet is blocked, so no resolution happens. To confirm this, other than checking and clearing both iptables and nftables, you could try run tcpdump on your host and then on another host to see if you can see the packet generated locally, and then if it actually arrives on the network. Note that once avahi has the address in its cache, when it queries the network for it, it includes that address in the packet as "Known Answer" and the other host won't respond. So when testing this you are likely best to restart the local avahi daemon to clear it's cache before each test. You can see those "Known Answers" in the tcpdump though. Best viewed with wireshark as it makes decoding the DNS part easy. As a secondary test, I would suggest trying a different network adapter (possibly wired instead of wireless, or vica-versa) - you can also get these problems from weird drivers in some cases. Though usually broken drivers prevent you from RECEIVING multicast, and so manifests that this never works, so that seems unlikely in your case, but perhaps not impossible. As a third test try 'avahi-resolve-host-name' instead of ping, to isolate if "avahi" / multicast is the issue, as opposed to the nss-mdns layer. Going to mark this Invalid for now, however, if you can show from the packet dumps that the query packets are really not being sent at all even locally feel free to set the status back to New for further investigation. ** Changed in: avahi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1830531 Title: .local domain look ups do not trigger name publication Status in avahi package in Ubuntu: Incomplete Bug description: On my local network I find that with 18.04 network name lookups using .local domains no not work unless stimulated by a non-18.04 machine first. This is observed for ssh, http, https and ping, but probably not limited to those. To demonstrate this here is a ping example. ~ $ ping pi.local ping: pi.local: Name or service not known ~ $ ping pi.local ping: pi.local: Name or service not known # At this point head to another machine running 16.04.6 and execute ping pi.local. # This is immediately successful. Then head back to the 18.04 machine. ~ $ ping pi.local PING pi.local (192.168.108.28) 56(84) bytes of data. 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms ^C --- pi.local ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 7018ms rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms After a couple of minutes, the name resolution fails again, but can be brought back again by following the procedure above. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: avahi-daemon 0.7-3.1ubuntu1.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_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 26 20:04:58 2019 InstallationDate: Installed on 2019-05-22 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1830531/+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 1830358] Re: Screen flickering
Please try to take a video of the problem and attach it here. A video is important because it tells us what type of "flickering" we are dealing with. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1830358 Title: Screen flickering Status in Ubuntu: Incomplete Bug description: Using Intel Graphics HD 520 Constant flickering begins after some usage. Rebooting resolves the issue for a short while. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 24 06:42:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704] InstallationDate: Installed on 2019-04-05 (49 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=26ae1f0c-87cf-450a-82e8-a4034f51425d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1830358/+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 1830489] Re: I don't Know
** Package changed: xorg (Ubuntu) => 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/1830489 Title: I don't Know Status in Ubuntu: Incomplete Bug description: When the OP Unbuntu 18.04 inicializate! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sat May 25 12:35:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (59 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 24 21:29:22 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1830489/+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 1830408] Re: Do not see login screen after screen is blanked
Please: 1. Reproduce the problem again. 2. Use your workaround to recover. Do not reboot. 3. Run this command: journalctl -b0 > journal.txt 4. Send us the file 'journal.txt'. ** Tags added: nouveau ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Do not see login screen after screen is blanked + [nouveau] Do not see login screen after screen is blanked ** Package changed: linux (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1830408 Title: [nouveau] Do not see login screen after screen is blanked Status in gdm3 package in Ubuntu: Incomplete Bug description: I've just upgraded to 18.10 from 18.04. Now when power manager (or whoever) puts the screen to blank, I cannot login, because I do not see anything. Befeore the upgrade, mouse move or keypress led to login screen. Now does not. Workaround: When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears. Where is the problem and how to fix it please? 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' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 24 17:59:31 2019 DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1682] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682] InstallationDate: Installed on 2018-09-03 (263 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK Computer Inc. U36SD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago) dmi.bios.date: 07/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SD 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.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U36SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1830408/+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 1830503] Re: [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at all
** Summary changed: - [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all + [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at all -- 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/1830503 Title: [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: No sound Motherboard MSI B450 Tomahawnk CPU APU AMD Ryzen 5 2400G-4 Core RX Vega. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 26 00:08:58 2019 InstallationDate: Installed on 2019-05-22 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio Symptom_Jack: Red Line Out, Rear Symptom_Type: No sound at all Title: [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/19/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1830503/+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 1830531] Re: .local domain look ups do not trigger name publication
Before I get a chance to look into this later today, I'd like to note that the network device is not firewalling those packets since a few days ago before I installed 18.04 on this machine it was behaving as expected and the 16.04 machine mentioned in the OP is not being blocked (it is on a slightly more restrictive policy than this one, but neither block that port). As for the possibility of blocking outbound packets from the machine itself, this seems most likely, however, as mentioned, this is a new install and I have not added any firewalling policy that would block them, suggesting that it's an out of the box setting. I'll report back on these and the other tests when I am at that location. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1830531 Title: .local domain look ups do not trigger name publication Status in avahi package in Ubuntu: Incomplete Bug description: On my local network I find that with 18.04 network name lookups using .local domains no not work unless stimulated by a non-18.04 machine first. This is observed for ssh, http, https and ping, but probably not limited to those. To demonstrate this here is a ping example. ~ $ ping pi.local ping: pi.local: Name or service not known ~ $ ping pi.local ping: pi.local: Name or service not known # At this point head to another machine running 16.04.6 and execute ping pi.local. # This is immediately successful. Then head back to the 18.04 machine. ~ $ ping pi.local PING pi.local (192.168.108.28) 56(84) bytes of data. 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms ^C --- pi.local ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 7018ms rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms After a couple of minutes, the name resolution fails again, but can be brought back again by following the procedure above. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: avahi-daemon 0.7-3.1ubuntu1.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_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 26 20:04:58 2019 InstallationDate: Installed on 2019-05-22 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1830531/+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 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
I was now able to try a few different versions leading to the following results: * The bug does not affect kernel version 4.18.0-15 (Tested using a Live install of 18.04.2) * The bug does not affect kernel version 4.20.17-042017 (Tested on my install of 19.04 with a manually installed kernel) * The bug does not affect kernel version 5.0.1-050001 (Tested on my install of 19.04 with a manually installed kernel) * The bug does affect newly build kernel version 5.1.5-050105 (Tested on my install of 19.04 with a manually installed kernel) So the bug must be introduced between 4.20.17 and 5.0.0-15. I hope this can be a good starting point for troubleshooting. -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829621/+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 1667503] Re: El sistema es muy lento
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/1667503 Title: El sistema es muy lento Status in xorg package in Ubuntu: Won't Fix Bug description: Utilizo ubuntu 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-80.88-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 23 17:22:55 2017 DistUpgraded: 2017-01-09 00:45:28,018 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9803] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:9082] InstallationDate: Installed on 2016-08-20 (187 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: Sony Corporation VPCYB10AL ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=0eb47a11-7bd6-4d5a-90c7-29f4fae24f9f ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2017-01-09 (45 days ago) dmi.bios.date: 09/13/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0162Z7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0162Z7:bd09/13/2011:svnSonyCorporation:pnVPCYB10AL:pvrC9006R37:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCYB10AL dmi.product.version: C9006R37 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A 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: Thu Feb 23 17:19:06 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1667503/+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 1440929] Re: xrandr orientation black screen
Thank you for reporting this bug to Ubuntu. 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: 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/1440929 Title: xrandr orientation black screen Status in xorg package in Ubuntu: Won't Fix Bug description: writing xrandr -o 2 in console give me a black screen , but i can fix this locking the screen (ctrl+alt+L) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 Uname: Linux 3.19.3-031903-generic i686 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Apr 6 18:55:41 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.18-3.16, 1, 3.16.0-33-generic, i686: installed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a02] Subsystem: Lenovo Device [17aa:3a02] InstallationDate: Installed on 2015-03-24 (13 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1491): WARNING **: Failed to load user image: No se ha podido abrir el archivo «/home/juan/.face»: No existe el archivo o el directorio LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1545): WARNING **: Failed to load user image: No se ha podido abrir el archivo «/home/juan/.face»: No existe el archivo o el directorio MachineType: LENOVO 4233A11 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.3-031903-generic root=UUID=62983c56-bedc-4e0e-b26d-e59e3aafbdc5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 6GET18WW(V1.09) dmi.board.name: KIWDX dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr6GET18WW(V1.09):bd05/22/2009:svnLENOVO:pn4233A11:pvrLenovo3000N500:rvnLENOVO:rnKIWDX:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 4233A11 dmi.product.version: Lenovo 3000 N500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.0-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.0-0intel1 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.917-1~exp1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Apr 6 18:31:25 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id7681 vendor LPL xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1440929/+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 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
It sounds like you made a typo there. The points you list suggest the regression started between kernels 5.0.1 and 5.1.5: * The bug does not affect kernel version 5.0.1-050001 (Tested on my install of 19.04 with a manually installed kernel) * The bug does affect newly build kernel version 5.1.5-050105 (Tested on my install of 19.04 with a manually installed kernel) Yet your original bug description suggests the bug is in version 5.0.0-15.16-generic too, as does your summary in comment #6. Those conclusions conflict with the above listed findings, so please clarify... -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829621/+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 1422165] Re: xrandr query resets refresh rate to default setting
Thank you for reporting this bug to Ubuntu. 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: 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/1422165 Title: xrandr query resets refresh rate to default setting Status in xorg package in Ubuntu: Won't Fix Bug description: Hi, I faced this problem after upgrading from 14.04 to 14.10. Basically, when I switch display refresh rate using xrandr to some non-default value and then just run xrandr without any arguments, the rate resets to default. I can clearly see it as my TV is able to show current refresh rate. Also TV blinks after second xrandr invocation. So steps to reproduce are: 1. xrandr --output HDMI1 --mode 1920x1080 --rate 24 <-- TV switches to 24HZ and stays in this mode. 2. xrandr (or xrandr --nograb) <-- TV blinks and switches back to default 60HZ. The original problem was observed in Kodi (ex Xbmc) - it failed to enable (and still fails) 24HZ video refresh rate, I analyzed Kodi sources and found out that above mentioned steps are indeed used by Kodi to switch refresh rate. Note that fore some reason the switch to 50HZ refresh rate does NOT exibit the problem, but only to 24/25/30HZ (on my system). Short summary about my system: - 64Bit Ubuntu 14.10 (everything stock, Unity, all up-to-date) - TV Phillips 47PFL7108 - CPU Intel(R) Core(TM) i7-4765T - Video card (builtin) Intel® HD Graphics 4600 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Feb 15 21:14:35 2015 DistUpgraded: 2014-11-29 15:58:09,685 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2014-01-06 (405 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: GIGABYTE MSH81TN-00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic root=UUID=606d0fae-4275-4eb2-ad9b-f730da28cbc5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-11-29 (78 days ago) dmi.bios.date: 10/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MSH81TN-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x 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.:bvrF2:bd10/15/2013:svnGIGABYTE:pnMSH81TN-00:pvr1.x:rvnGIGABYTE:rnMSH81TN-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MSH81TN-00 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE 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.2 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: Sun Feb 15 20:21:04 2015 xserver.configfile:
[Touch-packages] [Bug 1412594] Re: System hangs when kstart used in autostart script
Thank you for reporting this bug to Ubuntu. 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: 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/1412594 Title: System hangs when kstart used in autostart script Status in xorg package in Ubuntu: Won't Fix Bug description: I was trying to use kstart to start three programs in three different desktops after login, like this: kstart --desktop 1 firefox kstart --desktop 2 kmail kstart --desktop 3 konsole After (apparently) executing the script, the system hung solidly. I tried this more elaborate version of the same thing: #! /bin/sh kstart --desktop 1 firefox & kstart --desktop 2 kmail & kstart --desktop 3 konsole & exit but the behavior was the same. I'm running Kubuntu 14.10 with release 4:4.14.2-0ubuntu1~ubuntu14.10~ppa1 of kde-runtime. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 19 18:12:06 2015 InstallationDate: Installed on 2015-01-10 (9 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) 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/1412594/+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 1683255] Re: wifi
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/1683255 Title: wifi Status in xorg package in Ubuntu: Won't Fix Bug description: internet disconections and low flow network manager is on but there is no connection and sometimes there is, and then it stops. and to restart i have to switch of wifi and on again and it wil work for a few minutes... ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22 Uname: Linux 3.19.0-84-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Apr 17 08:38:16 2017 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:226b] Subsystem: Hewlett-Packard Company Device [103c:226b] InstallationDate: Installed on 2017-04-13 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-84-generic root=/dev/mapper/ubuntu--gnome--vg-root ro 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: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 226B dmi.board.vendor: Hewlett-Packard dmi.board.version: 73.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn226B:rvr73.41:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A 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: Sun Apr 16 22:33:34 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1683255/+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 1406480] Re: Xorg freezes
Thank you for reporting this bug to Ubuntu. 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: 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/1406480 Title: Xorg freezes Status in xorg package in Ubuntu: Won't Fix Bug description: Symptoms: Xorg freezes completely. Audio kept going for a while but then stopped too. Mouse cursor is the only thing I can control on the screen. ctrl+alt+f1-7 don't seem to work. What I was doing at the time: Watching a youtube video and trying to connect a bluetooth gamepad. Report was gathered by ssh'ing from another machine. I can see that the Xorg.log contains a backtrace for the crash. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Dec 30 11:12:25 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:2553] InstallationDate: Installed on 2014-10-17 (73 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) 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 file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession 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 file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=f9b26eb7-84d6-4fba-8574-3966b80cdf3a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F16 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H77-D3H 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.:bvrF16:bd12/06/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-D3H: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.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 29 12:10:36 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2 xserver.video_driver: radeon To manage notifications abou
[Touch-packages] [Bug 1412766] Re: Duplicated mouse cursor on top of every window
Thank you for reporting this bug to Ubuntu. 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: 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/1412766 Title: Duplicated mouse cursor on top of every window Status in xorg package in Ubuntu: Won't Fix Bug description: For some reason a second mouse cursor appeared in the center of the screen and shows over all the screens that are currently open. I'm using Ubuntu Studio 14.10, and this usually happens after hibernation (and some times after locking the screen). $ lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [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)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ WebCam SC-13HDL11939N id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-lowlatency 3.16.7-ckt2 Uname: Linux 3.16.0-29-lowlatency x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jan 20 09:57:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-07 (12 days ago) InstallationMedia: Ubuntu-Studio 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.20, 3.16.0-28-lowlatency, x86_64: installed vboxhost, 4.3.20, 3.16.0-29-lowlatency, x86_64: installed vboxhost, 4.3.20, 3.16.0-30-lowlatency, x86_64: installed vboxhost, 4.3.20, 3.16.0-31-lowlatency, x86_64: installed EcryptfsInUse: Yes 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: Samsung Electronics Co Ltd Device [144d:c0d1] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0d1] InstallationDate: Installed on 2015-01-07 (51 days ago) InstallationMedia: Ubuntu-Studio 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2050): WARNING **: Failed to load user image: Falha ao abrir o arquivo "/home/helder/.face": Permissão negada LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2075): WARNING **: Failed to load user image: Falha ao abrir o arquivo "/home/helder/.face": Permissão negada MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-lowlatency root=UUID=23a23148-7fc8-4563-8828-52c528ad8bb7 ro locale=pt_BR resume=/dev/sda2 ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5 Tags: utopic ubuntu Uname: Linux 3.16.0-31-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02ABI.004.120907.dg dmi.board.asset.tag: No Asset Tag dmi.board.name: NP550P5C-AD1BR dmi.board.vendor: SAMSUNG EL
[Touch-packages] [Bug 1387423] Re: package x11-common 1:7.7+7ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for reporting this bug to Ubuntu. 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: 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/1387423 Title: package x11-common 1:7.7+7ubuntu2 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: during upgrade to 14.10 possibly a cascading error from another install-failure ProblemType: Package DistroRelease: Ubuntu 14.10 Package: x11-common 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.1: 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 Date: Tue Oct 28 14:22:47 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DuplicateSignature: package:x11-common:1:7.7+7ubuntu2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:094b] InstallationDate: Installed on 2013-10-05 (389 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: Dell Inc. Precision T3600 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=/dev/sda6 ro quiet splash zswap.enabled=1 vt.handoff=7 Renderer: Software SourcePackage: xorg Title: package x11-common 1:7.7+7ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/03/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. 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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Oct 29 11:59:39 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1387423/+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 1386694] Re: Shows user accounts logged in incorrectly
Thank you for reporting this bug to Ubuntu. 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: 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/1386694 Title: Shows user accounts logged in incorrectly Status in xorg package in Ubuntu: Won't Fix Bug description: Upgraded from 14.04 to 14.10. Now find that when I click on user name, in top menu bar, that user accounts I have logged out of are still showing as logged in - tick against the user name is still there. Would expect the "logged in" indicator to be blank (see screenshot attached). This function was working correctly under 14.04. This was an upgrade, not a fresh install. 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: [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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Tue Oct 28 13:23:59 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.13.0-37-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-23-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: ASUSTeK Computer Inc. Device [1043:108d] InstallationDate: Installed on 2013-06-11 (503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X202E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=2209198a-c3f3-4a71-bcba-4b183c76050d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X202E.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X202E 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.:bvrX202E.206:bd11/06/2012:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X202E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Oct 27 18:02:20 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12380 vendor AUO xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386694/+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 1385955] Re: Wrong zoom in/out behavior touchpad move
Thank you for reporting this bug to Ubuntu. 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: 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/1385955 Title: Wrong zoom in/out behavior touchpad move Status in One Hundred Papercuts: Confirmed Status in xorg package in Ubuntu: Won't Fix Bug description: Scenario: 1. Being in browser, I drag the touchpad using two fingers -> page scroll 2. While the page is scrolling (my fingers are not on touchpad anymore), I press CTRL key. 3. The page is zoomed in/out Same issue appears in Nautilus, for example. How can this be fixed? ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-lowlatency 3.16.4 Uname: Linux 3.16.0-23-lowlatency 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: Sun Oct 26 22:07:43 2014 DistUpgraded: 2014-10-22 09:50:07,290 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-23-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-23-lowlatency, x86_64: installed virtualbox-guest, 4.3.18, 3.16.0-23-generic, x86_64: installed virtualbox-guest, 4.3.18, 3.16.0-23-lowlatency, 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: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] MachineType: ASUSTeK COMPUTER INC. N550JV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-lowlatency root=UUID=cddf136b-f5a3-4a0b-ae61-84042b4d9fee ro acpi_osi_Linux quiet splash intel_pstate=enable vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-22 (4 days ago) dmi.bios.date: 09/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV 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.:bvrN550JV.207:bd09/17/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sun Oct 26 09:58:11 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1385955/+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 1277677] Re: Two icons on the launchbar replace each other
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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/1277677 Title: Two icons on the launchbar replace each other Status in xorg package in Ubuntu: Won't Fix Bug description: Hi, When I try to add both lazarus and idle3 icons to the launchbar, they replace each other. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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: Fri Feb 7 23:35:36 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8304] InstallationDate: Installed on 2014-02-06 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. EP43-UD3L MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8bf9c7e0-09a9-4580-be78-3540889612ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: EP43-UD3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP43-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP43-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP43-UD3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Feb 7 22:49:05 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB Optical MouseMOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1277677/+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 1386834] Re: Second display stops working on repeated detection
Thank you for reporting this bug to Ubuntu. 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/1386834 Title: Second display stops working on repeated detection Status in xorg package in Ubuntu: Won't Fix 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:
[Touch-packages] [Bug 1387134] Re: when enabled nvidia graphics card, desktop freezes
Thank you for reporting this bug to Ubuntu. 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: 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/1387134 Title: when enabled nvidia graphics card, desktop freezes Status in xorg package in Ubuntu: Won't Fix Bug description: Screen freezes occasionally while simply browsing the web, can be recovered by ctrl+alt+f1 and ctrl+alt+f7 This has been the case in 14.04, and it's still the case in 14.10 (64 bit) Asus UX32V 331.89-0ubuntu5 *** 331.89-0ubuntu5 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: .tmp.unity.support.test.1: 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: Wed Oct 29 12:40:01 2014 DistUpgraded: 2014-10-28 11:18:50,177 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed bbswitch, 0.7, 3.16.0-24-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1507] Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507] InstallationDate: Installed on 2014-05-31 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=690e7454-2b46-48e2-9b5e-57228f67864a ro quiet splash processor.ignore_ppc=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Oct 29 12:00:13 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Touch-packages] [Bug 1272913] Re: Brightness settings aren't retained on reboot
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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/1272913 Title: Brightness settings aren't retained on reboot Status in xorg package in Ubuntu: Won't Fix Bug description: the lightness of my screen is after a reboot on max level. Even if I defined e.a. 75% before. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.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 Date: Sun Jan 26 14:16:56 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:90b6] InstallationDate: Installed on 2013-10-20 (97 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Sony Corporation SVP1321C5E MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=8a2494e4-83e1-4a99-9b0d-61d525184510 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1021V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1021V7:bd08/08/2013:svnSonyCorporation:pnSVP1321C5E:pvrC60C41MT:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVP1321C5E dmi.product.version: C60C41MT dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Jan 26 11:09:37 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 38562 vendor MEI xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1272913/+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 1301722] Re: Mouse Scroll Wheel not working in spice vm guests
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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/1301722 Title: Mouse Scroll Wheel not working in spice vm guests Status in xorg package in Ubuntu: Won't Fix Bug description: I'm running Precise in various qemu-kvm virtual machines with Spice. The ScrollWheel stops working in the virtual machine as soon the spice-vdagent gets started. After killing the spice-vdagent process the Scroll Wheel works again. Seems to be an evdev Bug, see solved Fedora Bug: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=805902 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 2 22:55:21 2014 DistUpgraded: 2013-10-21 18:32:59,232 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Device [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2013-05-26 (311 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:25761): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory ** (lightdm-gtk-greeter:25761): WARNING **: Failed to load user image: Failed to open file '/home/harry/.face': No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=adda9701-5de5-45dd-9068-ce97f8259354 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-21 (163 days ago) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Mar 28 12:35:38 2014 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 inputspice vdagent tablet TOUCHSCREEN, id 9 xserver.errors: Failed to load module "evdec" (module does not exist, 0) Failed to load module "evdec" (module does not exist, 0) No input driver matching `evdec' xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 0 vendor QXL xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1301722/+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 1309153] Re: 10de:06fd [HP Z400 Workstation] NVRM: os_pci_init_handle: invalid context!
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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/1309153 Title: 10de:06fd [HP Z400 Workstation] NVRM: os_pci_init_handle: invalid context! Status in xorg package in Ubuntu: Won't Fix Bug description: My Xsessions are locking up at random times (sometimes mulitple times an hour, sometimes with days in between). During these lockups I have a variety of effects not always the same. These include: having the display freeze, but the mouse cursor still moves (but clicks do nothing) having the display completely freeze sometimes sound continues to play and sometimes it starts looping the last few seconds of sound sometimes I can use Ctrl-Alt-F1 to get a command lines, but not always most of the time I can ssh in from another machine, but not always If I can get a command line, sometimes it can recover by restarting lightdm, but not always I can sometimes recover by using Alt-SysRq k, but not always sometimes the computer need to be powered off to reboot There is pretty much always lines in the syslog with statements such as Apr 17 10:10:58 pegasus kernel: [74129.721505] NVRM: os_pci_init_handle: invalid context! Apr 17 10:11:49 pegasus kernel: [74178.673977] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context with the NVRM: os_pci_init_handle: invalid context! being the most commonly seen one the need to reboot tends to be with the NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context errors I will try to provide additional needed data as requested, but will need specific instructions since I'm very new to debugging (I have used linux for about 15 years without major issues until now). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic i686 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 Kernel Module 331.20 Wed Oct 30 16:59:55 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,gnomecompat,snap,vpswitch,place,compiztoolbox,grid,imgpng,animation,resize,workarounds,move,mousepoll,wall,session,expo,unitymtgrabhandles,fade,scale,ezoom,unityshell] CompositorRunning: None Date: Thu Apr 17 15:17:28 2014 DistUpgraded: 2014-03-25 08:13:52,816 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-331, 331.20, 3.11.0-18-generic, i686: installed nvidia-331, 331.20, 3.11.0-19-generic, i686: installed nvidia-331, 331.20, 3.2.0-60-generic-pae, i686: installed nvidia-331, 331.20, 3.5.0-47-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G98 [Quadro NVS 295] [10de:06fd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:062e] InstallationDate: Installed on 2010-06-23 (1394 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) JockeyStatus: kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_331 - nvidia_331 (Proprietary, Enabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: Hewlett-Packard HP Z400 Workstation MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-generic root=UUID=d0cdc763-d1e9-4d49-9c33-03cbb8bc5099 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2014-03-25 (23 days ago) dmi.bios.date: 08/19/2009 dmi.bios.vendo
[Touch-packages] [Bug 1314209] Re: 047f:c006 [Dell OptiPlex GX260] USB Headset buttons don't work
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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/1314209 Title: 047f:c006 [Dell OptiPlex GX260] USB Headset buttons don't work Status in xorg package in Ubuntu: Won't Fix Bug description: We have a number of different USB headsets in our call center and none of the buttons work on them. They have Mute, vol up, and vol down. On two different models the mute button will left click the mouse and I had to add them to the xorg.conf to ignore their HID input but the rest of the buttons do nothing. When we use a Windows XP PC those buttons will mute the microphone, turn up the volume slider, and turn down the volume slider using the built in driver. I am using xUbuntu 13.10 64bit as an LTSP client. --- .tmp.unity.support.test.1: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 BootLog: [H[JNegotiation: ..size = 611MB bs=1024, sz=641343488 bytes * Setting up X socket directories... [128G [122G[ OK ] saned disabled; edit /etc/default/saned CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDmesg: [ 18.973643] ip_tables: (C) 2000-2006 Netfilter Core Team [ 23.994494] nbd9: unknown partition table [ 24.003014] block nbd9: NBD_DISCONNECT [ 24.003748] block nbd9: Receive control failed (result -32) [ 24.003803] block nbd9: queue cleared DistUpgraded: Fresh install DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0126] MachineType: Dell Computer Corporation OptiPlex GX260 MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: ro initrd=initrd.img-3.11.0-20-generic init=/sbin/init-ltsp quiet splash plymouth:force-splash vt.handoff=7 root=/dev/nbd0 BOOT_IMAGE=vmlinuz-3.11.0-20-generic BOOTIF=01-00-0b-db-42-e0-4f ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu Uname: Linux 3.11.0-20-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/01/2004 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A09 dmi.board.name: 02X378 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA09:bd11/01/2004:svnDellComputerCorporation:pnOptiPlexGX260:pvr:rvnDellComputerCorp.:rn02X378:rvr:cvnDellComputerCorporation:ct15:cvr: dmi.product.name: OptiPlex GX260 dmi.sys.vendor: Dell Computer Corporation version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314209/+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 1245730] Re: just installed ubuntu and found this.
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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/1245730 Title: just installed ubuntu and found this. Status in cinnamon: New Status in xorg package in Ubuntu: Won't Fix Bug description: i just installed cinnamon in my fresh-install ubuntu 13.10. and when i check with xdiagnose i found this error. can anybody help? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Oct 29 09:43:33 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.16, 3.11.0-12-generic, i686: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1b62] InstallationDate: Installed on 2013-10-28 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MachineType: ASUSTeK Computer Inc. K42N MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=5be69170-46a2-49bf-9ba4-005613d55f53 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K42N.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K42N dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK42N.211:bd11/10/2010:svnASUSTeKComputerInc.:pnK42N:pvr1.0:rvnASUSTeKComputerInc.:rnK42N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K42N dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Oct 29 08:39:51 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1245730/+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 1272749] Re: $ /usr/lib/nux/unity_support_test -p
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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/1272749 Title: $ /usr/lib/nux/unity_support_test -p Status in xorg package in Ubuntu: Won't Fix Bug description: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits) OpenGL version string: 2.1 Mesa 10.1.0-devel (git-a487b4d saucy-oibaf-ppa+curaga) Not software rendered:no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: no In particular : Not software rendered: no (double negative) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 Uname: Linux 3.4.0 i686 .tmp.unity.support.test.1: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 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: Sat Jan 25 14:39:37 2014 DistUpgraded: 2014-01-23 12:42:33,334 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] MachineType: GOOGLE Parrot MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no username) XDG_RUNTIME_DIR= SHELL=/bin/sh ProcKernelCmdLine: cros_secure console=tty1 debug verbose root=/dev/sda7 rootwait rw lsm.module_locking=0 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2014-01-23 (2 days ago) dmi.bios.date: 09/10/2012 dmi.bios.vendor: coreboot dmi.bios.version: Google_Parrot.2685.37.0 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrGoogle_Parrot.2685.37.0:bd09/10/2012:svnGOOGLE:pnParrot:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Parrot dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52+git1401250630.cbb31f~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.1~git1401250730.a487b4+curaga~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1~git1401250730.a487b4+curaga~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3+git1401241930.8de6f7~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907+git1401241930.294180~gd~s version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Sat Jan 25 14:18:40 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2~saucy1 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1272749/+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 1244778] Re: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in xorg package in Ubuntu: Won't Fix Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-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 / 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 (217 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers 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.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not e
[Touch-packages] [Bug 1162408] Re: little horizontal black lines sporadically appear
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. 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/1162408 Title: little horizontal black lines sporadically appear Status in xorg package in Ubuntu: Won't Fix Bug description: Some little horizontal black lines sometimes appear on the Ubuntu desktop. They disappear quickly, and there seems no obvious way to force the event to occur predictably. The problem occurs with libgl1-mesa-dri-experimental but, unless I'm mistaken, occurred also with the nonexperimental branch. Furthermore, I'm running Ubuntu Classic and was not using 3d effects when the problem occurred (was simply typing text in LibreOffice). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.25-lowlatency 3.5.7.4 Uname: Linux 3.5.0-25-lowlatency i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sun Mar 31 06:55:41 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-25-lowlatency, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-26-generic, i686: installed virtualbox, 4.1.18, 3.5.0-25-lowlatency, i686: installed virtualbox, 4.1.18, 3.5.0-26-generic, i686: installed 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: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (9 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0JF77M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd12/10/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0JF77M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.libdrm2: libdrm2 2.4.43+git1303291653.ca678b~gd~q version.libgl1-mesa-dri: libgl1-mesa-dri 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-glx: libgl1-mesa-glx 9.2~git1303291656.5f41e0~gd~q version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0+git1303291654.6e74aa~gd~q version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5+git1303291654.431816~gd~q version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7+git1303271126.677142~gd~q --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2013-11-19 15:54:14,165 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 201
[Touch-packages] [Bug 1242761] Re: System menu doesn't respond
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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: Fix Committed => 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/1242761 Title: System menu doesn't respond Status in xorg package in Ubuntu: Won't Fix Bug description: Some elements of the system menu do not respond to clicks - Restart - Shutdown After a wakeup from suspend to RAM, the Restart entry disappears This is only obserable on Macbook Pro Retina 15" (NVidia card) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl 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 319.60 Wed Sep 25 14:28:26 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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 Date: Mon Oct 21 17:39:24 2013 DistUpgraded: 2013-10-20 12:21:36,841 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.8.0-32-generic, x86_64: installed nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed vboxhost, 4.3.0, 3.11.0-12-generic, x86_64: installed vboxhost, 4.3.0, 3.8.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00f2] InstallationDate: Installed on 2013-05-17 (156 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-20 (1 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46+git20130910.58d00888-0ubuntu0sarvatt~raring version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nou
[Touch-packages] [Bug 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)
Please install this dkms, reboot and redo the test. If the headset-mic still doesn't work, please enable dump_coeff and generate an alsa-info.txt. thanks. ** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+attachment/5266849/+files/oem-audio-hda-daily-dkms_0.1_all.deb -- 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/1821269 Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect) Status in alsa-driver package in Ubuntu: New Bug description: I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple type. not europe type.). When I plug 4 pole mic into jack, It doesn't detect. So I can't my voice through external mic. My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21)). Internal mic works well. Please check 4pole external mic detection. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: jimnong1441 F...m pulseaudio /dev/snd/pcmC0D0p: jimnong1441 F...m pulseaudio /dev/snd/controlC0: jimnong1441 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 11:30:39 2019 InstallationDate: Installed on 2017-07-27 (603 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: 내장 오디오 - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: No auto-switch between inputs Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Garp_BA dmi.board.vendor: Acer dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire ES1-131 dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+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 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
Indeed my conclusion was wrong because I mixed up the versions. The bug does affect some newer versions although it seems that it was solved in the meantime before reappearing again. To correct, I observed the following: * The bug does NOT affect kernel version 4.18.0-15 (Tested using a Live install of 18.04.2) * The bug does NOT affect kernel version 4.20.17-042017 (Tested on my install of 19.04 with a manually installed kernel) * The bug DOES affect kernel version 5.0.0-13 (Tested on my install of 19.04 with a manually installed kernel) * The bug DOES affect kernel version 5.0.0-15 (I used this version when I filed the bug report some days after I installed Ubuntu on my laptop) * The bug DOES affect kernel version 5.0.0-16 (Tested on my install of 19.04 with an update from disco-proposed using apt-get) * The bug does NOT affect kernel version 5.0.1-050001 (Tested on my install of 19.04 with a manually installed kernel) * The bug DOES affect newly build kernel version 5.1.5-050105 (Tested on my install of 19.04 with a manually installed kernel) I conclude, that the bug was introduced between 4.20.17 and 5.0.0-13, then solved between 5.0.0-16 and 5.0.1 only to be reintroduced in the most recent build (5.1.5). As you might notice, I am only a user, so I have limited skills. The change might also come from something else but I did not purposely change any setting or behavior while I tried the different versions. I tested the sound using the button in the sound-settings of Ubuntu and Spotify (both after a fresh boot and after suspend). -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829621/+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 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
Thanks. That is very helpful. ** Summary changed: - [HP Laptop 14-ma0xxx] No sound after suspend + [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1) ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1) Status in linux package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829621/+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 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => ajay rahul (ajayrahulapiswi) -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Zesty: Won't Fix Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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
