[Touch-packages] [Bug 1758818] Re: kernel_oops crashed with SIGSEGV in _PyGC_CollectIfEnabled()
*** This bug is a duplicate of bug 1758817 *** https://bugs.launchpad.net/bugs/1758817 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1758817, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758818/+attachment/5090778/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758818/+attachment/5090781/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758818/+attachment/5090784/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758818/+attachment/5090785/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758818/+attachment/5090786/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758818/+attachment/5090787/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758818/+attachment/5090788/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1758817 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1758818 Title: kernel_oops crashed with SIGSEGV in _PyGC_CollectIfEnabled() Status in apport package in Ubuntu: New Bug description: kernel_oops crashed with SIGSEGV in _PyGC_CollectIfEnabled() ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportLog: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 24 21:46:30 2018 ExecutablePath: /usr/share/apport/kernel_oops InstallationDate: Installed on 2017-10-20 (156 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/kernel_oops 34436 ProcEnviron: PATH=(custom, no user) LANG=el_GR.UTF-8 SHELL=/bin/false Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SegvAnalysis: Segfault happened at: 0x4436c4: testb $0x40,0xa9(%rax) PC (0x004436c4) ok source "$0x40" ok destination "0xa9(%rax)" (0xdb2400ff242424cd) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () ?? () ?? () _PyGC_CollectIfEnabled () ?? () Title: kernel_oops crashed with SIGSEGV in _PyGC_CollectIfEnabled() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1758818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758498] Re: perl crashed with SIGABRT in _dbus_abort()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: perl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1758498 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: Confirmed Bug description: I was browsing the internet using firefox installed from ubuntu repo ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Fri Mar 23 22:56:12 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2018-03-15 (9 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() 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/ubuntu/+source/perl/+bug/1758498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725921] Re: [regression] Combobox menus have gray text on gray background
BTW, I think the bug there is that the menu background is light. They are meant to be dark now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1725921 Title: [regression] Combobox menus have gray text on gray background Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Xenial: In Progress Status in ubuntu-themes source package in Artful: New Status in ubuntu-themes source package in Bionic: Fix Released Bug description: [Impact] Regression: After a recent update, combobox menus have gray text on gray background making them almost unreadable. [Test Case] 1. Open GIMP and start a new file. 2. At the bottom of the window click on the 'px' combo box. 3. Verify the menu that appears has readable text (light grey text on a dark grey background). [Regression Potential] Very low. The fix changes the theme for "gtk-combobox-popup-menu" only. So theoretically it should not be possible for the fix to affect anything other than combobox menus. [Other Info] The regression happened in updates to 18.04, 17.10 and 16.04 around late 2017 - January 2018. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758589] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1758589 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1758589 Title: The wifi will be disconnected and the only thing I can do is to reboot the laptop Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: First of all, I am not sure whether it's true that this is a bug of network-manager, but it is true that this should be a bug related with network (wifi connection). Here is the issue: Every time after I login into the account, about 20 minutes later, the wifi will be disconnected automatically. I even cannot reconnect the wifi manually, the only thing that I can do is to reboot the laptop. After login again, wifi can be connected (but through manual way). By the way, during the period of wifi disconnection, I checked the "Wi-Fi Networks" by click "Select Network" in order to try to reconnect it manually. But I found that there is only one SSID which previously the laptop connected to. However, I was definitely sure that there should be more than one SSID being showed in the wifi list. Even for this only one SSID, like I mentioned before, I cannot reconnect manually unless I reboot the system. Finally, I set the wifi to be connected automatically after I login to the system, however, it just can't. I can only connect to the wifi manually after I login to the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 19:02:12 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-15 (68 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH wlp4s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 WolfieNet-Secure eb45c742-ba31-4f31-acf2-13a2768bcc29 /org/freedesktop/NetworkManager/ActiveConnection/5 enp5s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758589/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758589] Re: The wifi will be disconnected and the only thing I can do is to reboot the laptop
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1758589 Title: The wifi will be disconnected and the only thing I can do is to reboot the laptop Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: First of all, I am not sure whether it's true that this is a bug of network-manager, but it is true that this should be a bug related with network (wifi connection). Here is the issue: Every time after I login into the account, about 20 minutes later, the wifi will be disconnected automatically. I even cannot reconnect the wifi manually, the only thing that I can do is to reboot the laptop. After login again, wifi can be connected (but through manual way). By the way, during the period of wifi disconnection, I checked the "Wi-Fi Networks" by click "Select Network" in order to try to reconnect it manually. But I found that there is only one SSID which previously the laptop connected to. However, I was definitely sure that there should be more than one SSID being showed in the wifi list. Even for this only one SSID, like I mentioned before, I cannot reconnect manually unless I reboot the system. Finally, I set the wifi to be connected automatically after I login to the system, however, it just can't. I can only connect to the wifi manually after I login to the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 19:02:12 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-15 (68 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH wlp4s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 WolfieNet-Secure eb45c742-ba31-4f31-acf2-13a2768bcc29 /org/freedesktop/NetworkManager/ActiveConnection/5 enp5s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758589/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758273] Re: DD2.2 freezes/hangs after 20mins of uptime
I do see gnome and X installed on this system and /etc/os-release does not indicate much as to whether its a server/desktop install: root@p215n15:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Bionic Beaver (development branch)" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Sleep inactive is indeed set to 20 mins: $ gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 1200 But should user inactivity timer kinckin and invoke systemd- suspend.service even if there is an active terminal session for the root user ? -- 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/1758273 Title: DD2.2 freezes/hangs after 20mins of uptime Status in The Ubuntu-power-systems project: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: == Comment: #0 - Application Cdeadmin - 2018-03-19 09:30:53 == == Comment: #1 - Application Cdeadmin <> - 2018-03-19 09:30:55 == == Comment: #2 - Application Cdeadmin <> - 2018-03-19 09:30:57 == --- Comment From brihh 2018-03-19 09:10:30 EDT --- Needless to say, machine is pretty unusable. Needed for Performance testing for release. == Comment: #3 - Application Cdeadmin <> - 2018-03-19 10:10:59 == --- Comment From vaibhav92 2018-03-19 10:06:17 EDT --- @pridhiviraj Any idea who can look into this ? --- Comment From dougmill-ibm 2018-03-19 10:09:59 EDT --- If machine is locked-up and console is unresponsive, try collecting eSEL data from the BMC. == Comment: #4 - Application Cdeadmin - 2018-03-19 10:40:59 == --- Comment From pridhiviraj 2018-03-19 10:38:47 EDT --- @brihh Can you use latest 03/15 PNOR and re-create the issue. And also before it hangs please collect OPAL and kernel logs. @vaibhav92 If it is re-creatable OPAL/EM team need to look at it. == Comment: #5 - Application Cdeadmin <> - 2018-03-19 11:01:58 == --- Comment From vaibhav92 2018-03-19 10:41:53 EDT --- Saw this in the kernel-log of the system: [ 1247.404962] PM: suspend entry (s2idle) [ 1247.404970] PM: Syncing filesystems ... done. Looks like its getting suspended after 20 mins of inactivity. Looking at the /etc/systemd/logind.conf see IdleAction by default is 'ignore': #IdleAction=ignore #IdleActionSec=30min But clearly someone is issuing a suspend to the system. So this probably need to be looked by the distro/Power-Management/EM team --- Comment From megcurry 2018-03-19 10:43:14 EDT --- Please advise re. Assignments and Labels that would get the right team working on this.Mirror label gets a Bz opened, and that is necessary or at least useful for some of the LTC teams to look at things, right? --- Comment From brihh 2018-03-19 10:47:45 EDT --- odd about inactivity - i once had a test running for 20mins and it still froze: `08:52:23 up 20 min, 4 users, load average: 64.40, 98.94, 64.32` --- Comment From brihh 2018-03-19 10:49:30 EDT --- @pridhiviraj where is the latest 3/15 PNOR that I can load? ``` == Comment: #8 - Application Cdeadmin <> - 2018-03-19 12:40:54 == --- Comment From pridhiviraj 2018-03-19 12:34:18 EDT --- ``` Mar 19 11:35:01 p215n15 rsyslogd-2007: action 'action 13' suspended, next retry is Mon Mar 19 11:35:31 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Mar 19 11:35:01 p215n15 CRON[6464]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 19 11:42:39 p215n15 systemd[1]: Starting Cleanup of Temporary Directories... Mar 19 11:42:39 p215n15 rsyslogd-2007: action 'action 13' suspended, next retry is Mon Mar 19 11:43:39 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Mar 19 11:42:40 p215n15 systemd-tmpfiles[6504]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Mar 19 11:42:40 p215n15 systemd[1]: Started Cleanup of Temporary Directories. Mar 19 11:45:01 p215n15 rsyslogd-2007: action 'action 13' suspended, next retry is Mon Mar 19 11:46:01 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Mar 19 11:45:01 p215n15 CRON[6524]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 19 11:47:39 p215n15 systemd[1]: Starting Message of the Day... Mar 19 11:47:39 p215n15 rsyslogd-2007: action 'action 13' suspended, next retry is Mon Mar 19 11:48:39 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Mar 19 11:47:40 p215n15 50-motd-news[6528]: * Meltdown, Spectre and Ubuntu: What are the attack vectors, Mar 19 11:47:40 p215n15 50-motd-news[6528]:how the fixes work, and everything e
[Touch-packages] [Bug 1757299] Re: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications
** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1757299 Title: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications Status in xorg package in Ubuntu: New Bug description: The problem is that after launching a few applications, the GUI may become unresponsive, although this is not consistently reproducible. When the GUI is unresponsive, it is correlated to high CPU utilization of xorg. An example reproduction scenario is launch the following in order, and quickly: startx xterm via twm another xterm via the first xterm tmux firefox-esr bluetooth-manager pavucontrol While the above are launching, maximize the xterm running tmux, and the GUI immediately becomes unresponsive. For example, Ctrl+Alt+Fn don't respond. After this, I logged in via ssh, attached to tmux, launched htop, copied htop output, which shows xorg at 94.6 CPU%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd * Starting AppArmor profiles [160G [154G[ OK ] * Restoring resolver state... [160G [154G[ OK ] CompositorRunning: None Date: Tue Mar 20 17:15:16 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] JournalErrors: -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 CDT. -- Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon already running. MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1757299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758569] Re: can't switch to bluetooth speakers
** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu) ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags added: a2dp -- 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/1758569 Title: can't switch to bluetooth speakers Status in firefox package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I'm not really sure this problem is with bluez, pulseaudio or firefox. The main symptom is that Firefox refuses to send audio to my AD2P compliant bluetooth speakers. I can select the speakers with the gnome-control-center for bluetooth and play the test sounds (even while FF is playing sound through the computer (DELL N7010 laptop) speakers. Even VLC has the same problem so I suspect this is a system problem and not an application problem. Note - I installed pavucontrol and was able to switch the audio of a playing youtube to the bluetooth speakers. now for your recommended info lsb_release says Ubuntu 17.10 Firefox is Version 59.0.1 dpkg -l | grep -i blue says ii bluez 5.46-0ubuntu3 amd64 Bluetooth tools and daemons ii bluez-cups 5.46-0ubuntu3 amd64 Bluetooth printer driver for CUPS ii bluez-obexd 5.46-0ubuntu3 amd64 bluez obex daemon ii bluez-tools 0.2.0~20140808-5build1 amd64 Set of tools to manage Bluetooth devices for linux ii gir1.2-gnomebluetooth-1.0:amd64 3.26.1-1 amd64 Introspection data for GnomeBluetooth ii gnome-bluetooth 3.26.1-1 amd64 GNOME Bluetooth tools ii libbluetooth3:amd64 5.46-0ubuntu3 amd64 Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.26.1-1 amd64 GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth 1:10.0-2ubuntu3.1 amd64 Bluetooth module for PulseAudio sound server ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 14:10:02 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron N7010 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=94a7c54a-20a6-4bd0-905c-918de9b5ff61 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/31/2011:svnDellInc.:pnInspironN7010:pvrA11:rvnDellInc.:rn08VFX1:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N7010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: C0:CB:38:C2:18:51 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING INQUIRY RX bytes:234685 acl:43 sco:0 events:33407 errors:0 TX bytes:56372584 acl:66043 sco:0 commands:212 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 655619] Re: Auto-hinter muddles tildes/macrons in Ubuntu font <19px (ñĀÃāãŌÕōõ)
** Bug watch added: Non-GNU Savannah Bug Tracker #23537 http://savannah.nongnu.org/bugs/?23537 ** Also affects: freetype via http://savannah.nongnu.org/bugs/?23537 Importance: Unknown Status: Unknown -- 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/655619 Title: Auto-hinter muddles tildes/macrons in Ubuntu font <19px (ñĀÃāãŌÕōõ) Status in FreeType: Unknown Status in freetype package in Ubuntu: Triaged Bug description: 1. Copy and paste this line into the address field of a Web browser: data:text/html;charset=UTF-8, ñĀÃāãŌÕōõ 2. Reduce the font-size until the tildes ˜ become indistinguishable from the macrons ¯. Rendered in 13pt Regular Sample Glyphs: õ Description: At size 18 and less õ looks o that doesn't have tilde but simple line on it. I don't know if it's a bug but there may be different similar letters in other languages. Õ is estonian font. UA String: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100915 Ubuntu/10.04 (lucid) Firefox/3.6.10 To manage notifications about this bug go to: https://bugs.launchpad.net/freetype/+bug/655619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757299] Re: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications
just had a lockup watching a youtube video in firefox-esr. i did something extremely simple, i think it was push the pavucontrol window behind the firefox-esr window, which did so, but immediately thereafter the video image froze, the mouse could still move the cursor but the mouse and keyboard were otherwise unable to get any response, not even to ctl-alt-Fn, nothing visible would be expected from ctl-alt- PrintScreen-s, saw no response to ctl-alt-PrintScreen-e either, nor, surprisingly, to ctl-alt-PrintScreen-k. The sound played on via pusleaudio and bluetooth into my headphones for 2 more minutes, then it fell silent. After 10 minutes it all remained thus. i tried to login via ssh but unfortunately my phone was connected to mobile data but not wifi so i presumed ubuntu was not responding via ssh either, heck it likely would have if the phone's wifi radio was enabled. well this occurrence does serve the purpose of verifying that the problem does occur in bionic either while playing video or not playing video. the system did respond to ctl-alt-PrintScreen-b and booted up normally. in /var/crash all i found was a file named .lock, zero length, dated 3-22 12:42:30pm. dunno what that's from, curious, no bash history survived from that day, this is what i found from around then in syslog: Mar 22 12:17:01 op755 CRON[7216]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 22 12:42:28 op755 kernel: [76631.137616] Web Content[4830]: segfault at fffe8 ip 7fc182a1aab1 sp 7ffee816bb10 error 4 in libxul.so[7fc17ee3+4e3] Mar 22 13:01:54 op755 bluetoothd[577]: /org/bluez/hci0/dev_00_0C_8A_AA_FE_70/fd1: fd(36) ready Mar 22 13:01:55 op755 rtkit-daemon[4718]: Supervising 1 threads of 1 processes of 1 users. Mar 22 13:01:55 op755 rtkit-daemon[4718]: Successfully made thread 7434 of process 4717 (n/a) owned by '444' RT at priority 5. Mar 22 13:01:55 op755 rtkit-daemon[4718]: Supervising 2 threads of 1 processes of 1 users. Mar 22 13:01:55 op755 kernel: [77798.576032] input: 00:0C:8A:AA:FE:70 as /devices/virtual/input/input9 Mar 22 13:12:21 op755 kernel: [78424.582540] perf: interrupt took too long (4900 > 4897), lowering kernel.perf_event_max_sample_rate to 40750 Mar 22 13:17:01 op755 CRON[7486]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 22 14:17:01 op755 CRON[7648]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) and found this in apport.log: ERROR: apport (pid 1591) Sat Mar 10 08:04:36 2018: called for pid 1582, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 1591) Sat Mar 10 08:04:36 2018: script: /usr/bin/blueman-manager, interpreted by /usr/bin/python3.6 (command line "/usr/bin/python3 /usr/bin/blueman-manager") ERROR: apport (pid 1591) Sat Mar 10 08:04:36 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 1591) Sat Mar 10 08:04:40 2018: wrote report /var/crash/_usr_bin_blueman-manager.444.crash ERROR: apport (pid 1759) Sun Mar 18 06:47:37 2018: called for pid 1643, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 1759) Sun Mar 18 06:47:37 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f ERROR: apport (pid 1759) Sun Mar 18 06:47:37 2018: executable version is blacklisted, ignoring ERROR: apport (pid 2730) Tue Mar 20 14:19:04 2018: called for pid 1219, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2730) Tue Mar 20 14:19:04 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f ERROR: apport (pid 2730) Tue Mar 20 14:19:04 2018: executable version is blacklisted, ignoring ERROR: apport (pid 2755) Tue Mar 20 14:19:21 2018: called for pid 2732, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2755) Tue Mar 20 14:19:21 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f ERROR: apport (pid 2755) Tue Mar 20 14:19:21 2018: executable version is blacklisted, ignoring ERROR: apport (pid 4370) Tue Mar 20 19:04:53 2018: called for pid 4294, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 4370) Tue Mar 20 19:04:53 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f ERROR: apport (pid 4370) Tue Mar 20 19:04:53 2018: executable version is blacklisted, ignoring ERROR: apport (pid 7315) Thu Mar 22 12:42:30 2018: called for pid 4830, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7315) Thu Mar 22 12:42:30 2018: executable: /usr/lib/firefox-esr/plugin-container (command line "/usr/lib/firefox-esr/plugin-container -greomni /usr/lib/firefox-esr/omni.ja -appomni /usr/lib/f
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Please log a new bug using this command so that we may examine your system in detail: ubuntu-bug bluez -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files
Yes, I mentioned that 13 days ago back in comment #2 and again in comment #12. In comments #3 and #13 you told us that was not the problem. ** Changed in: ffmpeg (Ubuntu) Status: New => Invalid -- 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/1755144 Title: No audio on vlc or videos sound or video files Status in ffmpeg package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Up until a few weeks ago there was no problem with playing sound from mp3 files. I have a pair of usb speakers. Audio plays Ok on them for video clips using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok using Rhythmbox. I've also tried vlc 3.0 with no success. Interestingly, the standard Videos app (Totem?) also doesn't play sound on these speakers either of an mp4 file (downloaded from YouTube, though it plays Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I first reported this as bug 1752267 as I thought that the problem was with vlc. On that bug, it was suggested that the problem is with Pulseaudio. Just now, I've tried to play sound through my monitor's built in speakers connected by hdmi (though the monitor displays Ok) with no success even though the built-in speakers play sound using pavucontrol when testing is invoked. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: john 2410 F pulseaudio /dev/snd/controlC0: john 2410 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 12 11:06:46 2018 InstallationDate: Installed on 2016-12-08 (458 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1755144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725921] Re: [regression] Combobox menus have gray text on gray background
jibel, Please log a new bug for that. Also, do you know of any other apps that show it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1725921 Title: [regression] Combobox menus have gray text on gray background Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Xenial: In Progress Status in ubuntu-themes source package in Artful: New Status in ubuntu-themes source package in Bionic: Fix Released Bug description: [Impact] Regression: After a recent update, combobox menus have gray text on gray background making them almost unreadable. [Test Case] 1. Open GIMP and start a new file. 2. At the bottom of the window click on the 'px' combo box. 3. Verify the menu that appears has readable text (light grey text on a dark grey background). [Regression Potential] Very low. The fix changes the theme for "gtk-combobox-popup-menu" only. So theoretically it should not be possible for the fix to affect anything other than combobox menus. [Other Info] The regression happened in updates to 18.04, 17.10 and 16.04 around late 2017 - January 2018. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
** Summary changed: - [USB-Audio - SteelSeries Arctis 7, playback] No sound at all + [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback -- 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/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback Status in pulseaudio package in Ubuntu: New Bug description: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758498] Re: perl crashed with SIGABRT in _dbus_abort()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1758498 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: New Bug description: I was browsing the internet using firefox installed from ubuntu repo ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Fri Mar 23 22:56:12 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2018-03-15 (9 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() 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/ubuntu/+source/perl/+bug/1758498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Hi I have this problem both on 16.04 and 17.10, and it is NOT related to wifi, since on my 16.04 desktop there is no wifi module at all. I tried installing 5.49 blues on 16.04 host, it does not seem to help, but I can not be 100% sure since I did not check whether exact new bt service was operating. 17.10 contrary is macbook laptop with BCM4360 adapter and wl driver, but disabling wifi and removing the module does not help. Rebooting 17.10 with new audio.conf/hcid.conf and using blueman to pair seems to help, but that can be a coincidence. What steps you want me to make to provide more debug information? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758762] [NEW] Dedug
Private bug reported: can't get rid of it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 BootLog: [[0;32m OK [0m] Started Network Manager. Starting Network Manager Wait Online... Starting Network Manager Script Dispatcher Service... [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 25 19:04:53 2018 DistUpgraded: 2016-09-30 19:40:15,256 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:02a0] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:02a0] InstallationDate: Installed on 2015-10-06 (901 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) MachineType: Dell Inc. Studio 1737 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=61766765-04bf-4526-98f7-7c3d69ae38a1 ro nopat drm.debug=0xe vesafb.invalid=1 plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-09-30 (540 days ago) dmi.bios.date: 02/11/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0P792H dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/11/2009:svnDellInc.:pnStudio1737:pvrA05:rvnDellInc.:rn0P792H:rvrA05:cvnDellInc.:ct8:cvrA05: dmi.product.name: Studio 1737 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Mar 24 22:59:12 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21570 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1758762 Title: Dedug Status in xorg package in Ubuntu: New Bug description: can't get rid of it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 BootLog: [[0;32m OK [0m] Started Network Manager. Starting Network Manager Wait Online... Starting Network Manager Script Dispatcher Service... [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 25 19:04:53 2018 DistUpgraded: 2016-09-30 19:40:15,256 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:02a0] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:02a0] InstallationDate: Installed on 2015-10-06 (901 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) MachineType: Dell Inc. Studio 1737 ProcEnvi
[Touch-packages] [Bug 1756006] Re: FFe: Support suspend-to-hibernate
>From systemd point of view, the patches are relatively straight forward, and simply add "one more way to sleep/suspend/hybernate/etc" without affecting any other code paths or any other functionality. Thus i see little risk for landing the systemd patches. If this turns out to be bad, only the policy would need to be change to either not offer it by default, or not use by default. Or some such. -- 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/1756006 Title: FFe: Support suspend-to-hibernate Status in gnome-settings-daemon package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
This is a very big problem. A lot of packages from external repos are still using libcurl3. In my opinion libcurl3 and libcurl4 should be able to coexist. I tried the workaround proposed by @marcosjacoby, but I get errors like: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found or curl: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_4' not found (required by curl) It depends on the last libcurl version I installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop
Same problem with HP-250-G4-Notebook-PC $ cat /proc/asound/card*/codec* | grep Codec Codec: Realtek ALC3227 Codec: Intel Skylake HDMI $ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP HD Audio Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1737614 Title: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a new laptop HP-15-BS576TX which has this Intel Corporation Sunrise Point-LP HD Audio. 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) The laptop sound works perfectly fine in Windows 10 with realtek drivers. However, in Ubuntu 17.10, the volume is significantly low, that I've to scroll the volume slider above 100% mark in pulseaudio to the maximum to get acceptable level of sound. I suspect the sound quality also is low (mono-like), may be not coming from all speakers (perhaps subwoofer exist for this model). Also alsamixer shows the speaker volume at the maximum. Details about the audio hardware are below: :~$ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Hewlett-Packard Company Device 832b Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- /proc/asound/card0/codec#0 <== Codec: Realtek ALC3227 ==> /proc/asound/card0/codec#2 <== Codec: Intel Kabylake HDMI :~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 I have gone through Linux kernel sources ALSA and Snd-HDA lists and unable to find any optimizations for this laptop. Here is the relevant dmesg details: [ 15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 16.310510] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [ 16.310512] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 16.451397] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input9 [ 16.451451] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input12 [ 16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input13 [ 16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input14 [ 16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input15 Any further information needed, please let me know. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: usr/share/alsa-base/alsa-info.sh] ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: ndiswrapper ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin2018 1246 F pulseaudio CurrentDesktop: GNOME Date: Tue Dec 12 00:46:12 2017 InstallationDate: Installed on 2017-11-22 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all Sour
[Touch-packages] [Bug 1758752] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
*** This bug is a duplicate of bug 1754214 *** https://bugs.launchpad.net/bugs/1754214 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754214, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758752/+attachment/5090510/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758752/+attachment/5090513/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758752/+attachment/5090520/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758752/+attachment/5090522/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758752/+attachment/5090523/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758752/+attachment/5090524/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758752/+attachment/5090525/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1754214 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1758752 Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() Status in systemd package in Ubuntu: New Bug description: migrated home dir to encrypted ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Mar 25 17:04:00 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-03-24 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) MachineType: Dell Inc. Latitude E6410 ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=b4de8a20-c13c-4b42-822c-cd12a2e0c684 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: systemd StacktraceTop: __GI___pthread_timedjoin_ex (threadid=140658219820800, thread_return=0x0, abstime=0x0, block=) at pthread_join_common.c:89 ?? () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/15/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K42JR dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/15/2011:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1758752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757299] Re: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications
gregrwm: 1) Regarding other reports, as mentioned multiple times previously, those are useless. Hence, if you cannot reproduce a crash, then it is most helpful if you remain focused on this report, and providing previously requested information (see below), and other information requested of you in the future. Otherwise, this will never be root caused, fixed, and backported to prior releases as applicable. 2) Regarding the question previously asked of you in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1757299/comments/6: After reproducing the problem, if you SSH in and only kill processes that are not xorg, which processes do you have to kill until your GUI begins to be responsive again? 3) Regarding your Bug Description, at the point where you "maximize the xterm running tmux, and the GUI immediately becomes unresponsive", is there an amount of time that if you wait the GUI eventually become responsive again, and if so, how long precisely? -- 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/1757299 Title: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications Status in xorg package in Ubuntu: Incomplete Bug description: The problem is that after launching a few applications, the GUI may become unresponsive, although this is not consistently reproducible. When the GUI is unresponsive, it is correlated to high CPU utilization of xorg. An example reproduction scenario is launch the following in order, and quickly: startx xterm via twm another xterm via the first xterm tmux firefox-esr bluetooth-manager pavucontrol While the above are launching, maximize the xterm running tmux, and the GUI immediately becomes unresponsive. For example, Ctrl+Alt+Fn don't respond. After this, I logged in via ssh, attached to tmux, launched htop, copied htop output, which shows xorg at 94.6 CPU%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd * Starting AppArmor profiles [160G [154G[ OK ] * Restoring resolver state... [160G [154G[ OK ] CompositorRunning: None Date: Tue Mar 20 17:15:16 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] JournalErrors: -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 CDT. -- Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon already running. MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-x
[Touch-packages] [Bug 1758746] [NEW] Error processing package libc-bin (--configure)
Public bug reported: For any upgrade, install, auto-remove, remove, upgrade ... I get the following error: /usr/lib/x86_64-linux-gnu: Aborted (core dumped) dpkg: error processing package libc-bin (--configure): subprocess installed post-installation script returned error exit status 134 Errors were encountered while processing: libc-bin E: Sub-process /usr/bin/dpkg returned an error code (1) Tried reinstalling libc-bin, but, get the following error after download, extract, copying ldconfig to sbin and installing libc-bin using apt-get: E: Internal Error, No file name for libc-bin:amd64 No updates or upgrades can be done. ** Affects: language-pack-en-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/1758746 Title: Error processing package libc-bin (--configure) Status in language-pack-en-base package in Ubuntu: New Bug description: For any upgrade, install, auto-remove, remove, upgrade ... I get the following error: /usr/lib/x86_64-linux-gnu: Aborted (core dumped) dpkg: error processing package libc-bin (--configure): subprocess installed post-installation script returned error exit status 134 Errors were encountered while processing: libc-bin E: Sub-process /usr/bin/dpkg returned an error code (1) Tried reinstalling libc-bin, but, get the following error after download, extract, copying ldconfig to sbin and installing libc-bin using apt-get: E: Internal Error, No file name for libc-bin:amd64 No updates or upgrades can be done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1758746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758736] [NEW] [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
Public bug reported: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758734] Re: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/1758734 Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory Status in language-pack-en-base package in Ubuntu: New Bug description: error in libc-bin stops update, auto-remove, remove, etc. No packages can be installed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Mar 25 20:24:44 2018 DuplicateSignature: package:language-pack-en-base:1:16.04+20160627 Removing language-pack-en-base (1:16.04+20160627) ... dpkg: error processing package language-pack-en-base (--remove): unable to securely remove '/var/lib/locales/supported.d/en': Not a directory ErrorMessage: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory InstallationDate: Installed on 2015-11-12 (863 days ago) InstallationMedia: /etc/systemd/system/multi-user.target.wants/unattended- PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory UpgradeStatus: Upgraded to xenial on 2016-04-22 (701 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1758734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758734] [NEW] package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory
Public bug reported: error in libc-bin stops update, auto-remove, remove, etc. No packages can be installed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Mar 25 20:24:44 2018 DuplicateSignature: package:language-pack-en-base:1:16.04+20160627 Removing language-pack-en-base (1:16.04+20160627) ... dpkg: error processing package language-pack-en-base (--remove): unable to securely remove '/var/lib/locales/supported.d/en': Not a directory ErrorMessage: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory InstallationDate: Installed on 2015-11-12 (863 days ago) InstallationMedia: /etc/systemd/system/multi-user.target.wants/unattended- PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory UpgradeStatus: Upgraded to xenial on 2016-04-22 (701 days ago) ** Affects: language-pack-en-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/1758734 Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory Status in language-pack-en-base package in Ubuntu: New Bug description: error in libc-bin stops update, auto-remove, remove, etc. No packages can be installed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Mar 25 20:24:44 2018 DuplicateSignature: package:language-pack-en-base:1:16.04+20160627 Removing language-pack-en-base (1:16.04+20160627) ... dpkg: error processing package language-pack-en-base (--remove): unable to securely remove '/var/lib/locales/supported.d/en': Not a directory ErrorMessage: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory InstallationDate: Installed on 2015-11-12 (863 days ago) InstallationMedia: /etc/systemd/system/multi-user.target.wants/unattended- PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: unable to securely remove '/var/lib/locales/supported.d/en': Not a directory UpgradeStatus: Upgraded to xenial on 2016-04-22 (701 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1758734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758619] Re: lxc-update-config incorrectly converts network settings
This has been fixed upstream and in Ubuntu 18.04, marking fix release. If we do a SRU of 2.1.1 for Ubuntu 17.10, this fix will be in it. ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1758619 Title: lxc-update-config incorrectly converts network settings Status in lxc package in Ubuntu: Fix Released Bug description: Before the update, on LXC 2.0.8, I had: lxc.network.type = veth lxc.network.flags = up lxc.network.link = lxcbr0 lxc.network.ipv4 = 10.0.3.205/24 lxc.network.ipv4.gateway = 10.0.3.1 lxc.network.hwaddr = 00:16:3e:ae:79:d7 After the update to LXC 3.0.0beta3, I have: lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = lxcbr0 lxc.net.0.ipv4 = 10.0.3.205/24 lxc.net.0.ipv4.gateway = 10.0.3.1 lxc.net.0.hwaddr = 00:16:3e:ae:79:d7 The conversion is wrong. lxc.network.ipv4 (which was the correct spelling, according to the man page in the old package) should have been converted to lxc.net.0.ipv4.address, not to lxc.net.0.ipv4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc-utils 3.0.0~beta3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Mar 25 14:24:16 2018 InstallationDate: Installed on 2018-01-25 (58 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180120) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758725] [NEW] network-manager applet up/down arrows when connected to wifi only
Public bug reported: I have an issue with the network-manager applet that shows up and down arrows (wired connection?) when connected to wifi only. I still have internet connectivity, but unable to choose a wifi network. The computer: Toshiba Satellite L55W-C5320. The OS: Ubuntu 16.04.4. Thank you, Pavel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 25 11:27:15 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-25 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH shrek4 1 a8c323eb-6312-4287-924a-ce4567222530 802-11-wireless 1522002319 Sun 25 Mar 2018 11:25:19 AM PDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 shrek4 1a8c323eb-6312-4287-924a-ce4567222530 /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1758725 Title: network-manager applet up/down arrows when connected to wifi only Status in network-manager package in Ubuntu: New Bug description: I have an issue with the network-manager applet that shows up and down arrows (wired connection?) when connected to wifi only. I still have internet connectivity, but unable to choose a wifi network. The computer: Toshiba Satellite L55W-C5320. The OS: Ubuntu 16.04.4. Thank you, Pavel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 25 11:27:15 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-25 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH shrek4 1 a8c323eb-6312-4287-924a-ce4567222530 802-11-wireless 1522002319 Sun 25 Mar 2018 11:25:19 AM PDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes w
[Touch-packages] [Bug 1758721] [NEW] Screen corruption after suspend
Public bug reported: I consistently get screen corruption after a suspend in the wake-up screen (the one with the arrows you drag) and login screen. Sometimes I have trouble dragging the wake-up screen to get the login screen. Sometimes I am able to get the login screen (although all text is corrupted) and login back into my session. After login screen corruption is inconsistent, at times the whole session is corrupted (see attachment), sometimes only text is corrupted (icons, desktop is okay) and sometimes there is no corruption. One workaround that seems to avoid the situation is to disable all automatic suspend options in the power settings. Note that I have recently upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 19:18:25 2018 DistUpgraded: 2018-03-25 11:25:40,806 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218M [NVS 3100M] [103c:172b] InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=a16d7c26-68e8-4cec-bcdc-c814a96b448d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.22 dmi.board.name: 172B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.33 dmi.chassis.asset.tag: CZC02417F8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.22:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.33:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 23 14:06:10 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption has-workaround reproducible ubuntu ** Attachment added: "TotalScreenCorruptionAfterLogin" https://bugs.launchpad.net/bugs/1758721/+attachment/5090305/+files/Screenshot%20from%202018-03-25%2014-18-58.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1758721 Title: Screen corruption after suspend Status in xorg package in Ubuntu: New Bug description: I consistently get screen corruption after a suspend in the wake-up screen (the one with the arrows you drag) and login screen. Sometimes I have trouble dragging the wake-up screen to get the login screen. Sometimes I am able to get the login screen (although all text is corrupted) and login back into my session. After login screen corruption is inconsistent, at times the whole session is corrupted (see attachment), sometimes only text is corrupted (icons, desktop is okay) and sometimes there is no corruption. One workaround that seems to avoid the situation is to disable all automatic suspend options in the power settings. Note that I have recently upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Compi
[Touch-packages] [Bug 1758720] [NEW] not able to open, adapt size and position of application windows
Public bug reported: windows of applications cannot be adapted to screen size or closed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Mar 25 19:56:24 2018 DistUpgraded: 2016-05-01 09:53:49,322 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:5105] InstallationDate: Installed on 2013-10-19 (1617 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 33597FG ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=523d7466-d561-4cde-8664-11fab034ade1 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-05-01 (693 days ago) dmi.bios.date: 12/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: HMET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 33597FG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHMET90WW(2.50):bd12/26/2012:svnLENOVO:pn33597FG:pvrThinkPadEdgeE135:rvnLENOVO:rn33597FG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33597FG dmi.product.version: ThinkPad Edge E135 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 25 19:37:11 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1758720 Title: not able to open, adapt size and position of application windows Status in xorg package in Ubuntu: New Bug description: windows of applications cannot be adapted to screen size or closed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Mar 25 19:56:24 2018 DistUpgraded: 2016-05-01 09:53:49,322 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:5105] InstallationDate: Installed on 2013-10-19 (1617 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 33597FG ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=523d7466-d561-4cde-8664-11fab034ade1 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-05-01 (693 days ago) dmi.bios.date: 12/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: HMET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 33597FG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHMET90WW(
[Touch-packages] [Bug 1752928] Re: [FFe] GNOME 3.28
** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => Fix Released ** Description changed: Feature Freeze Justification Evolution was delayed to not intertangle transitions. gnome-shell was released late upstream. gnome-control-center & gnome-shell were waiting for a subject matter expert to return from holiday. Shotwell got overlooked but plans to release at the same time as GNOME. GNOME prefers us to not mix and match components from different versions as much as possible. GNOME 3.28.0 release is just over a week away Affected Packages - DONE: evolution transition LP: #1752578 DONE: gnome-shell and mutter LP: #1751070 DONE: shotwell DONE: gnome-settings-daemon LP: #1750174 DONE: gnome-session - gnome-control-center LP: #1750174 + DONE: gnome-control-center LP: #1750174 - gnome-games, retro-gtk & libmanette (libmanette released yesterday with - updated library name, waiting on new retro-gtk release expected any day) + DONE: gnome-games, retro-gtk & libmanette (libmanette released yesterday + with updated library name, waiting on new retro-gtk release expected any + day) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1752928 Title: [FFe] GNOME 3.28 Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Feature Freeze Justification Evolution was delayed to not intertangle transitions. gnome-shell was released late upstream. gnome-control-center & gnome-shell were waiting for a subject matter expert to return from holiday. Shotwell got overlooked but plans to release at the same time as GNOME. GNOME prefers us to not mix and match components from different versions as much as possible. GNOME 3.28.0 release is just over a week away Affected Packages - DONE: evolution transition LP: #1752578 DONE: gnome-shell and mutter LP: #1751070 DONE: shotwell DONE: gnome-settings-daemon LP: #1750174 DONE: gnome-session DONE: gnome-control-center LP: #1750174 DONE: gnome-games, retro-gtk & libmanette (libmanette released yesterday with updated library name, waiting on new retro-gtk release expected any day) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1752928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758712] Re: GNOME Builder Omnibar theming issue with Ambiance
** Attachment added: "gnome-builder-ambiance-20180325.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758712/+attachment/5090252/+files/gnome-builder-ambiance-20180325.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1758712 Title: GNOME Builder Omnibar theming issue with Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: Ubuntu 18.04 GNOME Builder 3.28.0 (from the GNOME3 Staging PPA, will be uploaded directly to 18.04 soon) In the center of the headerbar is a widget the GNOME Builder documentation calls the Omnibar. In the Adwaita screenshot, it has a pale green background showing that the build has completed successfully. In the Ambiance screenshot, the Omnibar is unreadable because it's basically dark grey text on dark grey background with only minimal contrast. (Note there is a screenshot problem because of a mutter bug. Ambiance should have orange highlights and Adwaita should be blue, but it's basically reversed! The screenshot bug doesn't really affect this theming bug). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758712] Re: GNOME Builder Omnibar theming issue with Ambiance
** Attachment added: "gnome-builder-adwaita-20180325.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758712/+attachment/5090251/+files/gnome-builder-adwaita-20180325.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1758712 Title: GNOME Builder Omnibar theming issue with Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: Ubuntu 18.04 GNOME Builder 3.28.0 (from the GNOME3 Staging PPA, will be uploaded directly to 18.04 soon) In the center of the headerbar is a widget the GNOME Builder documentation calls the Omnibar. In the Adwaita screenshot, it has a pale green background showing that the build has completed successfully. In the Ambiance screenshot, the Omnibar is unreadable because it's basically dark grey text on dark grey background with only minimal contrast. (Note there is a screenshot problem because of a mutter bug. Ambiance should have orange highlights and Adwaita should be blue, but it's basically reversed! The screenshot bug doesn't really affect this theming bug). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758713] [NEW] system
Public bug reported: Ubuntu 16.04 LTS system bugs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 25 19:33:39 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: microdia, 2009.01: added v4l2loopback, 0.9.1, 4.13.0-36-generic, i686: installed v4l2loopback, 0.9.1, 4.13.0-37-generic, i686: installed virtualbox, 5.0.40, 4.13.0-36-generic, i686: installed virtualbox, 5.0.40, 4.13.0-37-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 1100/1150] [1458:d000] InstallationDate: Installed on 2018-02-28 (24 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) JournalErrors: -- Logs begin at v 2018-03-25 19:03:19 CEST, end at v 2018-03-25 19:34:01 CEST. -- márc 25 19:28:46 hostname com.canonical.Unity.Scope.Applications[1847]: Error loading package indexes: Couldn't stat '/var/cache/software-center/xapian' márc 25 19:28:46 hostname com.canonical.Unity.Scope.Applications[1847]: (unity-scope-loader:5431): unity-applications-daemon-CRITICAL **: daemon.vala:144: Failed to load Software Center index. 'Apps Available for Download' will not be listed MachineType: FUJITSU SIEMENS GA-K8RS482M ProcEnviron: LANGUAGE=hu PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2005 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: GA-K8RS482M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/27/2005:svnFUJITSUSIEMENS:pnGA-K8RS482M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8RS482M:rvrx.x:cvn:ct3:cvr: dmi.product.name: GA-K8RS482M dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Mar 25 17:47:59 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSIGMACHIP Usb Mouse MOUSE, id 8 inputHID 1267:0103KEYBOARD, id 9 inputHID 1267:0103KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1758713 Title: system Status in xorg package in Ubuntu: New Bug description: Ubuntu 16.04 LTS system bugs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 25 19:33:39 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: microdia, 2009.01: added v4l2loopback, 0.9.1, 4.13.0-36-generic, i686: installed v4l2loopback, 0.9.1, 4.13.0-37-generic, i686: installed virtualbox, 5.0.40, 4.13.0-36-generic, i686: installed virtualbox, 5.0.40, 4.13.0-37-generic, i686: installed ExtraDe
[Touch-packages] [Bug 1758712] [NEW] GNOME Builder Omnibar theming issue with Ambiance
Public bug reported: Ubuntu 18.04 GNOME Builder 3.28.0 (from the GNOME3 Staging PPA, will be uploaded directly to 18.04 soon) In the center of the headerbar is a widget the GNOME Builder documentation calls the Omnibar. In the Adwaita screenshot, it has a pale green background showing that the build has completed successfully. In the Ambiance screenshot, the Omnibar is unreadable because it's basically dark grey text on dark grey background with only minimal contrast. (Note there is a screenshot problem because of a mutter bug. Ambiance should have orange highlights and Adwaita should be blue, but it's basically reversed! The screenshot bug doesn't really affect this theming bug). ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: bionic rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1758712 Title: GNOME Builder Omnibar theming issue with Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: Ubuntu 18.04 GNOME Builder 3.28.0 (from the GNOME3 Staging PPA, will be uploaded directly to 18.04 soon) In the center of the headerbar is a widget the GNOME Builder documentation calls the Omnibar. In the Adwaita screenshot, it has a pale green background showing that the build has completed successfully. In the Ambiance screenshot, the Omnibar is unreadable because it's basically dark grey text on dark grey background with only minimal contrast. (Note there is a screenshot problem because of a mutter bug. Ambiance should have orange highlights and Adwaita should be blue, but it's basically reversed! The screenshot bug doesn't really affect this theming bug). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)
** Changed in: mesa Status: Unknown => Fix Released ** Changed in: mesa Importance: Unknown => Medium -- 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/1753776 Title: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only) Status in Mesa: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in wayland package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Invalid Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Invalid Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:
[Touch-packages] [Bug 1687353] Re: System freezes due to ALSA error and recovers after significant time
This was corrected and is no longer happening to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: Confirmed Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1687353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758700] [NEW] Internal display not working
Public bug reported: My internal display is not working. The internal display works at boot and goes black during ubuntu boot. I am able to use the hdmi monitor but i need my internal screen to work. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 09:35:30 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] InstallationDate: Installed on 2018-02-18 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=cd069400-aa78-43dd-9434-6d260f2c78f1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.06.00 dmi.board.name: 0K99NX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0K99NX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91+git1803221830.bb45ce~oibaf~a version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803241930.d60eaf~oibaf~a version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1803241930.d60eaf~oibaf~a version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1+git1803151933.fdba53~oibaf~a version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1803021934.aa3639~oibaf~a version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1803090733.ac8f7b~oibaf~a ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1758700 Title: Internal display not working Status in xorg package in Ubuntu: New Bug description: My internal display is not working. The internal display works at boot and goes black during ubuntu boot. I am able to use the hdmi monitor but i need my internal screen to work. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 09:35:30 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] InstallationDate: Installed on 2018-02-18 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=cd069400-aa78-43dd-9434-6d260f2c78f1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.06.00 dmi.board.name: 0K99NX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0K99NX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91+git1803221830.bb45ce~oibaf~a version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803241930.d60eaf~oibaf~a version.l
[Touch-packages] [Bug 1758695] Re: apport-gtk crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1756469 *** https://bugs.launchpad.net/bugs/1756469 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1756469, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758695/+attachment/5090152/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758695/+attachment/5090155/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758695/+attachment/5090159/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758695/+attachment/5090160/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758695/+attachment/5090161/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758695/+attachment/5090162/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758695/+attachment/5090163/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1756469 ** Information type changed from Private Security to Public Security ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1758695 Title: apport-gtk crashed with SIGABRT in g_assertion_message() Status in apport package in Ubuntu: New Bug description: Fix please ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.8-0ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 18:55:36 2018 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-02-10 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 Signal: 6 SourcePackage: apport StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_error () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to bionic on 2018-03-17 (8 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1758695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error
** Changed in: ktp-accounts-kcm (Ubuntu) Assignee: (unassigned) => vaibhav singh (rockey1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1451728 Title: [master] kde-config-telepathy-accounts package install error Status in Kubuntu PPA: Fix Released Status in Telepathy KDE: Fix Released Status in kaccounts-integration package in Ubuntu: Fix Committed Status in kaccounts-providers package in Ubuntu: Fix Committed Status in ktp-accounts-kcm package in Ubuntu: Triaged Status in libaccounts-glib package in Ubuntu: Fix Released Status in kaccounts-providers source package in Wily: Triaged Status in ktp-accounts-kcm source package in Wily: Triaged Bug description: Installing from Kubuntu 15.04 backports: Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/facebook-im.service', which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) SRU information === [Impact] It's not possible to install KDE and Unity in co-existence because of several file conflicts: many files under /usr/share/accounts/{providers,services}/ are provided by both the package "kaccounts-providers" and packages build from the "account- plugins" source package, for example 'account-plugin-facebook'. [Test case] Install both kaccounts-providers and account-plugin-facebook: you'll get file conflicts for /usr/share/accounts/services/facebook-im.service and /usr/share/accounts/providers/facebook.provider. You might get other conflicts as well, but those are due to bug 1565772 (also nominated for SRU). [Regression potential] Minimal: the changed packages belong to the default KDE installation, and have already landed in Yakkety. Things appear to be working fine there: account creation is still possible under KDE, even after changing the file paths as per this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
I have found a solution that at least worked for me. I do not claim that this is the absolute end-solution for this problem and it would like Timo to have a look on it to confirm that this is the way to go. As I mentioned above is the guest user working without any problems. What differs between my not working user and the guest user might cause the problem. So I started comparing and found that ~/.cache/compizconfig-1/core.pb is only 82 bytes while the same file for guest contains 4237 bytes. My original core.pb is nearly empty. What I did was the following: - first make a backup of ~/.cache/compizconfig-1/core.pb You can now always revert the change - su root - copy core.pb to your own home dir to ~/.cache/compizconfig-1/core.pb - chmod the file to your user - reboot All went working again. I can use the unity launcher again. Perfect! It is clear to me that is not the entire solution. The file might have been corrupted by an update and might be corrupted again. So the fix needs to correct the damaging part and also load the correct config. At least I have found a temporary solution and I'm very happy with it because I can use my computer again. I was forced to use Windows and that was no fun. Cheers, Mark -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Released Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758665] [NEW] Automatic Wi-Fi login failure on user session startup
Public bug reported: network-manager seems to fail to automatically login into home Wi-Fi network (with WPA2 Security) on user session start (it shows the Wi-Fi symbol with a question mark). Going to Wi-Fi settings and clicking on the settings button for the network seems to solve the problem, without needing to actually change anything. Note that I just upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 14:42:13 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.34 metric 600 192.168.123.0/24 dev virbr0 proto kernel scope link src 192.168.123.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: network-manager seems to fail to automatically login into home Wi-Fi network (with WPA2 Security) on user session start (it shows the Wi-Fi symbol with a question mark). Going to Wi-Fi settings and clicking on the settings button for the network seems to solve the problem, without needing to actually change anything. Note that I just upgraded from 16.04 LTS to 18.04 LTS Beta (1?). - - First time reporting a ubuntu bug, used the recommend tool with this - command "ubuntu-bug network-manager", hope that appends all the - necessary info, if not let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 14:42:13 2018 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: - default via 192.168.1.1 dev wlo1 proto dhcp metric 600 - 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown - 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.34 metric 600 - 192.168.123.0/24 dev virbr0 proto kernel scope link src 192.168.123.1 linkdown + default via 192.168.1.1 dev wlo1 proto dhcp metric 600 + 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown + 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.34 metric 600 + 192.168.123.0/24 dev virbr0 proto kernel scope link src 192.168.123.1 linkdown NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.10.4 connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.10.4 connected started full enabled enabled enabled enabled enabled -- 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/1758665 Title: Automatic Wi-Fi login failure on user session startup Status in network-manager package in Ubuntu: New Bug description: network-manager seems to fail to automatically login into home Wi-Fi network (with WPA2 Security) on user session start (it shows the Wi-Fi symbol with a question mark). Going to Wi-Fi settings and clicking on the settings button for the network seems to solve the problem, without needing to actually change anything. Note that I just upgraded from 16.04 LTS to 18.04 LTS Beta (1?)
[Touch-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
My network consists of: 2: enp8s0: mtu 1500 qdisc mq state UP group default qlen 1000 inet 10.1.1.1/24 brd 10.1.1.255 scope global enp8s0 3: wlp4s0: mtu 1500 qdisc mq state UP group default qlen 1000 inet 192.168.99.2/24 brd 192.168.99.255 scope global wlp4s0 5: ppp0: mtu 1484 qdisc pfifo_fast state UNKNOWN group default qlen 3 inet 220.132.100.42 peer 168.95.98.254/32 scope global ppp0 and it seems all work ok except the service networking status keep showing: Active: failed (Result: exit-code) since Sun 2018-03-25 20:47:42 CST; 53min ago Docs: man:interfaces(5) Process: 953 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Process: 859 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" Main PID: 953 (code=exited, status=1/FAILURE) cant find a fix and lead to also see in service NetworkManager status: NetworkManager[933]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed but the point is the network function normally, are these two issues related and what's the cause ? -- 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/1568560 Title: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3 My WiFi connection is very unstable and I have to often restart NetworkManager service (~ a dozen times every day...): sudo systemctl -l status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago Main PID: 27832 (NetworkManager) Memory: 13.8M CPU: 1.729s CGroup: /system.slice/NetworkManager.service ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d ├─27832 /usr/sbin/NetworkManager --no-daemon └─30448 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: keyfile: add connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0") avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): new Tun device (carrier: OFF, driver: 'tun', ifindex: 34) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1): bridge port virbr1-nic was attached avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): enslaved to virbr1 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Also, each time I restart my desktop, NetworkManager generates a crash report: cf. attached screenshots. I have tried an Ubuntu VM with the same packages related to networking and the exact same releases (same repositories), the crash never happens; the difference appears to be only the type of network connection: WiFi for the desktop vs Ethernet for the VM. Any suggestion? To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1568560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
This is an amazing bug trail! A lot has been done and @Timo, thanks for the work so far. I have an update that might help. I have 2 laptops, a ASUS and a Lenovo. They both had the issue. I did a reinstall of Ubuntu 16.04 on the Lenovo keeping the home folder. First I had the "no launcher problem" again but after update and reboot it suddenly worked. The the ASUS laptop got the same issue. I have now 2 laptops one working and one not, with the same software but apparently different settings. I saw the status being set to "Fix released" and assumed that just update+upgrade would bring in the fix. My versions are on both computers: $uname -a 4.4.0-116-generic $apt policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 17.2.8-0ubuntu0~16.04.1 Candidate: 17.2.8-0ubuntu0~16.04.1 $apt policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.4-0ubuntu0.7 Candidate: 2:1.18.4-0ubuntu0.7 The not working laptop (ASUS) was switched from the NVIDIA driver to the X.org X server just before the trouble started. There is an odd way of bypassing this bug: Go to the background image and right click and select: "Change Desktop image" You don't want to do this but select: "All Settings". Select: "User accounts". Create a new user. In my case the guest user. (standard, non admin) At least in my case I can use the newly created user WITHOUT ANY PROBLEMS. The newly created user can see and use the launcher. In this way I can at least use the computer. At least it is a temporary fix. The I started looking for differences between my normal user and the new guest user. It is possible to ctrl-alt to a different tty and log in as a different user. Some config must different and make sense but hard to compare and I do not know where to look. So far I only found that the .Xauthority file of both is different. The have the MIT-MAGIC-COOKIE setting with different settings. Removing the .Xauthority file will have the file recreated but does not help in fixing the problem. Please let me know how I can compare both users and where to look. -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Released Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758655] [NEW] [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all
Public bug reported: like bug https://bugs.launchpad.net/bugs/855567 But with Ubuntu 16.04.3 LTS 64 bit Kernel: 4.13.0-37-generic AMD FX(tm)-6350 Six-Core Processor × 6 GeForce GT 730/PCIe/SSE2 16 GB RAM pulseaudio is used. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bern 5504 F pulseaudio /dev/snd/pcmC1D7p: bern 5504 F...m pulseaudio /dev/snd/controlC1: bern 5504 F pulseaudio /dev/snd/controlC0: bern 5504 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 25 13:37:09 2018 InstallationDate: Installed on 2017-08-13 (224 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U0xccd0x77 failed Symptom_Card: Aureon Dual USB - USB Device 0xccd:0x77 Symptom_Type: No sound at all Title: [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1758655 Title: [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: like bug https://bugs.launchpad.net/bugs/855567 But with Ubuntu 16.04.3 LTS 64 bit Kernel: 4.13.0-37-generic AMD FX(tm)-6350 Six-Core Processor × 6 GeForce GT 730/PCIe/SSE2 16 GB RAM pulseaudio is used. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bern 5504 F pulseaudio /dev/snd/pcmC1D7p: bern 5504 F...m pulseaudio /dev/snd/controlC1: bern 5504 F pulseaudio /dev/snd/controlC0: bern 5504 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 25 13:37:09 2018 InstallationDate: Installed on 2017-08-13 (224 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U0xccd0x77 failed Symptom_Card: Aureon Dual USB - USB Device 0xccd:0x77 Symptom_Type: No sound at all Title: [USB-Audio - USB Device 0xccd:0x77, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1758655/+subscriptions -- Mailing list: https://launchpad.net
[Touch-packages] [Bug 1441253] Re: hanging suspend job prevents shutdown
Hello. I'm having the same problems with shutdown. Yesterday, I've choosed "menu/logout/halt" option instead of "menu/logout/shutdown". And problems started to happen: I could not even reboot or shutdown computer, because every time when I wanted to do this, there was a window to unblock session (I have had to enter my user password and there was not even internet connection - it could not be connected via NetworkManager! etc.) For now, a solution is: press "RESET" and next "POWER" button for a few seconds. That's the only way to shutdown computer now. I've decided to try shutdown system via shutdown(8) command but it did not work: [~]$ shutdown now Failed to power off system via logind: There's already a shutdown or sleep operation in progress [~]$ systemctl list-jobs No jobs running. Anyway, there is not LightDM now! I have to login via "unblock" window mentioned above. And when I want to edit e.g. 'rtkit-daemon.service' file via 'mousepad', there is a WARNING message (** (mousepad:2869): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*: Connection refused). It happens with every file, that I want to edit etc. Log files contains many entries related to the 'rtkit-daemon' (please see 1.) But this is not important here. I apologize for such a comment, but shutdown issues, started to happen after described situation. I have no idea if it's important, but it started to happen when I choosed - by accident - 'halt' option instead of 'shutdown' during logout. ● Release: 16.04.4 LTS ● Xfce: 4.12 (according to 'xfce4-about' command) Thanks, best regads. 1. https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1547589 (comment #3) -- 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/1441253 Title: hanging suspend job prevents shutdown Status in systemd package in Ubuntu: Won't Fix Bug description: poweroff (systemd poweroff) and reboot no longer work running sudo sytemd poweroff generates this: Failed to start poweroff.target: Transaction is destructive. journal log also shows: Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Output of systemctl list-jobs JOB UNITTYPE STATE 6009 suspend.target start waiting 6010 systemd-suspend.service start running 6014 anacron-resume.service start waiting ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Tue Apr 7 18:32:27 2015 MachineType: Hewlett-Packard HP EliteBook 8560w ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@ SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog
Hello. I'm having the same problem with 'rtkit' and log files flooding. Yesterday, I've choosed "menu/logout/halt" option instead of "menu/logout/shutdown". And problems started to happen: I could not even reboot or shutdown computer, because every time when I wanted to do this, there was a window to unblock session (I have had to enter my user password and there was not even internet connection - it could not be connected via NetworkManager! etc.) The only one working solution to shutdown computer was: press "RESET" and next "POWER" buttons. I've decided to try shutdown system via shutdown(8) command but it did not work: [~]$ shutdown now Failed to power off system via logind: There's already a shutdown or sleep operation in progress Anyway, there is not LightDM now! I have to login via "unblock" window mentioned above. And when I want to edit e.g. 'rtkit-daemon.service' file via 'mousepad', there is a WARNING message (** (mousepad:2869): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*: Connection refused). It happens with every file, that I want to edit etc. But this is not important here. Log files contains many entries related to the 'rtkit-daemon'. For example: ✗✗ rtkit-daemon[1383]: Supervising 0 threads of 0 processes of 1 users. ✗✗ rtkit-daemon[1383]: Failed to look up client: No such file or directory ✗✗ rtkit-daemon[1364]: message repeated 10 times: [ Failed to look up client: No such file or directory] There is about 30. such entries in '/var/log/syslog/' file etc. Anyway, here are informations gathered via systemd's systemctl(1) command: [~]$ systemctl status rtkit-daemon.service ● rtkit-daemon.service - RealtimeKit Scheduling Policy Service Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled; vendor preset: enabled) Active: active (running) since sun 2018-03-25 11:44:47 CEST; 1h 26min ago Main PID: 1383 CGroup: /system.slice/rtkit-daemon.service └─1383 n/a mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No such file or directory I apologize for such a long comment, but 'rtkit' issues, started to happen after described situation. I have no idea if it's important, but it started to happen when I choosed - by accident - 'halt' option instead of 'shutdown' during logout. ● Release: 16.04.4 LTS ● rtkit: 0.11-4 Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1547589 Title: rtkit-daemon flooding syslog Status in rtkit package in Ubuntu: Confirmed Bug description: rtkit is flooding syslog with the following: Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000
[Touch-packages] [Bug 1751261] Re: libgweather-locations.pot generation fails with bionic meson
** Changed in: gettext (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1751261 Title: libgweather-locations.pot generation fails with bionic meson Status in libgweather: Unknown Status in Ubuntu Translations: Fix Released Status in gettext package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gettext package in Debian: Fix Released Bug description: From bionic: Change to the libgweather source directory and run sudo apt build-dep libgweather dh_auto_configure dh_auto_build ninja -v -C obj-x86_64-linux-gnu/ libgweather-3.0-pot ninja -v -C obj-x86_64-linux-gnu/ libgweather-locations-pot For reference, the second to last command succeeds with this output: --- ninja -v -C obj-x86_64-linux-gnu/ libgweather-3.0-pot ninja: Entering directory `obj-x86_64-linux-gnu/' [0/1] /usr/bin/python3 /usr/bin/meson --internal commandrunner /home/jeremy/devel/libgweather /home/jeremy/devel/libgweather/obj-x86_64-linux-gnu po /usr/bin/python3 /usr/bin/meson /usr/bin/python3 /usr/bin/meson --internal gettext pot --pkgname=libgweather-3.0 --extra-args=--keyword=_@@--add-comments@@--flag=g_set_error:4:c-format@@--flag=N_:1:pass-c-format@@--flag=g_dngettext:2:pass-c-format@@--keyword=NC_:1c,2@@--flag=g_error_new:3:c-format@@--from-code=UTF-8@@--keyword=g_dpgettext2:2c,3@@--keyword=C_:1c,2@@--keyword=g_dngettext:2,3@@--keyword=N_@@--flag=g_string_printf:2:c-format@@--flag=g_string_append_printf:2:c-format@@--flag=C_:2:pass-c-format@@--keyword=g_dcgettext:2@@--flag=NC_:2:pass-c-format@@--flag=g_strdup_printf:1:c-format The last command fails with this output: --- ninja: Entering directory `obj-x86_64-linux-gnu/' [0/1] /usr/bin/python3 /usr/bin/meson --internal commandrunner /home/jeremy/devel/libgweather /home/jeremy/devel/libgweather/obj-x86_64-linux-gnu po-locations /usr/bin/python3 /usr/bin/meson /usr/bin/python3 /usr/bin/meson --internal gettext pot --pkgname=libgweather-locations --extra-args=--its@@/home/jeremy/devel/libgweather/po-locations/../data/locations.its FAILED: meson-libgweather-locations-pot /usr/bin/python3 /usr/bin/meson --internal commandrunner /home/jeremy/devel/libgweather /home/jeremy/devel/libgweather/obj-x86_64-linux-gnu po-locations /usr/bin/python3 /usr/bin/meson /usr/bin/python3 /usr/bin/meson --internal gettext pot --pkgname=libgweather-locations --extra-args=--its@@/home/jeremy/devel/libgweather/po-locations/../data/locations.its ninja: build stopped: subcommand failed. To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1751261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758644] [NEW] [System Product Name, Realtek ALC1150, Green Headphone Out, Front] Playback problem
Public bug reported: Initially Front audio port was in mute and I installed ALSA Mixer and Unmuted it. Then I'm able to hear background noise and whatever I speak in the front mic. But I'm not able to hear any other sound played using Movie player or Rythmbox. Then I ran "ubuntu-bug -s audio" application. It tried playing beep tone two times. First time I could hear it but second time I couldn't. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: selvariyan 1962 F pulseaudio /dev/snd/controlC1: selvariyan 1962 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 25 16:11:05 2018 InstallationDate: Installed on 2016-08-06 (595 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Only some of outputs are working Title: [System Product Name, Realtek ALC1150, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3501 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3501:bd06/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1758644 Title: [System Product Name, Realtek ALC1150, Green Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Initially Front audio port was in mute and I installed ALSA Mixer and Unmuted it. Then I'm able to hear background noise and whatever I speak in the front mic. But I'm not able to hear any other sound played using Movie player or Rythmbox. Then I ran "ubuntu-bug -s audio" application. It tried playing beep tone two times. First time I could hear it but second time I couldn't. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: selvariyan 1962 F pulseaudio /dev/snd/controlC1: selvariyan 1962 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 25 16:11:05 2018 InstallationDate: Installed on 2016-08-06 (595 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Only some of outputs are working Title: [System Product Name, Realtek ALC1150, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3501 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3501:bd06/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To man
[Touch-packages] [Bug 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*
Hello. I'm having the same problem with mousepad. Yesterday, I've choosed "menu/logout/halt" option instead of "menu/logout/shutdown". And problems started to happen: I could not even reboot or shutdown computer, because every time when I wanted to do this, there was a window to unblock session (I have had to enter my user password and there was not internet connection - it could not be connected via NetworkManager! etc.) The only one working solution to shutdown computer was: press "RESET" and next "POWER" buttons. I've decided to try shytdown system via shutdown(8) command but it did not work: [~]$ shutdown now Failed to power off system via logind: There's already a shutdown or sleep operation in progress Anyway, there is not LightDM now! I have to login via "unblock" window mentioned above. And when I want to edit some file, there is a WARNING message: [~]$ mousepad /lib/systemd/system/rtkit-daemon.service ** (mousepad:2869): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*: Connection refused It happens with every file, that I want to edit etc. Log files contains many entries related to the 'rtkit-daemon'. For example: rtkit-daemon[1383]: Supervising 0 threads of 0 processes of 1 users. rtkit-daemon[1383]: Failed to look up client: No such file or directory I apologize for such a long comment, but mousepad issues, started to happen after described situation. I have no idea if it's important, but it started to happen when I choosed - by accident - 'halt' option instead of 'shutdown' during logout. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1617630 Title: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -* Status in at-spi2-core package in Ubuntu: Confirmed Bug description: When I start mousepad in a terminal, I have this warning : ** (mousepad:25021): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion refusée When I start it with GKSU, the warning is not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*
Geez, I forgot to write an informations about system version etc. So: ● Release: 16.04 LTS ● Xfce: 4.12.1-3ubuntu1 ● Mousepad: 0.4.0-3ubuntu1 Thanks, best regards. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1617630 Title: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -* Status in at-spi2-core package in Ubuntu: Confirmed Bug description: When I start mousepad in a terminal, I have this warning : ** (mousepad:25021): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion refusée When I start it with GKSU, the warning is not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1679117] Re: avahi-daemon crashed with SIGABRT in avahi_malloc()
*** This bug is a duplicate of bug 1668559 *** https://bugs.launchpad.net/bugs/1668559 ** Also affects: avahi Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1679117 Title: avahi-daemon crashed with SIGABRT in avahi_malloc() Status in Avahi: New Status in avahi package in Ubuntu: Confirmed Bug description: The problem started with Ubuntu 16.10 and is still here after the upgrade to 17.04. A warning message displays several times a day. I click submit or cancel and nothing seems to happen. No other problems but the message. Everything seems to work properly. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Mon Apr 3 12:26:42 2017 ExecutablePath: /usr/sbin/avahi-daemon InstallationDate: Installed on 2014-04-14 (1084 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413) ProcCmdline: avahi-daemon:\ running\ [hostname.local] ProcEnviron: Signal: 6 SourcePackage: avahi StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 avahi_malloc () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 avahi_prio_queue_put () from /usr/lib/x86_64-linux-gnu/libavahi-core.so.7 avahi_time_event_new () from /usr/lib/x86_64-linux-gnu/libavahi-core.so.7 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-core.so.7 Title: avahi-daemon crashed with SIGABRT in avahi_malloc() UpgradeStatus: Upgraded to zesty on 2017-04-03 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1679117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp