[Touch-packages] [Bug 1895299] Re: Wrong scaling factor after reboot
** Attachment added: "Screenshot after rescalling from 1.00 to 0.99 back to 1.00" https://bugs.launchpad.net/ubuntu/+bug/1895299/+attachment/5410122/+files/Screenshot%20after%20rescalling%201_00-0_99-1_00.png ** Package changed: ubuntu => xorg (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/1895299 Title: Wrong scaling factor after reboot Status in xorg package in Ubuntu: Confirmed Bug description: After reboot I can see wrong scaling factor for icons, etc., although after opening Gnome Tweaks -> Fonts, I can verify that the Scaling Factor is set to 1,00. Changing it (by '+' or '-') to 1,01 or 0,99 and back to 1,00 recovers proper scaling. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 15:34:09 2020 DistUpgraded: 2020-05-20 22:32:35,149 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-45-generic, x86_64: installed nvidia, 435.21, 5.4.0-47-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2020-04-02 (162 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 20QNS17N00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro psmouse.elantech_smbus=0 nouveau.modeset=0 quiet splash max_loop=64 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-20 (113 days ago) dmi.bios.date: 06/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNS17N00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:svnLENOVO:pn20QNS17N00:pvrThinkPadP53:rvnLENOVO:rn20QNS17N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNS17N00 dmi.product.sku: LENOVO_MT_20QN_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895299/+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 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Same with me, problem showed up after upgrading from 19.04 version. Uncommenting lines mentioned in #13 did not work for me (ASUS UX301L). Extremely annoying. -- 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/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+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 1815889]
(In reply to Michel Dänzer from comment #8) > Mesa doesn't really need explicit thread affinity at all. All it wants is > that certain sets of threads run on the same CPU module; it doesn't care > which particular CPU module that is. What's really needed is an API to > express this affinity between threads, instead of to specific CPU cores. I think the thread affinity API is a correct way to optimize for CPU cache topologies. pthread is a basic user API. Security policies shouldn't disallow pthread functions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Confirmed Status in QEMU: New Status in mesa package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Triaged Status in mesa source package in Disco: Fix Released Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1798861] Re: Tooltips flicker constantly in GTK3 applications
** Bug watch added: Debian Bug tracker #911148 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148 ** Also affects: hash-it via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1798861 Title: Tooltips flicker constantly in GTK3 applications Status in Hash-it: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Tooltips are flicker constantly (i.e. repeatedly shown and the hidden again) in GTK3 applications under XFCE. It is a regression in the recent GTK 3.24. This is the upstream report and fix: https://gitlab.gnome.org/GNOME/gtk/issues/1371 https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2 A workaround for XFCE is as follows: Open Settings Editor. Set xsettings -> Gtk -> CursorThemeSize to 16. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.24.1-1ubuntu2 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 12:23:53 2018 InstallationDate: Installed on 2017-02-01 (624 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hash-it/+bug/1798861/+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 1803316] Re: VPN connection is stopped
It works with 18.04 and does not work with 16.04 It connects with other gates of VPN provider but not with this one I have set. -- 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/1803316 Title: VPN connection is stopped Status in network-manager package in Ubuntu: Incomplete Bug description: From a few days I cannot connect via VPN, It worked from a few months *sudo apt policy network-manager* network-manager: Installed: 1.2.6-0ubuntu0.16.04.3 Candidate: 1.2.6-0ubuntu0.16.04.3 Versions: *** 1.2.6-0ubuntu0.16.04.3 500 500 http://ftp.agh.edu.pl/ubuntu xenial-updates/main amd64 Packages 500 http://ftp.agh.edu.pl/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ftp.agh.edu.pl/ubuntu xenial/main amd64 Packages */var/sys/log* Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8520] audit: op="connection-activate" uuid="3872fc1d-94ce-465e-8d52-7bbeb3eb72fe" name="HS VPN" pid=13561 uid=1000 result="success" Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8706] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Started the VPN service, PID 2396 Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8815] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Saw the service appear; activating connection Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.9989] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN connection: (ConnectInteractive) reply received Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: pppd started with pid 2405 Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0148] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: starting (3) Nov 14 10:46:08 hs pppd[2405]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing Nov 14 10:46:08 hs pppd[2405]: pppd 2.4.7 started by root, uid 0 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Nov 14 10:46:08 hs NetworkManager[1081]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0226] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/47) Nov 14 10:46:08 hs pptp[2411]: nm-pptp-service-2396 log[main:pptp.c:350]: The synchronous pptp option is NOT activated Nov 14 10:46:08 hs pppd[2405]: Using interface ppp0 Nov 14 10:46:08 hs NetworkManager[1081]: Using interface ppp0 Nov 14 10:46:08 hs pppd[2405]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0391] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0392] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Nov 14 10:46:39 hs pppd[2405]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect' Nov 14 10:46:39 hs NetworkManager[1081]: Connection terminated. Nov 14 10:46:39 hs pppd[2405]: Connection terminated. Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: Terminated ppp daemon with PID 2405. Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0566] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: failed: connect-failed (1) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0577] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopping (5) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0579] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopped (6) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0680] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state change reason: unknown (0) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0802] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN service disappeared Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin:
[Touch-packages] [Bug 1803316] Re: VPN connection is stopped
VPN provider wrote to me that everything is ok on their side. -- 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/1803316 Title: VPN connection is stopped Status in network-manager package in Ubuntu: Incomplete Bug description: From a few days I cannot connect via VPN, It worked from a few months *sudo apt policy network-manager* network-manager: Installed: 1.2.6-0ubuntu0.16.04.3 Candidate: 1.2.6-0ubuntu0.16.04.3 Versions: *** 1.2.6-0ubuntu0.16.04.3 500 500 http://ftp.agh.edu.pl/ubuntu xenial-updates/main amd64 Packages 500 http://ftp.agh.edu.pl/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ftp.agh.edu.pl/ubuntu xenial/main amd64 Packages */var/sys/log* Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8520] audit: op="connection-activate" uuid="3872fc1d-94ce-465e-8d52-7bbeb3eb72fe" name="HS VPN" pid=13561 uid=1000 result="success" Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8706] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Started the VPN service, PID 2396 Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8815] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Saw the service appear; activating connection Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.9989] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN connection: (ConnectInteractive) reply received Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: pppd started with pid 2405 Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0148] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: starting (3) Nov 14 10:46:08 hs pppd[2405]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing Nov 14 10:46:08 hs pppd[2405]: pppd 2.4.7 started by root, uid 0 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Nov 14 10:46:08 hs NetworkManager[1081]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0226] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/47) Nov 14 10:46:08 hs pptp[2411]: nm-pptp-service-2396 log[main:pptp.c:350]: The synchronous pptp option is NOT activated Nov 14 10:46:08 hs pppd[2405]: Using interface ppp0 Nov 14 10:46:08 hs NetworkManager[1081]: Using interface ppp0 Nov 14 10:46:08 hs pppd[2405]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0391] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0392] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Nov 14 10:46:39 hs pppd[2405]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect' Nov 14 10:46:39 hs NetworkManager[1081]: Connection terminated. Nov 14 10:46:39 hs pppd[2405]: Connection terminated. Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: Terminated ppp daemon with PID 2405. Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0566] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: failed: connect-failed (1) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0577] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopping (5) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0579] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopped (6) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0680] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state change reason: unknown (0) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0802] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN service disappeared Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 1 / phase 'dead' Nov 14 10:46:39 hs
[Touch-packages] [Bug 1803316] Re: VPN connection is stopped
Hi, I install each new update/upgrade. VPN works if my mate uses it using MacOS. VPN does not work with Ubuntu 18.04 and 16.04 (only this OS I use). I've checked it in two different networks. I used every possible setting using NetworkManager. I've checked each possible solutions using StackOverflow. I did not check VPN connection using other VPN. I wrote the question to VPN's provider if they can check it out this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1803316 Title: VPN connection is stopped Status in network-manager package in Ubuntu: Incomplete Bug description: From a few days I cannot connect via VPN, It worked from a few months *sudo apt policy network-manager* network-manager: Installed: 1.2.6-0ubuntu0.16.04.3 Candidate: 1.2.6-0ubuntu0.16.04.3 Versions: *** 1.2.6-0ubuntu0.16.04.3 500 500 http://ftp.agh.edu.pl/ubuntu xenial-updates/main amd64 Packages 500 http://ftp.agh.edu.pl/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ftp.agh.edu.pl/ubuntu xenial/main amd64 Packages */var/sys/log* Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8520] audit: op="connection-activate" uuid="3872fc1d-94ce-465e-8d52-7bbeb3eb72fe" name="HS VPN" pid=13561 uid=1000 result="success" Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8706] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Started the VPN service, PID 2396 Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8815] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Saw the service appear; activating connection Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.9989] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN connection: (ConnectInteractive) reply received Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: pppd started with pid 2405 Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0148] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: starting (3) Nov 14 10:46:08 hs pppd[2405]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing Nov 14 10:46:08 hs pppd[2405]: pppd 2.4.7 started by root, uid 0 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Nov 14 10:46:08 hs NetworkManager[1081]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0226] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/47) Nov 14 10:46:08 hs pptp[2411]: nm-pptp-service-2396 log[main:pptp.c:350]: The synchronous pptp option is NOT activated Nov 14 10:46:08 hs pppd[2405]: Using interface ppp0 Nov 14 10:46:08 hs NetworkManager[1081]: Using interface ppp0 Nov 14 10:46:08 hs pppd[2405]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0391] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0392] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Nov 14 10:46:39 hs pppd[2405]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect' Nov 14 10:46:39 hs NetworkManager[1081]: Connection terminated. Nov 14 10:46:39 hs pppd[2405]: Connection terminated. Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: Terminated ppp daemon with PID 2405. Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0566] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: failed: connect-failed (1) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0577] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopping (5) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0579] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopped (6) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0680]
[Touch-packages] [Bug 1803316] [NEW] VPN connection is stopped
Public bug reported: >From a few days I cannot connect via VPN, It worked from a few months *sudo apt policy network-manager* network-manager: Installed: 1.2.6-0ubuntu0.16.04.3 Candidate: 1.2.6-0ubuntu0.16.04.3 Versions: *** 1.2.6-0ubuntu0.16.04.3 500 500 http://ftp.agh.edu.pl/ubuntu xenial-updates/main amd64 Packages 500 http://ftp.agh.edu.pl/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ftp.agh.edu.pl/ubuntu xenial/main amd64 Packages */var/sys/log* Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8520] audit: op="connection-activate" uuid="3872fc1d-94ce-465e-8d52-7bbeb3eb72fe" name="HS VPN" pid=13561 uid=1000 result="success" Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8706] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Started the VPN service, PID 2396 Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.8815] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Saw the service appear; activating connection Nov 14 10:46:07 hs NetworkManager[1081]: [1542188767.9989] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN connection: (ConnectInteractive) reply received Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: pppd started with pid 2405 Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0148] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: starting (3) Nov 14 10:46:08 hs pppd[2405]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing Nov 14 10:46:08 hs pppd[2405]: pppd 2.4.7 started by root, uid 0 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Nov 14 10:46:08 hs NetworkManager[1081]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0226] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/47) Nov 14 10:46:08 hs pptp[2411]: nm-pptp-service-2396 log[main:pptp.c:350]: The synchronous pptp option is NOT activated Nov 14 10:46:08 hs pppd[2405]: Using interface ppp0 Nov 14 10:46:08 hs NetworkManager[1081]: Using interface ppp0 Nov 14 10:46:08 hs pppd[2405]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: Connect: ppp0 <--> /dev/pts/22 Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0391] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Nov 14 10:46:08 hs NetworkManager[1081]: [1542188768.0392] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Nov 14 10:46:39 hs pppd[2405]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: LCP: timeout sending Config-Requests Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect' Nov 14 10:46:39 hs NetworkManager[1081]: Connection terminated. Nov 14 10:46:39 hs pppd[2405]: Connection terminated. Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: Terminated ppp daemon with PID 2405. Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0566] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: failed: connect-failed (1) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0577] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopping (5) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0579] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state changed: stopped (6) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0680] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN plugin: state change reason: unknown (0) Nov 14 10:46:39 hs NetworkManager[1081]: [1542188799.0802] vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN service disappeared Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 1 / phase 'dead' Nov 14 10:46:39 hs NetworkManager[1081]: Terminating on signal 15 Nov 14 10:46:39 hs NetworkManager[1081]: Modem hangup Nov 14 10:46:39 hs pppd[2405]: Terminating on signal 15 Nov 14 10:46:39 hs pppd[2405]: Modem hangup Nov 14 10:46:39 hs pptp[2291]: nm-pptp-service-2215 log[pptp_read_some:pptp_ctrl.c:593]: read error: Bad file descriptor Nov 14 10:46:39 hs kernel: [ 5539.540135] pptpcm[2291]: segfault at 7f069f3a87b8 ip 00406a87 sp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
I'm on 18.04.01 LTS, and I have this issue. I was searching for this shortcut to be disabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+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 1432949]
You can try "git am -3 ...". If that doesn't help, then I don't know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1432949 Title: r300 Mesa driver not loading with KMS enabled Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: I cannot get 3D acceleration to work. I was expecting to see the gears via the command 'glxgears' I have KMS enable on my iBook G4 by using the following parameter Linux radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 Here are my Mesa and Xorg output rican-linux@ibookG4-UbuntuMATE:~$ cat /var/log/Xorg.0.log |grep -e radeon -e dri2 -e drm -e KMS [32.774] Kernel command line: root=UUID=fadadc01-6fd5-49fa-85f3-9e52d0fe6155 ro quiet splash video=offb:off video=1024x768-32 video=radeonfb:off radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 [33.203] (II) xfree86: Adding drm device (/dev/dri/card0) [35.011] (II) LoadModule: "radeon" [35.012] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [35.337] (II) Module radeon: vendor="X.Org Foundation" [35.604] (II) [KMS] Kernel modesetting enabled. [35.697] (II) Loading sub module "dri2" [35.697] (II) LoadModule: "dri2" [35.697] (II) Module "dri2" already built-in [35.870] (II) RADEON(0): KMS Color Tiling: enabled [35.870] (II) RADEON(0): KMS Color Tiling 2D: disabled [35.870] (II) RADEON(0): KMS Pageflipping: enabled rican-linux@ibookG4-UbuntuMATE:~$ LIBGL_DEBUG=verbose glxinfo |grep render libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 4: 1002:4e56, driver r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig rican-linux@ibookG4-UbuntuMATE:~$ dpkg -l libgl1-mesa-dri Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libgl1-mesa-dr 10.5.0~rc1-0 powerpc free implementation of the OpenGL rican-linux@ibookG4-UbuntuMATE:~$ rican-linux@ibookG4-UbuntuMATE:~$ lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 rican-linux@ibookG4-UbuntuMATE:~$ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 10.5.0~rc1-0ubuntu1 Candidate: 10.5.0-0ubuntu1 Version table: 10.5.0-0ubuntu1 0 500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main powerpc Packages *** 10.5.0~rc1-0ubuntu1 0 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-powerpc-smp 3.18.5 Uname: Linux 3.18.0-13-powerpc-smp ppc ApportVersion: 2.16.1-0ubuntu2 Architecture: powerpc CurrentDesktop: MATE Date: Tue Mar 17 00:58:43 2015 InstallationDate: Installed on 2015-03-17 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha powerpc (20150225) SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1432949/+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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04
Thanks Timo for explanation. I'm aware of all inconveniences related to running unstable system, looks that I have just hit one of those... I'll keep my eye on it. I'd keep the bug open till those dependencies are fixed, but it is up to you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752343 Title: Problem with DRI2 and GLX - bionic 18.04 Status in mesa package in Ubuntu: Invalid Bug description: I have encountered the problem described below, after some recent updates in my Kubuntu. After asking on "Answers" I was requested to open a bug, so I'm doing it. My problem was, that kwin stopped to show graphical effects. I'm using a laptop with Intel graphics - HD5500 After some log file search I've found, that probably the cause is shown in Xorg.0.log: Xorg.0.log:[ 7073.803] (II) AIGLX: Screen 0 is not DRI2 capable Xorg.0.log:[ 7073.803] (EE) AIGLX: reverting to software rendering After some googling, I have found article below, explaining possible root cause. I have used a solution proposed there, and after installing libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my problem disappeared. Link below describes details: https://bugs.freedesktop.org/show_bug.cgi?id=104928 Here is some output from my OS diag tools: lshw -C display *-display description: VGA compatible controller product: HD Graphics 5500 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:47 memory:c000-c0ff memory:b000-bfff ioport:4000(size=64) memory:c-d lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic uname -a Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux sudo dmidecode -t 1 # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: FUJITSU Product Name: LIFEBOOK A555 Version: Serial Number: YM3M035369 UUID: CF0F380B-2089-E511-8681-742B62ED267C Wake-up Type: Power Switch SKU Number: Family: LIFEBOOK-FTS Best Regards, Marek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752343/+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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04
Ekhm... why do you say "As that package is installed by default"? Maybe in experimental Debian, but not in Ubuntu. I had to find this solution, manually download two deb files and install them creating a mess in my package repository just to make my kubuntu working. Do you call that "solution"? Is anyone even trying to read that report with understanding or verifying what is in the repository?!? On 2018-03-01 15:29, dino99 wrote: > As you said, and freedesktop concluded: > > Installing libegl-mesa0 package from experimental repository fixes the > bug. > > As that package is installed by default, that report is now useless. > > > ** Changed in: mesa (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the > bug > report. > https://bugs.launchpad.net/bugs/1752343 > > Title: > Problem with DRI2 and GLX - bionic 18.04 > > Status in mesa package in Ubuntu: > Invalid > > Bug description: > I have encountered the problem described below, after some recent > updates in my Kubuntu. After asking on "Answers" I was requested to > open a bug, so I'm doing it. > > My problem was, that kwin stopped to show graphical effects. I'm > using a laptop with Intel graphics - HD5500 > After some log file search I've found, that probably the cause is > shown in Xorg.0.log: > > Xorg.0.log:[ 7073.803] (II) AIGLX: Screen 0 is not DRI2 capable > Xorg.0.log:[ 7073.803] (EE) AIGLX: reverting to software rendering > > > After some googling, I have found article below, explaining possible > root cause. I have used a solution proposed there, and after > installing libegl-mesa0_18.0.0~rc4-1_amd64.deb and > libgbm1_18.0.0~rc4-1_amd64.deb my problem disappeared. > > Link below describes details: > > https://bugs.freedesktop.org/show_bug.cgi?id=104928 > > Here is some output from my OS diag tools: > > lshw -C display > > *-display > description: VGA compatible controller > product: HD Graphics 5500 > vendor: Intel Corporation > physical id: 2 > bus info: pci@:00:02.0 > version: 09 > width: 64 bits > clock: 33MHz > capabilities: msi pm vga_controller bus_master cap_list rom > configuration: driver=i915 latency=0 > resources: irq:47 memory:c000-c0ff > memory:b000-bfff ioport:4000(size=64) memory:c-d > > lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu Bionic Beaver (development branch) > Release: 18.04 > Codename: bionic > > uname -a > Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 > UTC 2018 x86_64 x86_64 x86_64 GNU/Linux > > sudo dmidecode -t 1 > # dmidecode 3.1 > Getting SMBIOS data from sysfs. > SMBIOS 2.7 present. > > Handle 0x0001, DMI type 1, 27 bytes > System Information > Manufacturer: FUJITSU > Product Name: LIFEBOOK A555 > Version: > Serial Number: YM3M035369 > UUID: CF0F380B-2089-E511-8681-742B62ED267C > Wake-up Type: Power Switch > SKU Number: > Family: LIFEBOOK-FTS > > Best Regards, > > Marek > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752343/+subscriptions ** Bug watch added: freedesktop.org Bugzilla #104928 https://bugs.freedesktop.org/show_bug.cgi?id=104928 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752343 Title: Problem with DRI2 and GLX - bionic 18.04 Status in mesa package in Ubuntu: Invalid Bug description: I have encountered the problem described below, after some recent updates in my Kubuntu. After asking on "Answers" I was requested to open a bug, so I'm doing it. My problem was, that kwin stopped to show graphical effects. I'm using a laptop with Intel graphics - HD5500 After some log file search I've found, that probably the cause is shown in Xorg.0.log: Xorg.0.log:[ 7073.803] (II) AIGLX: Screen 0 is not DRI2 capable Xorg.0.log:[ 7073.803] (EE) AIGLX: reverting to software rendering After some googling, I have found article below, explaining possible root cause. I have used a solution proposed there, and after installing libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my problem disappeared. Link below describes details: https://bugs.freedesktop.org/show_bug.cgi?id=104928 Here is some output from my OS d
[Touch-packages] [Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04
I hope after 10 years with kubuntu I'm not trying to mix anything... This is my sources list: deb http://archive.ubuntu.com/ubuntu/ bionic main restricted deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted deb http://archive.ubuntu.com/ubuntu/ bionic universe deb http://archive.ubuntu.com/ubuntu/ bionic-updates universe deb http://archive.ubuntu.com/ubuntu/ bionic multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse deb http://archive.canonical.com/ubuntu bionic partner deb http://security.ubuntu.com/ubuntu bionic-security main restricted deb http://security.ubuntu.com/ubuntu bionic-security universe deb http://security.ubuntu.com/ubuntu bionic-security multiverse What I did was just a regular apt update && apt upgrade. At some point I have lost my graphical effects in KDE I suppose you are still supporting apt upgrade, aren't you? :-D So to summarize - there is a bug in package which is currently in Ubuntu repository. With following packages: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-=-= ii libegl1:amd640.2.999+git20 amd64 Vendor neutral GL dispatch library -- ii libegl1-mesa:amd 17.3.3-0ubunt amd64 free implementation of the EGL API -- ii libegl1-mesa-dev 17.3.3-0ubunt amd64 free implementation of the EGL API -- un libegl1-x11 (no description available) My kubuntu is not using hardware accelerated graphics. In /var/log/Xorg.0.log file, I can see this: [ 17324.106] (II) AIGLX: Screen 0 is not DRI2 capable [ 17324.106] (EE) AIGLX: reverting to software rendering Using those, I have just googled for some solution and found that when I install those two .deb files: libegl-mesa0_18.0.0~rc4-1_amd64.deb libgbm1_18.0.0~rc4-1_amd64.deb Everything goes back to normal. So something is wrong, but I can't go behind that point to say what exactly. ** Changed in: mesa (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752343 Title: Problem with DRI2 and GLX - bionic 18.04 Status in mesa package in Ubuntu: New Bug description: I have encountered the problem described below, after some recent updates in my Kubuntu. After asking on "Answers" I was requested to open a bug, so I'm doing it. My problem was, that kwin stopped to show graphical effects. I'm using a laptop with Intel graphics - HD5500 After some log file search I've found, that probably the cause is shown in Xorg.0.log: Xorg.0.log:[ 7073.803] (II) AIGLX: Screen 0 is not DRI2 capable Xorg.0.log:[ 7073.803] (EE) AIGLX: reverting to software rendering After some googling, I have found article below, explaining possible root cause. I have used a solution proposed there, and after installing libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my problem disappeared. Link below describes details: https://bugs.freedesktop.org/show_bug.cgi?id=104928 Here is some output from my OS diag tools: lshw -C display *-display description: VGA compatible controller product: HD Graphics 5500 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:47 memory:c000-c0ff memory:b000-bfff ioport:4000(size=64) memory:c-d lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic uname -a Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux sudo dmidecode -t 1 # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: FUJITSU Product Name: LIFEBOOK A555 Version: Serial Number: YM3M035369 UUID: CF0F380B-2089-E511-8681-742B62ED267C Wake-up Type: Power Switch SKU Number: Family: LIFEBOOK-FTS Best Regards, Marek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.ne
[Touch-packages] [Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04
One more - please contact me before setting this again to invalid. English is not my native, so I'd like to be sure, that misunderstanding is not the cause for invalidating the report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752343 Title: Problem with DRI2 and GLX - bionic 18.04 Status in mesa package in Ubuntu: New Bug description: I have encountered the problem described below, after some recent updates in my Kubuntu. After asking on "Answers" I was requested to open a bug, so I'm doing it. My problem was, that kwin stopped to show graphical effects. I'm using a laptop with Intel graphics - HD5500 After some log file search I've found, that probably the cause is shown in Xorg.0.log: Xorg.0.log:[ 7073.803] (II) AIGLX: Screen 0 is not DRI2 capable Xorg.0.log:[ 7073.803] (EE) AIGLX: reverting to software rendering After some googling, I have found article below, explaining possible root cause. I have used a solution proposed there, and after installing libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my problem disappeared. Link below describes details: https://bugs.freedesktop.org/show_bug.cgi?id=104928 Here is some output from my OS diag tools: lshw -C display *-display description: VGA compatible controller product: HD Graphics 5500 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:47 memory:c000-c0ff memory:b000-bfff ioport:4000(size=64) memory:c-d lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic uname -a Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux sudo dmidecode -t 1 # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: FUJITSU Product Name: LIFEBOOK A555 Version: Serial Number: YM3M035369 UUID: CF0F380B-2089-E511-8681-742B62ED267C Wake-up Type: Power Switch SKU Number: Family: LIFEBOOK-FTS Best Regards, Marek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752343/+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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04
** Package changed: ubuntu => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752343 Title: Problem with DRI2 and GLX - bionic 18.04 Status in mesa package in Ubuntu: New Bug description: I have encountered the problem described below, after some recent updates in my Kubuntu. After asking on "Answers" I was requested to open a bug, so I'm doing it. My problem was, that kwin stopped to show graphical effects. I'm using a laptop with Intel graphics - HD5500 After some log file search I've found, that probably the cause is shown in Xorg.0.log: Xorg.0.log:[ 7073.803] (II) AIGLX: Screen 0 is not DRI2 capable Xorg.0.log:[ 7073.803] (EE) AIGLX: reverting to software rendering After some googling, I have found article below, explaining possible root cause. I have used a solution proposed there, and after installing libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my problem disappeared. Link below describes details: https://bugs.freedesktop.org/show_bug.cgi?id=104928 Here is some output from my OS diag tools: lshw -C display *-display description: VGA compatible controller product: HD Graphics 5500 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:47 memory:c000-c0ff memory:b000-bfff ioport:4000(size=64) memory:c-d lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic uname -a Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux sudo dmidecode -t 1 # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: FUJITSU Product Name: LIFEBOOK A555 Version: Serial Number: YM3M035369 UUID: CF0F380B-2089-E511-8681-742B62ED267C Wake-up Type: Power Switch SKU Number: Family: LIFEBOOK-FTS Best Regards, Marek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752343/+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 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
I would just like to inform you that this bug appear since last CentOS 7.4 update, 7.3 was ok. https://bugs.centos.org/view.php?id=13916 Maybe it should be reported to Systemd Issues ? ** Bug watch added: bugs.centos.org/ #13916 https://bugs.centos.org/view.php?id=13916 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without any keyboard. [EDIT]But I can still switch back to tty1.[/EDIT] I have also tried with much lower values for vm.dirty_background_ratio and vm.dirty_ratio, but to no avail. Linux
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
had somebody tryed sound with kernel 4.12 ?? -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1614943] Re: No ringtone on incoming calls
I believe this is the common problem with bug: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1612367 But I agree marking bug as critical is more appropriate. Maybe it would be better to merge and raise the importance of the original bug to Critical? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1614943 Title: No ringtone on incoming calls Status in Canonical System Image: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: current build number: 405 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en Regularly on incoming calls, there is no ringtone or just a click. Apart from that, the notification is displayed, I can answer the call normally. Phone is not muted, sound is close to the max, and if I reboot it works again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614943/+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 1442105] Re: GPS not working on my BQ Ubuntu Touch
I also have the GPS not working problem. My phone is bq Aquaris E5, I have OTA 13 installed. I don't even have the "Using GPS, anonymized Wi- Fi and cellular network info" option present in my settings menu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1442105 Title: GPS not working on my BQ Ubuntu Touch Status in Canonical System Image: Incomplete Status in location-service package in Ubuntu: Confirmed Bug description: Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch from BQ (I am on update 20), but the app dont detect my location. I have to mention that I check Here terms & Condition and GPS and location are checked. I attached some screenshot from what I did. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442105/+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 1643843] Re: Distorted colours after suspend / resume cycle
I can't bisect the problem, because for the two kernels I build, suspend was broken and the PC didn't wake up from 2nd suspend :-( I also tried 4.9-rc6 (albeit on an Arch Linux), which shows the same bug. ** Package changed: xorg (Ubuntu) => linux-lts-xenial (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/1643843 Title: Distorted colours after suspend / resume cycle Status in X.Org X server: Unknown Status in linux-lts-xenial package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1643843/+subscriptions --
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
So I applied this "big hammer" solution of the patch to the Trusty (14.04) Xenial HWE kernel (4.4.0-47.68~14.04.1) and this fixes the bug. I'll give it some more testing, while bisecting v4.0 to v4.1. ** Bug watch added: freedesktop.org Bugzilla #98832 https://bugs.freedesktop.org/show_bug.cgi?id=98832 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=98832 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle Status in X.Org X server: Unknown Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version:
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
$ git bisect log # bad: [89e419960fb6a260f6a112821507d516117d5aa1] Linux 4.1.4 # good: [c8bde72f9af412de57f0ceae218d648640118b0b] Linux 4.1.3 git bisect start 'v4.1.4' 'v4.1.3' # good: [e0cf83cc3de0341d8cabbb23097ad85f5ce97a11] drm/qxl: Do not leak memory if qxl_release_list_add fails git bisect good e0cf83cc3de0341d8cabbb23097ad85f5ce97a11 # bad: [9d680e03989324f000596be4862728a7c30f22c1] selinux: don't waste ebitmap space when importing NetLabel categories git bisect bad 9d680e03989324f000596be4862728a7c30f22c1 # bad: [510c99974fdbc18f143c41cbd461c522f5ad7164] tpm, tpm_crb: fix le64_to_cpu conversions in crb_acpi_add() git bisect bad 510c99974fdbc18f143c41cbd461c522f5ad7164 # bad: [8b941a43ea7709111d3cbea2bdfcc678975255da] drm/radeon: only check the sink type on DP connectors git bisect bad 8b941a43ea7709111d3cbea2bdfcc678975255da # good: [0f2bb042f21bdb28f20efcf1ff1c507e2f8b3caa] drm/i915: Declare the swizzling unknown for L-shaped configurations git bisect good 0f2bb042f21bdb28f20efcf1ff1c507e2f8b3caa # good: [1f977d7e942519127aea0a08e9d08437b363cf19] drm/i915: Use two 32bit reads for select 64bit REG_READ ioctls git bisect good 1f977d7e942519127aea0a08e9d08437b363cf19 # good: [7b49262b642511a16699cc63cf2a716739f0c43f] drm/radeon: SDMA fix hibernation (CI GPU family). git bisect good 7b49262b642511a16699cc63cf2a716739f0c43f # bad: [d1a4362d41e4feb52df6464f70fb64f21b894623] Revert "drm/radeon: dont switch vt on suspend" git bisect bad d1a4362d41e4feb52df6464f70fb64f21b894623 # first bad commit: [d1a4362d41e4feb52df6464f70fb64f21b894623] Revert "drm/radeon: dont switch vt on suspend" Just remember that good and bad is inverted, as I was looking for the commit which fixes my colour problem in v4.1.4. For me it fixes more then just the cursor. -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
Hmm - so I'm not sure what's going on here. I started bisecting v4.1 .. v4.2.8 and I couldn't find a working version in 6-7 bisects and when I checked rest of the commit set in the bisect, it couldn't find any commits to drivers/gpu?! So I decided to test Ubuntu mainline kernels a little bit more and the current status is: Broken: linux-image-4.1.3-040103-generic_4.1.3-040103.201507220129_amd64.deb Working: linux-image-4.1.4-040104-generic_4.1.4-040104.201508031330_amd64.deb So probably something was fixed and in a short time broken again during the v4.2 development cycle?! And probably I should check with other connectors too, as I currently run the monitor via DVI => VGA connector. -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
So I downloaded some kernels from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D Working: linux-image-4.1.35-040135-generic_4.1.35-040135.201610241431_amd64.deb Broken: linux-image-4.2.7-040207-generic_4.2.7-040207.201512091533_amd64.deb -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
While keeping the Xenial HWE stack on Ubuntu Trusty (14.04), I tried various installed HWE kernels. It seems it really broke with the Wily kernel (4.2.0.42.34). The Vivid kernel (3.19.0.74.56) has survived multiple resume cycles, while Wily instantly created the problem. -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
Now I tried all the Trusty HWEs and it seems to have started with Wily. xserver-xorg-video-radeon-lts-wily 1:7.5.0+git20150819-0ubuntu1~trusty1 linux-image-generic-lts-wily 4.2.0.42.34 xserver-xorg-core-lts-wily 2:1.17.2-1ubuntu9.1~trusty1 mesa-lts-wily 11.0.2-1ubuntu4~trusty1 I had once wrong colors with the Trusty initial stack (3.13), which I couldn't reproduce. And I was just told that disabling DPMS / monitor power management in KDE also prevents the problem, which might correlate with the fact, that running a DPMS "force off" / "force on" cycle also restores the colors correctly. -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
I couldn't reproduce the problem with Trusty (14.04) using its original HWE stack (AKA Kernel 3.13). -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+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 1643843] Re: Distorted colours after suspend / resume cycle
This is just a display problem - a snapshot is correct, so it really looks like a radeon driver problem, instead of an xorg problem. The wrong colors are always different, so every cycle produces a different result. For a photo as background it almost looks like modern art ;-) -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
** Attachment added: "Correct Unity desktop" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+attachment/4781463/+files/photo_desktop_ok.jpg -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1643843] [NEW] Distorted colours after suspend / resume cycle
Public bug reported: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu yakkety ** Attachment added: "Broken Unity desktop after resume from suspend" https://bugs.launchpad.net/bugs/1643843/+attachment/4781443/+files/photo_desktop_broken.jpg -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep
[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
Not sure whether it is same bug, but today there was no ringing on incoming call. Just only seen incoming call on a display. BQ E4.5 with OTA13. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtmultimedia-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Fix Released Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in qtmultimedia-opensource-src package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1625201] [NEW] "lvconvert --repair" destroys thin pool LV
Public bug reported: Hi If pool meta is 16GB , lvconvert --repair will destroy logical volumes. After rapair logical volumes inside the pool can not be activated again. Steps to reproduce: truncate --size 100GiB /tmp/test losetup /dev/loop1 /tmp/test pvcreate /dev/loop1 vgcreate vg02 /dev/loop1 lvcreate -n pool0meta -L 16G vg02 lvcreate -n pool0 -L 16GiB vg02 lvcreate -n data -V 1GiB --thinpool vg02/pool0 vgchange -a n vg02 lvconvert --repair vg02/pool0 # vgchange -a y vg02 device-mapper: resume ioctl on (252:3) failed: Invalid argument Unable to resume vg02-pool0-tpool (252:3) device-mapper: resume ioctl on (252:3) failed: Invalid argument Unable to resume vg02-pool0-tpool (252:3) 1 logical volume(s) in volume group "vg02" now active Syslog : [6039585.407800] device-mapper: thin: 252:2: metadata device (4145152 blocks) too small: expected 4161600 [6039585.407859] device-mapper: table: 252:2: thin-pool: preresume failed, error = -22 [6039586.535215] device-mapper: thin: 252:2: metadata device (4145152 blocks) too small: expected 4161600 [6039586.535258] device-mapper: table: 252:2: thin-pool: preresume failed, error = -22 [6039613.657170] device-mapper: thin: 252:3: metadata device (4145152 blocks) too small: expected 4161600 [6039613.657212] device-mapper: table: 252:3: thin-pool: preresume failed, error = -22 [6039614.716005] device-mapper: thin: 252:3: metadata device (4145152 blocks) too small: expected 4161600 [6039614.716047] device-mapper: table: 252:3: thin-pool: preresume failed, error = -22 Workaround for this is to shirk pool meta ( only when it is possible: You have free space in VG, and when meta will fit ) : thin_dump /dev/mapper/vg02-pool0_tmeta > lvm_meta_dum lvcreate -n pool0meta2 -L 12G vg02 thin_restore -i lvm_meta_dump -o /dev/mapper/vg02-pool0meta2 lvconvert --thinpool vg02/pool0 --poolmetadata vg02/pool0meta2 -- Kind Regards Marek Grzybowski ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Sep 19 13:29:54 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 LC_MESSAGES=POSIX SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1625201 Title: "lvconvert --repair" destroys thin pool LV Status in lvm2 package in Ubuntu: New Bug description: Hi If pool meta is 16GB , lvconvert --repair will destroy logical volumes. After rapair logical volumes inside the pool can not be activated again. Steps to reproduce: truncate --size 100GiB /tmp/test losetup /dev/loop1 /tmp/test pvcreate /dev/loop1 vgcreate vg02 /dev/loop1 lvcreate -n pool0meta -L 16G vg02 lvcreate -n pool0 -L 16GiB vg02 lvcreate -n data -V 1GiB --thinpool vg02/pool0 vgchange -a n vg02 lvconvert --repair vg02/pool0 # vgchange -a y vg02 device-mapper: resume ioctl on (252:3) failed: Invalid argument Unable to resume vg02-pool0-tpool (252:3) device-mapper: resume ioctl on (252:3) failed: Invalid argument Unable to resume vg02-pool0-tpool (252:3) 1 logical volume(s) in volume group "vg02" now active Syslog : [6039585.407800] device-mapper: thin: 252:2: metadata device (4145152 blocks) too small: expected 4161600 [6039585.407859] device-mapper: table: 252:2: thin-pool: preresume failed, error = -22 [6039586.535215] device-mapper: thin: 252:2: metadata device (4145152 blocks) too small: expected 4161600 [6039586.535258] device-mapper: table: 252:2: thin-pool: preresume failed, error = -22 [6039613.657170] device-mapper: thin: 252:3: metadata device (4145152 blocks) too small: expected 4161600 [6039613.657212] device-mapper: table: 252:3: thin-pool: preresume failed, error = -22 [6039614.716005] device-mapper: thin: 252:3: metadata device (4145152 blocks) too small: expected 4161600 [6039614.716047] device-mapper: table: 252:3: thin-pool: preresume failed, error = -22 Workaround for this is to shirk pool meta ( only when it is possible: You have free space in VG, and when meta will fit ) : thin_dump /dev/mapper/vg02-pool0_tmeta > lvm_meta_dum lvcreate -n pool0meta2 -L 12G vg02 thin_restore -i lvm_meta_dump -o /dev/mapper/vg02-pool0meta2 lvconvert --thinpool vg02/pool0 --poolmetadata vg02/pool0meta2 -- Kind Regards Marek Grzybowski ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-ge
[Touch-packages] [Bug 1619481] [NEW] package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka
Public bug reported: I do not know more. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libnl-3-200 (not installed) ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Sep 1 22:31:44 2016 DuplicateSignature: package:libnl-3-200:(not installed):pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 ErrorMessage: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 InstallationDate: Installed on 2016-04-16 (137 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: libnl3 Title: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package rosa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1619481 Title: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 Status in libnl3 package in Ubuntu: New Bug description: I do not know more. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libnl-3-200 (not installed) ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Sep 1 22:31:44 2016 DuplicateSignature: package:libnl-3-200:(not installed):pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 ErrorMessage: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 InstallationDate: Installed on 2016-04-16 (137 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: libnl3 Title: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka libnl-3-200:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1619481/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
I might be doing something broken, but it still seems broken to me on
Ubuntu 16.04 on Raspberry PI despite having these fixes applied.
Package versions:
systemd: 229-4ubuntu7
udev: 229-4ubuntu7
Could you please take a look if I'm not doing something stupid (I
hopefully attached the relevant info):
$ ifconfig -a | head
enxb827eb739cc2 Link encap:Ethernet HWaddr b8:27:eb:73:9c:c2
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
$ ls -l /etc/udev/rules.d/80-net-setup-link.rules | tee -a report.txt
lrwxrwxrwx 1 root root 9 Aug 4 2016 /etc/udev/rules.d/80-net-setup-link.rules
-> /dev/null
$ grep net.ifnames=0 /proc/cmdline | tee -a report.txt
8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa02082 bcm2709.serial=0xb2739cc2
smsc95xx.macaddr=B8:27:EB:73:9C:C2 bcm2708_fb.fbswap=1
bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0
vc_mem.mem_size=0x3f00 fsck.mode=force net.ifnames=0 dwc_otg.lpm_enable=0
console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4
elevator=deadline rootwait
$ cat /lib/udev/rules.d/73-usb-net-by-mac.rules
# Use MAC based names for network interfaces which are directly or indirectly
# on USB and have an universally administered (stable) MAC address (second bit
# is 0).
IMPORT{cmdline}="net.ifnames", ENV{net.ifnames}=="0", GOTO="usb_net_by_mac_end"
PROGRAM="/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules",
RESULT=="/dev/null", GOTO="usb_net_by_mac_end"
ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="", \
ATTR{address}=="?[014589cd]:*", \
IMPORT{builtin}="net_id", NAME="$env{ID_NET_NAME_MAC}"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1593379
Title:
systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
/etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
In Progress
Status in systemd package in Debian:
Fix Released
Bug description:
Description:Ubuntu 16.04 LTS
Release:16.04
The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
devices.
It appears the regression is here:
* Set MAC based name for USB network interfaces only for universally
administered (i. e. stable) MACs, not for locally administered (i. e.
randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
(as link files don't currently support globs for MACAddress=) and replace
with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
(Closes: #812575, LP: #1574483)
As Raspberry Pi's use eth0 via USB, this breaks running systems.
Before:
ii systemd229-4ubuntu4 armhfsystem and service manager
ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem
3: eth0: mtu 1500 qdisc pfifo_fast state UP
mode DEFAULT group default qlen 1000
link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff
After:
ii systemd 229-4ubuntu6armhf
system and service manager
ii udev 229-4ubuntu6armhf
/dev/ and hotplug management daemon
3: enxb827eb1639e9: mtu 1500 qdisc
pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff
cat /proc/cmdline
dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2
rootfstype=ext4 elevator=deadline rootwait
With the default interfaces configuration, all networking is lost on
reboot after upgrade.
SRU TEST CASE
=
* Boot with "net.ifnames=0" on the kernel command line, and connect an USB
ethernet device. It will still be called enxDEADBEEF with current xenial. With
the -proposed version it will instead keep the kernel name, like "usb0" as
intended.
* Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
(the other documented way to disable ifnames) and do the above
connect/name check test again.
To manage notifications about this bug go
[Touch-packages] [Bug 1591174] Re: No sound notification after receiving a new message
I never used headphones, music applications nor bluetooth and I experience it also. It should not be related to the above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1591174 Title: No sound notification after receiving a new message Status in messaging-app package in Ubuntu: Confirmed Bug description: Unfortunately I can't give you any clues bit it happens in my bq4.5 for the second time. I sit next to my phone in silence und suddendly see that the green notification LED is blinking. I take the phone into my hand and see in a notification area a new sms message that came a few second ago without letting me know with a tone. I put the phone down and send another sms from another device. Again no sound notification after message arrival. This situation happens to me already for the second time. The first time rebboting helped. For the second time rebooted helped as well. What I was doing before was using uRadio but after rebbot i turned the radio on and off and everything worked fine. I was also using Music app with earphones. If it happens to me again I provide more information what could be the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1591174/+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 1432949]
Fixed by 172bfdaa9e80342ade3f023f72d455d76713b866. Closing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1432949 Title: r300 Mesa driver not loading with KMS enabled Status in Mesa: Fix Released Status in mesa package in Ubuntu: Confirmed Bug description: I cannot get 3D acceleration to work. I was expecting to see the gears via the command 'glxgears' I have KMS enable on my iBook G4 by using the following parameter Linux radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 Here are my Mesa and Xorg output rican-linux@ibookG4-UbuntuMATE:~$ cat /var/log/Xorg.0.log |grep -e radeon -e dri2 -e drm -e KMS [32.774] Kernel command line: root=UUID=fadadc01-6fd5-49fa-85f3-9e52d0fe6155 ro quiet splash video=offb:off video=1024x768-32 video=radeonfb:off radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 [33.203] (II) xfree86: Adding drm device (/dev/dri/card0) [35.011] (II) LoadModule: "radeon" [35.012] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [35.337] (II) Module radeon: vendor="X.Org Foundation" [35.604] (II) [KMS] Kernel modesetting enabled. [35.697] (II) Loading sub module "dri2" [35.697] (II) LoadModule: "dri2" [35.697] (II) Module "dri2" already built-in [35.870] (II) RADEON(0): KMS Color Tiling: enabled [35.870] (II) RADEON(0): KMS Color Tiling 2D: disabled [35.870] (II) RADEON(0): KMS Pageflipping: enabled rican-linux@ibookG4-UbuntuMATE:~$ LIBGL_DEBUG=verbose glxinfo |grep render libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 4: 1002:4e56, driver r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig rican-linux@ibookG4-UbuntuMATE:~$ dpkg -l libgl1-mesa-dri Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libgl1-mesa-dr 10.5.0~rc1-0 powerpc free implementation of the OpenGL rican-linux@ibookG4-UbuntuMATE:~$ rican-linux@ibookG4-UbuntuMATE:~$ lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 rican-linux@ibookG4-UbuntuMATE:~$ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 10.5.0~rc1-0ubuntu1 Candidate: 10.5.0-0ubuntu1 Version table: 10.5.0-0ubuntu1 0 500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main powerpc Packages *** 10.5.0~rc1-0ubuntu1 0 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-powerpc-smp 3.18.5 Uname: Linux 3.18.0-13-powerpc-smp ppc ApportVersion: 2.16.1-0ubuntu2 Architecture: powerpc CurrentDesktop: MATE Date: Tue Mar 17 00:58:43 2015 InstallationDate: Installed on 2015-03-17 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha powerpc (20150225) SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1432949/+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 1432949]
(In reply to Michel Dänzer from comment #29) > That piglit sanity is failing with the patch may confirm my suspicion that > something doesn't add up yet I'm afraid: Since the kernel driver and > xf86-video-ati EXA code are using the same hardware formats for > display/rendering with BE & LE, I was wondering how the patch could result > in both display and glReadPixels working correctly for winsys buffers. Looks > like indeed only display works correctly, which indicates that the GPU is > effectively writing/reading PIPE_FORMAT_x8R8G8B8_* pixels like > PIPE_FORMAT_B8G8R8x8_* (which is what the kernel driver and EXA code are > using). The patch is correct from the LE perspective. It simply adds ARGB support and was tested thoroughly on LE. The side effect is that BE can use the format now too, but there may be other issues with BE. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1432949 Title: r300 Mesa driver not loading with KMS enabled Status in Mesa: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I cannot get 3D acceleration to work. I was expecting to see the gears via the command 'glxgears' I have KMS enable on my iBook G4 by using the following parameter Linux radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 Here are my Mesa and Xorg output rican-linux@ibookG4-UbuntuMATE:~$ cat /var/log/Xorg.0.log |grep -e radeon -e dri2 -e drm -e KMS [32.774] Kernel command line: root=UUID=fadadc01-6fd5-49fa-85f3-9e52d0fe6155 ro quiet splash video=offb:off video=1024x768-32 video=radeonfb:off radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 [33.203] (II) xfree86: Adding drm device (/dev/dri/card0) [35.011] (II) LoadModule: "radeon" [35.012] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [35.337] (II) Module radeon: vendor="X.Org Foundation" [35.604] (II) [KMS] Kernel modesetting enabled. [35.697] (II) Loading sub module "dri2" [35.697] (II) LoadModule: "dri2" [35.697] (II) Module "dri2" already built-in [35.870] (II) RADEON(0): KMS Color Tiling: enabled [35.870] (II) RADEON(0): KMS Color Tiling 2D: disabled [35.870] (II) RADEON(0): KMS Pageflipping: enabled rican-linux@ibookG4-UbuntuMATE:~$ LIBGL_DEBUG=verbose glxinfo |grep render libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 4: 1002:4e56, driver r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig rican-linux@ibookG4-UbuntuMATE:~$ dpkg -l libgl1-mesa-dri Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libgl1-mesa-dr 10.5.0~rc1-0 powerpc free implementation of the OpenGL rican-linux@ibookG4-UbuntuMATE:~$ rican-linux@ibookG4-UbuntuMATE:~$ lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 rican-linux@ibookG4-UbuntuMATE:~$ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 10.5.0~rc1-0ubuntu1 Candidate: 10.5.0-0ubuntu1 Version table: 10.5.0-0ubuntu1 0 500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main powerpc Packages *** 10.5.0~rc1-0ubuntu1 0 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-powerpc-smp 3.18.5 Uname: Linux 3.18.0-13-powerpc-smp ppc ApportVersion: 2.16.1-0ubuntu2 Architecture: powerpc CurrentDesktop: MATE Date: Tue Mar 17 00:58:43 2015 InstallationDate: Installed on 2015-03-17 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha powerpc (20150225) SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1432949/+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 1432949]
At this stage I just need a confirmation that more than 60% of apps work and show correct colors (mainly games). I don't expect all apps to be perfect right now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1432949 Title: r300 Mesa driver not loading with KMS enabled Status in Mesa: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I cannot get 3D acceleration to work. I was expecting to see the gears via the command 'glxgears' I have KMS enable on my iBook G4 by using the following parameter Linux radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 Here are my Mesa and Xorg output rican-linux@ibookG4-UbuntuMATE:~$ cat /var/log/Xorg.0.log |grep -e radeon -e dri2 -e drm -e KMS [32.774] Kernel command line: root=UUID=fadadc01-6fd5-49fa-85f3-9e52d0fe6155 ro quiet splash video=offb:off video=1024x768-32 video=radeonfb:off radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 [33.203] (II) xfree86: Adding drm device (/dev/dri/card0) [35.011] (II) LoadModule: "radeon" [35.012] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [35.337] (II) Module radeon: vendor="X.Org Foundation" [35.604] (II) [KMS] Kernel modesetting enabled. [35.697] (II) Loading sub module "dri2" [35.697] (II) LoadModule: "dri2" [35.697] (II) Module "dri2" already built-in [35.870] (II) RADEON(0): KMS Color Tiling: enabled [35.870] (II) RADEON(0): KMS Color Tiling 2D: disabled [35.870] (II) RADEON(0): KMS Pageflipping: enabled rican-linux@ibookG4-UbuntuMATE:~$ LIBGL_DEBUG=verbose glxinfo |grep render libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 4: 1002:4e56, driver r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig rican-linux@ibookG4-UbuntuMATE:~$ dpkg -l libgl1-mesa-dri Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libgl1-mesa-dr 10.5.0~rc1-0 powerpc free implementation of the OpenGL rican-linux@ibookG4-UbuntuMATE:~$ rican-linux@ibookG4-UbuntuMATE:~$ lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 rican-linux@ibookG4-UbuntuMATE:~$ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 10.5.0~rc1-0ubuntu1 Candidate: 10.5.0-0ubuntu1 Version table: 10.5.0-0ubuntu1 0 500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main powerpc Packages *** 10.5.0~rc1-0ubuntu1 0 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-powerpc-smp 3.18.5 Uname: Linux 3.18.0-13-powerpc-smp ppc ApportVersion: 2.16.1-0ubuntu2 Architecture: powerpc CurrentDesktop: MATE Date: Tue Mar 17 00:58:43 2015 InstallationDate: Installed on 2015-03-17 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha powerpc (20150225) SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1432949/+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 1432949]
Created attachment 123370 final fix? Could you please test this patch? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1432949 Title: r300 Mesa driver not loading with KMS enabled Status in Mesa: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I cannot get 3D acceleration to work. I was expecting to see the gears via the command 'glxgears' I have KMS enable on my iBook G4 by using the following parameter Linux radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 Here are my Mesa and Xorg output rican-linux@ibookG4-UbuntuMATE:~$ cat /var/log/Xorg.0.log |grep -e radeon -e dri2 -e drm -e KMS [32.774] Kernel command line: root=UUID=fadadc01-6fd5-49fa-85f3-9e52d0fe6155 ro quiet splash video=offb:off video=1024x768-32 video=radeonfb:off radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 [33.203] (II) xfree86: Adding drm device (/dev/dri/card0) [35.011] (II) LoadModule: "radeon" [35.012] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [35.337] (II) Module radeon: vendor="X.Org Foundation" [35.604] (II) [KMS] Kernel modesetting enabled. [35.697] (II) Loading sub module "dri2" [35.697] (II) LoadModule: "dri2" [35.697] (II) Module "dri2" already built-in [35.870] (II) RADEON(0): KMS Color Tiling: enabled [35.870] (II) RADEON(0): KMS Color Tiling 2D: disabled [35.870] (II) RADEON(0): KMS Pageflipping: enabled rican-linux@ibookG4-UbuntuMATE:~$ LIBGL_DEBUG=verbose glxinfo |grep render libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 4: 1002:4e56, driver r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig rican-linux@ibookG4-UbuntuMATE:~$ dpkg -l libgl1-mesa-dri Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libgl1-mesa-dr 10.5.0~rc1-0 powerpc free implementation of the OpenGL rican-linux@ibookG4-UbuntuMATE:~$ rican-linux@ibookG4-UbuntuMATE:~$ lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 rican-linux@ibookG4-UbuntuMATE:~$ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 10.5.0~rc1-0ubuntu1 Candidate: 10.5.0-0ubuntu1 Version table: 10.5.0-0ubuntu1 0 500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main powerpc Packages *** 10.5.0~rc1-0ubuntu1 0 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-powerpc-smp 3.18.5 Uname: Linux 3.18.0-13-powerpc-smp ppc ApportVersion: 2.16.1-0ubuntu2 Architecture: powerpc CurrentDesktop: MATE Date: Tue Mar 17 00:58:43 2015 InstallationDate: Installed on 2015-03-17 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha powerpc (20150225) SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1432949/+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 1452291] Re: Browser cannot use system proxy settings
I would recommend not to have system-wide proxy settings, but proxy setting for every connection. Since there could be different proxy servers in different locations. Each WiFi AP should have his own proxy settings saved. This also implies gui setup for proxy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1452291 Title: Browser cannot use system proxy settings Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: While I can create successfully system proxy settings using gsettings set org.gnome.system.proxy use-same-proxy false gsettings set org.gnome.system.proxy mode "'manual'" gsettings set org.gnome.system.proxy ignore-hosts "['localhost', '127.0.0.0/8', '192.168.0.0/16', '::1']" gsettings set org.gnome.system.proxy.ftp host "'192.168.112.1'" gsettings set org.gnome.system.proxy.ftp port 800 gsettings set org.gnome.system.proxy.socks host "'192.168.112.1'" gsettings set org.gnome.system.proxy.socks port 800 gsettings set org.gnome.system.proxy.http host "'192.168.112.1'" gsettings set org.gnome.system.proxy.http port 800 gsettings set org.gnome.system.proxy.http use-authentication false gsettings set org.gnome.system.proxy.http enabled true gsettings set org.gnome.system.proxy.https host "'192.168.112.1'" gsettings set org.gnome.system.proxy.https port 800 those settings are currently not being used by the browser app. Accordingly I would like to request the addition of a feature to use the system proxy settings in the browser app. I have tested this on an by Aquaris E4.5 with Ubuntu 14.10 (r21). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452291/+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 1485803] Re: [system settings] No notification for which Sim card call is received from
I agree this bug was partially solved by OTA-9. But only the part concerning displaying SIM when call is received. The part concerning different ringtones per SIM (or ideally per contact per SIM) was not solved. Also the information I would expect to be seen in call log in the first sight, not to click info button for this information. The suggestion for colour differentiation was awesome, if it is not possible to put the text information due to space reasons. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1485803 Title: [system settings] No notification for which Sim card call is received from Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: Incomplete Bug description: When using the dual sim feature of the BQ Aquaris 4.5, there is no indication of which sim card a call is being received from. I.e., I run two businesses, and when my phone rings I have no idea which number someone is calling. Ideally there would be a different ringtone per sim card, as well as text notification on the answer call panel. There should also be the option of setting a different message tone for incoming messages per sim card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1485803/+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 411688]
This bug is still present in Fedora 23 x86_64 and pulseaudio-7.1-1 My machine was sending ~ 180KB/s to 224.0.0.56 until I unchecked "Enable Multicast/RTP sender" in paprefs. For peace of mind, I ended up adding "unload-module module-rtp-send source=rtp.monitor" into /etc/pulse/default.pa -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto
[Touch-packages] [Bug 1368647] Re: GPS and location detection not working on Nexus 4
I have Nexus 4 with latest radio, yesterday I flashed the phone with bq- aquaris.en channel and it was not working. Maybe it would get the location eventually but if no location is acquired after 5 minutes, I consider it not working. I'm very much interested in knowing if anyone from Ubuntu team is working on resolving this issue. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1368647 Title: GPS and location detection not working on Nexus 4 Status in location-service package in Ubuntu: Confirmed Bug description: Mako with MultiROM, utopic r239 None of the apps I have tried including Weather, Google maps, OSM Touch and SensorStatus are able to use the phone's GPS. The SensorStatus app actually reports "Found supported backend", but finds no position or other GPS data. Location detection on the other hand is doing something, but it is really far off when it comes to determining the actual location of the device. The Weather app suggests my location as Vänsjö, Jämtland, which is about 400 km north of Stockholm where I am at. OSM Touch reports "no location available" and Google maps "Your location could not be determined" I don't know if the GPS has to "waken up" somehow, but it has not shown any form of life for me on Ubuntu Touch, even though it works perfectly fine when booting the phone as Android. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1368647/+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 33288]
I went through the patch written by me and unfortunately I can not make it so that it returns the same result as before. I've separated axes in which it searches for immediate up/down/left/right neighbours, sorted them and found the neighbours by single pass (+ number of possible neighbour candidates in the other axis for given block, which should be sqrt(n) in average case). The difference is that the patch searches for right-down neighbour by looking at down neighbour of its right neighbour and at the right neighbour of its down neighbour. If they match then it selects it as the right-bottom neighbour. Previous version just searched for the closest block which is to the right of the block and below the block (and looking at the code, the result could depend on order of the blocks in the searched array). Modifying the patch so that it would return the same results as without it would cost the whole efficiency. Anyway, the efficiency improvement of my patch is not as big as the one from Brian so you can reject it (but I think that it improves the conversion :) ). -- 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/33288 Title: Evince doesn't handle columns properly Status in Poppler: Confirmed Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Lucid: Fix Released Bug description: So, now that RC is here, let's propose it as an SRU. I've pushed it in lucid-proposed. The debdiff is poppler_0.12.4-0ubuntu4_2_0.12.4-0ubuntu5.debdiff attached there for information. I'm removing old debdiff to avoid confusion. poppler (0.12.4-0ubuntu5) lucid-proposed; urgency=low * debian/patches/11_column_selection.patch: - backport from upstream git commit to fix wrong selection in pdf when containing tables, long text, broken flow and so on. (fixing most of known issues with selection in pdf) (LP: #33288) When making a multi column selection from a PDF like this: http://www.specialist-games.com/mordheim/assets/lrb/1Rules.pdf And pasting the result into OpenOffice.org the columns are not maintained. The results unusable because the text from both columns becomes mixed. Please note, this is not a PDF problem, using Adobe Acrobat Reader 7.x under Windows does properly copy-paste columned text over to OpenOffice.org. Regards, Pascal de Bruijn To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/33288/+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 1462090] Re: Calling to numbers formatted with slash results in Call failed
I confirm the bug is fixed in OTA-5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1462090 Title: Calling to numbers formatted with slash results in Call failed Status in Canonical System Image: Fix Released Status in One Hundred Papercuts: New Status in telephony-service: New Status in telepathy-ofono package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Fix Released Bug description: When I call to numbers which are formatted with slash '/', I get call failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx xxx I get call failed, because numbers are automatically formatted as +421 2/xxx xxx xx or 02/xxx xxx xx. This is probably caused by incorrect regular expression in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-]. Please, consider this bug critical, since I cannot place any call to any fixed line in Slovakia, which is basic function of phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462090/+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 1453942] Re: Calling to some numbers results in Call failed
The bug is concerning telephony-service. See https://bugs.launchpad.net /canonical-devices-system-image/+bug/1462090. It is fixed in OTA-5. ** Changed in: dialer-app (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453942 Title: Calling to some numbers results in Call failed Status in dialer-app package in Ubuntu: Fix Released Bug description: When I try to call some numbers I cannot place the call and get Call failed message. After some investigation a think this is related to automatically adding the slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which is in VPN and I should use 0 to call out or use international format, I get these results when calling the same station: When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the call is successfully placed. When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and the call is failing. You probably remove displayed spaces when placing a call but do not remove slash signs. The formatting slash cannot be manually deleted. I am using: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1446054] Re: syncevolution and all day events synchronize from owncloud
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1446054 Title: syncevolution and all day events synchronize from owncloud Status in the base for Ubuntu mobile products: New Status in Calendar application for Ubuntu devices: New Status in qtorganizer5-eds package in Ubuntu: Confirmed Bug description: Hi. I have noticed a problem with synchronization between Onwcloud (vCal) and calendar app. All day events always appear today and the next day. The problem seems to be with DTSTART et DTEND : before sync | after sync removed during sync added during sync --- BEGIN:VCALENDAR BEGIN:VCALENDAR VERSION:2.0 VERSION:2.0 BEGIN:VEVENT BEGIN:VEVENT SUMMARY:@@@ Rencontre (1997) @@@ SUMMARY:@@@ Rencontre (1997) @@@ DTEND;VALUE=DATE:20150419| DTEND;VALUE=DATE:20150420 DTSTART;VALUE=DATE:20150419 DTSTART;VALUE=DATE:20150419 RRULE:BYMONTH=3;FREQ=YEARLY UID:20150420T051538Z-4109-32011-149 UID:20150420T051538Z-4109-32011-149 9-11@ubuntu-phablet 9-11@ubuntu-phablet END:VEVENT END:VEVENT END:VCALENDAREND:VCALENDAR --- Any ideas ? Thank. My configuration : Nexus 4 Ubuntu Touch 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1446054/+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 1462090] Re: Calling to numbers formatted with slash results in Call failed
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1462090 Title: Calling to numbers formatted with slash results in Call failed Status in the base for Ubuntu mobile products: New Status in One Hundred Papercuts: New Status in Telephony Service: New Status in telephony-service package in Ubuntu: New Bug description: When I call to numbers which are formatted with slash '/', I get call failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx xxx I get call failed, because numbers are automatically formatted as +421 2/xxx xxx xx or 02/xxx xxx xx. This is probably caused by incorrect regular expression in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-]. Please, consider this bug critical, since I cannot place any call to any fixed line in Slovakia, which is basic function of phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462090/+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 1462090] Re: Calling to numbers formatted with slash results in Call failed
** Also affects: telephony-service Importance: Undecided Status: New ** Also affects: hundredpapercuts Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1462090 Title: Calling to numbers formatted with slash results in Call failed Status in One Hundred Papercuts: New Status in Telephony Service: New Status in telephony-service package in Ubuntu: New Bug description: When I call to numbers which are formatted with slash '/', I get call failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx xxx I get call failed, because numbers are automatically formatted as +421 2/xxx xxx xx or 02/xxx xxx xx. This is probably caused by incorrect regular expression in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-]. Please, consider this bug critical, since I cannot place any call to any fixed line in Slovakia, which is basic function of phone. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1462090/+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 1462090] [NEW] Calling to numbers formatted with slash results in Call failed
Public bug reported: When I call to numbers which are formatted with slash '/', I get call failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx xxx I get call failed, because numbers are automatically formatted as +421 2/xxx xxx xx or 02/xxx xxx xx. This is probably caused by incorrect regular expression in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-]. Please, consider this bug critical, since I cannot place any call to any fixed line in Slovakia, which is basic function of phone. ** Affects: telephony-service Importance: Undecided Status: New ** Affects: telephony-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1462090 Title: Calling to numbers formatted with slash results in Call failed Status in Telephony Service: New Status in telephony-service package in Ubuntu: New Bug description: When I call to numbers which are formatted with slash '/', I get call failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx xxx I get call failed, because numbers are automatically formatted as +421 2/xxx xxx xx or 02/xxx xxx xx. This is probably caused by incorrect regular expression in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-]. Please, consider this bug critical, since I cannot place any call to any fixed line in Slovakia, which is basic function of phone. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1462090/+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 1453942] Re: Calling to some numbers results in Call failed
This is probably on telephony-service to handle the slash character, since I found regexp [p+*#(),;-] in libtelephonyservice/phoneutils.cpp for nondialable digits removal, which should probably read [p+*#/(),;-]. I am going to file a bug against telephony-service. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453942 Title: Calling to some numbers results in Call failed Status in dialer-app package in Ubuntu: Confirmed Bug description: When I try to call some numbers I cannot place the call and get Call failed message. After some investigation a think this is related to automatically adding the slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which is in VPN and I should use 0 to call out or use international format, I get these results when calling the same station: When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the call is successfully placed. When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and the call is failing. You probably remove displayed spaces when placing a call but do not remove slash signs. The formatting slash cannot be manually deleted. I am using: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1453942] Re: Calling to some numbers results in Call failed
Could someone assign the Critical importance to this bug? It is basic functionality to place a calls. If I did not have a SIM card in VPN and use the hack above I would not be able place calls to Slovak fixed line numbers. Not everybody has such SIM. It is 100% reproducible and probably caused by pretty print telephone number function. I would not mind of disallowing this function, since it is not needed and does not follow standard either. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453942 Title: Calling to some numbers results in Call failed Status in dialer-app package in Ubuntu: Confirmed Bug description: When I try to call some numbers I cannot place the call and get Call failed message. After some investigation a think this is related to automatically adding the slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which is in VPN and I should use 0 to call out or use international format, I get these results when calling the same station: When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the call is successfully placed. When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and the call is failing. You probably remove displayed spaces when placing a call but do not remove slash signs. The formatting slash cannot be manually deleted. I am using: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1453942] Re: Calling to some numbers results in Call failed
** Changed in: dialer-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453942 Title: Calling to some numbers results in Call failed Status in dialer-app package in Ubuntu: Confirmed Bug description: When I try to call some numbers I cannot place the call and get Call failed message. After some investigation a think this is related to automatically adding the slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which is in VPN and I should use 0 to call out or use international format, I get these results when calling the same station: When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the call is successfully placed. When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and the call is failing. You probably remove displayed spaces when placing a call but do not remove slash signs. The formatting slash cannot be manually deleted. I am using: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1453506] Re: cannot pick incoming call
** Changed in: dialer-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453506 Title: cannot pick incoming call Status in dialer-app package in Ubuntu: Confirmed Bug description: aquaris bq phone. from suspend / lockscreen i am unable to select incoming call. no visual inteface appears, even if going to phone-app manually while phone rings. please fix soon. this is a basic phone function! thank you... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453506/+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 1453942] [NEW] Calling to some numbers results in Call failed
Public bug reported: When I try to call some numbers I cannot place the call and get Call failed message. After some investigation a think this is related to automatically adding the slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which is in VPN and I should use 0 to call out or use international format, I get these results when calling the same station: When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the call is successfully placed. When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and the call is failing. You probably remove displayed spaces when placing a call but do not remove slash signs. The formatting slash cannot be manually deleted. I am using: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1 ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453942 Title: Calling to some numbers results in Call failed Status in dialer-app package in Ubuntu: New Bug description: When I try to call some numbers I cannot place the call and get Call failed message. After some investigation a think this is related to automatically adding the slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which is in VPN and I should use 0 to call out or use international format, I get these results when calling the same station: When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the call is successfully placed. When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and the call is failing. You probably remove displayed spaces when placing a call but do not remove slash signs. The formatting slash cannot be manually deleted. I am using: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1453506] Re: cannot pick incoming call
I am also affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453506 Title: cannot pick incoming call Status in dialer-app package in Ubuntu: New Bug description: aquaris bq phone. from suspend / lockscreen i am unable to select incoming call. no visual inteface appears, even if going to phone-app manually while phone rings. please fix soon. this is a basic phone function! thank you... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453506/+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 1453942] Re: Calling to some numbers results in Call failed
Moreover the dialed number is not added to the recent call list. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453942 Title: Calling to some numbers results in Call failed Status in dialer-app package in Ubuntu: New Bug description: When I try to call some numbers I cannot place the call and get Call failed message. After some investigation a think this is related to automatically adding the slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which is in VPN and I should use 0 to call out or use international format, I get these results when calling the same station: When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the call is successfully placed. When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and the call is failing. You probably remove displayed spaces when placing a call but do not remove slash signs. The formatting slash cannot be manually deleted. I am using: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1199571]
(In reply to Behdad Esfahbod from comment #9) Patchset is now upstream in FreeType. Thank you very much for all the effort you've put into this! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1199571 Title: Huge multi-threading violations in freetype Status in FreeType: High Quality Font Rendering: Fix Released Status in freetype package in Ubuntu: In Progress Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/freetype/+bug/1199571/+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 299725]
I'm closing this since it seems to be already fixed (by http://cgit.freedesktop.org/poppler/poppler/commit/?id=f3a1b765bd6a58d327a80feedbe30e1c0792076e and http://cgit.freedesktop.org/poppler/poppler/commit/?id=5056e33e01ce0f7db1a5401b7b38d30e84eedf69). -- 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/299725 Title: Context of adjacent different fonts are displayed incorrectly by Evince Status in Poppler: Fix Released Status in poppler package in Ubuntu: Triaged Bug description: Binary package hint: evince Use Evince to open a PDF-file including CJK characters, and select some of these characters with cursor, and most of them disappears, and some are rendered as different characters or ASCII characters. Using Ubuntu 8.10 with Evince 2.24.1. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/evince Package: evince 2.24.1-0ubuntu1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux 2.6.27-8-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/299725/+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 1199571]
(In reply to Behdad Esfahbod from comment #4) Looks like copying thread-local storage macros from pixman-compiler.h and using them to use per-thread FT_Library might easily get most of this resolved. I can take a look if no one else steps in. Hi Behdad, had you time to look at this already? Regards Marek -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1199571 Title: Huge multi-threading violations in cairo Status in libcairo - cairo vector graphics library: Confirmed Status in “cairo” package in Ubuntu: Triaged Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/libcairo/+bug/1199571/+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 1367118] [NEW] [System Product Name, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
Public bug reported: Using Ubuntu 13.10 - have tried re-loading alsa driver but no success - still no sound from monitor speakers. Have looked at sound card information BUT do not know what to look for! Am a total beginner with OS ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1486 F pulseaudio /dev/snd/controlC0: user 1486 F pulseaudio CurrentDmesg: [ 1535.971713] audit_printk_skb: 5 callbacks suppressed [ 1535.971719] type=1400 audit(1410244692.413:66): apparmor=STATUS operation=profile_replace parent=2247 profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2251 comm=apparmor_parser [ 1535.971732] type=1400 audit(1410244692.413:67): apparmor=STATUS operation=profile_replace parent=2247 profile=unconfined name=/usr/sbin/cupsd pid=2251 comm=apparmor_parser [ 1535.972918] type=1400 audit(1410244692.417:68): apparmor=STATUS operation=profile_replace parent=2247 profile=unconfined name=/usr/sbin/cupsd pid=2251 comm=apparmor_parser Date: Tue Sep 9 07:44:59 2014 InstallationDate: Installed on 2014-04-08 (153 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1486 F pulseaudio /dev/snd/controlC0: user 1486 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to saucy on 2014-04-30 (131 days ago) dmi.bios.date: 08/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0115 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-X/1333 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0115:bd08/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: dmi.product.name: System Product Name dmi.product.version: Rev 1.xx dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- 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/1367118 Title: [System Product Name, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: Using Ubuntu 13.10 - have tried re-loading alsa driver but no success - still no sound from monitor speakers. Have looked at sound card information BUT do not know what to look for! Am a total beginner with OS ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1486 F pulseaudio /dev/snd/controlC0: user 1486 F pulseaudio CurrentDmesg: [ 1535.971713] audit_printk_skb: 5 callbacks suppressed [ 1535.971719] type=1400 audit(1410244692.413:66): apparmor=STATUS operation=profile_replace parent=2247 profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2251 comm=apparmor_parser [ 1535.971732] type=1400 audit(1410244692.413:67): apparmor=STATUS operation=profile_replace parent=2247 profile=unconfined name=/usr/sbin/cupsd pid=2251 comm=apparmor_parser [ 1535.972918] type=1400 audit(1410244692.417:68): apparmor=STATUS operation=profile_replace parent=2247 profile=unconfined name=/usr/sbin/cupsd pid=2251 comm=apparmor_parser Date: Tue Sep 9 07:44:59 2014 InstallationDate: Installed on 2014-04-08 (153 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1486 F pulseaudio /dev/snd/controlC0: user 1486 F pulseaudio Symptom_Jack: Green Line Out, Rear
[Touch-packages] [Bug 1367118] Re: [System Product Name, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
Can anyone help? I'm not a computer geek - need SIMPLE instructions on how to regain sound -- 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/1367118 Title: [System Product Name, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: Using Ubuntu 13.10 - have tried re-loading alsa driver but no success - still no sound from monitor speakers. Have looked at sound card information BUT do not know what to look for! Am a total beginner with OS ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1486 F pulseaudio /dev/snd/controlC0: user 1486 F pulseaudio CurrentDmesg: [ 1535.971713] audit_printk_skb: 5 callbacks suppressed [ 1535.971719] type=1400 audit(1410244692.413:66): apparmor=STATUS operation=profile_replace parent=2247 profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2251 comm=apparmor_parser [ 1535.971732] type=1400 audit(1410244692.413:67): apparmor=STATUS operation=profile_replace parent=2247 profile=unconfined name=/usr/sbin/cupsd pid=2251 comm=apparmor_parser [ 1535.972918] type=1400 audit(1410244692.417:68): apparmor=STATUS operation=profile_replace parent=2247 profile=unconfined name=/usr/sbin/cupsd pid=2251 comm=apparmor_parser Date: Tue Sep 9 07:44:59 2014 InstallationDate: Installed on 2014-04-08 (153 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1486 F pulseaudio /dev/snd/controlC0: user 1486 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to saucy on 2014-04-30 (131 days ago) dmi.bios.date: 08/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0115 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-X/1333 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0115:bd08/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: dmi.product.name: System Product Name dmi.product.version: Rev 1.xx dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1367118/+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
