[Touch-packages] [Bug 1740653] Re: sudo crashed with SIGABRT in kill() when sudoing clinfo
*** This bug is a duplicate of bug 1565332 *** https://bugs.launchpad.net/bugs/1565332 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 #1565332, 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/1740653/+attachment/5029330/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1740653/+attachment/5029332/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1740653/+attachment/5029336/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1740653/+attachment/5029337/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1740653/+attachment/5029338/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1740653/+attachment/5029339/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1740653/+attachment/5029341/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1565332 sudo crashed with SIGABRT in kill() ** 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 sudo in Ubuntu. https://bugs.launchpad.net/bugs/1740653 Title: sudo crashed with SIGABRT in kill() when sudoing clinfo Status in sudo package in Ubuntu: New Bug description: My clinfo is erroring: ~$ clinfo terminate called after throwing an instance of 'cl::Error' what(): clGetPlatformIDs Aborted (core dumped) I tried again as ~$sudo clinfo: Got gui errors (one of which crashed sudo) Description: Ubuntu 16.04.3 LTS Release: 16.04 I expected to get the core dump somehow if I used sudo, since sudo brings up the gui. Maybe I'm off base there. apt-cache policy clinfo clinfo: Installed: (none) Candidate: 2.1.16.01.12-1 Version table: 2.1.16.01.12-1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages apt-cache policy sudo sudo: Installed: 1.8.16-0ubuntu1.5 Candidate: 1.8.16-0ubuntu1.5 Version table: *** 1.8.16-0ubuntu1.5 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.8.16-0ubuntu1.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.8.16-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.5 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Dec 31 00:01:59 2017 ExecutablePath: /usr/bin/sudo InstallationDate: Installed on 2017-12-30 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcCmdline: sudo clinfo Signal: 6 SourcePackage: sudo StacktraceTop: kill () at ../sysdeps/unix/syscall-template.S:84 ?? () __libc_start_main (main=0x558548bbfa50, argc=2, argv=0x7fffde4df418, init=, fini=, rtld_fini=, stack_end=0x7fffde4df408) at ../csu/libc-start.c:291 ?? () Title: sudo crashed with SIGABRT in kill() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1740653/+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 1726981] Re: nautilus crashed with SIGSEGV
[Expired for tracker (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tracker (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1726981 Title: nautilus crashed with SIGSEGV Status in tracker package in Ubuntu: Expired Bug description: ... ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 17:20:03 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f8107aaad34:mov(%rsi),%ebp PC (0x7f8107aaad34) ok source "(%rsi)" (0x40) not located in a known VMA region (needed readable region)! destination "%ebp" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 Title: nautilus crashed with SIGSEGV 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/tracker/+bug/1726981/+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 1728784] Re: package libk5crypto3:amd64 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package libk5crypto3:amd64 is not ready for configuration cannot configure (current status
[Expired for krb5 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: krb5 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1728784 Title: package libk5crypto3:amd64 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package libk5crypto3:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in krb5 package in Ubuntu: Expired Bug description: I got this problem while updating my system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libk5crypto3:amd64 1.13.2+dfsg-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Oct 31 08:06:32 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 libkrb5support0 1.13.2+dfsg-5ubuntu2 DuplicateSignature: package:libk5crypto3:amd64:1.13.2+dfsg-5ubuntu2 Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package libk5crypto3:amd64 (--configure): package libk5crypto3:amd64 is not ready for configuration ErrorMessage: package libk5crypto3:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-10-28 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: krb5 Title: package libk5crypto3:amd64 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package libk5crypto3:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1728784/+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 1740635] Re: Correct screen resolution not available on Ubuntu 17.10
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1740635 Title: Correct screen resolution not available on Ubuntu 17.10 Status in xorg package in Ubuntu: New Bug description: I did a fresh installation of Ubuntu 17.10 on my Dell Precision M2800. I use two external displays (both Dell U2715Hc) with a screen resolution of 2560x1440 (one connected over HDMI-1, the other over DP-1). On the one connected over HDMI the maximum available resolution is 2048x1152. I tried to add the missing resolution with xrandr to HDMI-1 - but this was not successful (Error: could not apply...). ... 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:0684] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] Kernel driver in use: radeon Kernel modules: radeon, amdgpu Linux swinkler-Precision-M2800 4.13.0-19-generic #22-Ubuntu SMP Mon Dec 4 11:58:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux /usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server Hit:1 http://ch.archive.ubuntu.com/ubuntu artful InRelease Hit:2 http://ch.archive.ubuntu.com/ubuntu artful-updates InRelease Get:3 http://security.ubuntu.com/ubuntu artful-security InRelease [78.6 kB] Hit:4 http://ch.archive.ubuntu.com/ubuntu artful-backports InRelease Hit:5 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu artful InRelease Fetched 78.6 kB in 0s (194 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done fbset is already the newest version (2.1-29ubuntu1). hardinfo is already the newest version (0.5.1+git20170815-1). inxi is already the newest version (2.3.37-1). mesa-utils is already the newest version (8.3.0-5). nux-tools is already the newest version (4.0.8+17.10.20170922-0ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. System:Host: swinkler-Precision-M2800 Kernel: 4.13.0-19-generic x86_64 bits: 64 Desktop: Gnome 3.26.2 Distro: Ubuntu 17.10 Machine: Device: laptop System: Dell product: Precision M2800 v: 01 serial: N/A Mobo: Dell model: 01P6V3 v: A00 serial: N/A BIOS: Dell v: A06 date: 05/18/2015 BatteryBAT0: charge: 42.0 Wh 93.5% condition: 44.9/65.5 Wh (69%) CPU: Quad core Intel Core i7-4810MQ (-HT-MCP-) cache: 6144 KB clock speeds: max: 3800 MHz 1: 2793 MHz 2: 2793 MHz 3: 2793 MHz 4: 2793 MHz 5: 2793 MHz 6: 2793 MHz 7: 2793 MHz 8: 2793 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: Advanced Micro Devices [AMD/ATI] Mars XTX [Radeon HD 8790M] Display Server: x11 (X.Org 1.19.5 ) drivers: i915,radeon Resolution: 2048x1152@60.00hz, 2560x1440@59.95hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 4.5 Mesa 17.2.4 Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller driver: snd_hda_intel Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.13.0-19-generic Network: Card-1: Intel Ethernet Connection I217-LM driver: e1000e IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 34:e6:d7:87:64:35 Card-2: Intel Wireless 7260 driver: iwlwifi IF: wlp3s0 state: down mac: ac:fd:ce:4c:4a:8c Drives:HDD Total Size: 1272.3GB (28.8% used) ID-1: USB /dev/sda model: Rugged_Mini_USB3 size: 1000.2GB ID-2: USB /dev/sdb model: USB_Flash_Disk size: 16.0GB ID-3: /dev/sdc model: LITEONIT_LCS size: 256.1GB Partition: ID-1: / size: 218G used: 17G (9%) fs: ext4 dev: /dev/dm-1 ID-2: /boot size: 704M used: 137M (21%) fs: ext4 dev: /dev/sdc1 ID-3: swap-1 size: 17.08GB used: 0.00GB (0%) fs: swap dev: /dev/dm-2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 60.0C mobo: N/A gpu: 50.0 Fan Speeds (in rpm): cpu: N/A Info: Processes: 289 Uptime: 6 min Memory: 1433.9/15949.3MB Client: Shell (bash) inxi: 2.3.37 mode "1024x768" geometry 1024 768 1024 768 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name: radeondrmfb Addre
[Touch-packages] [Bug 1740635] [NEW] Correct screen resolution not available on Ubuntu 17.10
You have been subscribed to a public bug: I did a fresh installation of Ubuntu 17.10 on my Dell Precision M2800. I use two external displays (both Dell U2715Hc) with a screen resolution of 2560x1440 (one connected over HDMI-1, the other over DP-1). On the one connected over HDMI the maximum available resolution is 2048x1152. I tried to add the missing resolution with xrandr to HDMI-1 - but this was not successful (Error: could not apply...). ... 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:0684] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] Kernel driver in use: radeon Kernel modules: radeon, amdgpu Linux swinkler-Precision-M2800 4.13.0-19-generic #22-Ubuntu SMP Mon Dec 4 11:58:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux /usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server Hit:1 http://ch.archive.ubuntu.com/ubuntu artful InRelease Hit:2 http://ch.archive.ubuntu.com/ubuntu artful-updates InRelease Get:3 http://security.ubuntu.com/ubuntu artful-security InRelease [78.6 kB] Hit:4 http://ch.archive.ubuntu.com/ubuntu artful-backports InRelease Hit:5 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu artful InRelease Fetched 78.6 kB in 0s (194 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done fbset is already the newest version (2.1-29ubuntu1). hardinfo is already the newest version (0.5.1+git20170815-1). inxi is already the newest version (2.3.37-1). mesa-utils is already the newest version (8.3.0-5). nux-tools is already the newest version (4.0.8+17.10.20170922-0ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. System:Host: swinkler-Precision-M2800 Kernel: 4.13.0-19-generic x86_64 bits: 64 Desktop: Gnome 3.26.2 Distro: Ubuntu 17.10 Machine: Device: laptop System: Dell product: Precision M2800 v: 01 serial: N/A Mobo: Dell model: 01P6V3 v: A00 serial: N/A BIOS: Dell v: A06 date: 05/18/2015 BatteryBAT0: charge: 42.0 Wh 93.5% condition: 44.9/65.5 Wh (69%) CPU: Quad core Intel Core i7-4810MQ (-HT-MCP-) cache: 6144 KB clock speeds: max: 3800 MHz 1: 2793 MHz 2: 2793 MHz 3: 2793 MHz 4: 2793 MHz 5: 2793 MHz 6: 2793 MHz 7: 2793 MHz 8: 2793 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: Advanced Micro Devices [AMD/ATI] Mars XTX [Radeon HD 8790M] Display Server: x11 (X.Org 1.19.5 ) drivers: i915,radeon Resolution: 2048x1152@60.00hz, 2560x1440@59.95hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 4.5 Mesa 17.2.4 Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller driver: snd_hda_intel Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.13.0-19-generic Network: Card-1: Intel Ethernet Connection I217-LM driver: e1000e IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 34:e6:d7:87:64:35 Card-2: Intel Wireless 7260 driver: iwlwifi IF: wlp3s0 state: down mac: ac:fd:ce:4c:4a:8c Drives:HDD Total Size: 1272.3GB (28.8% used) ID-1: USB /dev/sda model: Rugged_Mini_USB3 size: 1000.2GB ID-2: USB /dev/sdb model: USB_Flash_Disk size: 16.0GB ID-3: /dev/sdc model: LITEONIT_LCS size: 256.1GB Partition: ID-1: / size: 218G used: 17G (9%) fs: ext4 dev: /dev/dm-1 ID-2: /boot size: 704M used: 137M (21%) fs: ext4 dev: /dev/sdc1 ID-3: swap-1 size: 17.08GB used: 0.00GB (0%) fs: swap dev: /dev/dm-2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 60.0C mobo: N/A gpu: 50.0 Fan Speeds (in rpm): cpu: N/A Info: Processes: 289 Uptime: 6 min Memory: 1433.9/15949.3MB Client: Shell (bash) inxi: 2.3.37 mode "1024x768" geometry 1024 768 1024 768 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name: radeondrmfb Address : 0xe05d8000 Size: 3145728 Type: PACKED PIXELS Visual : TRUECOLOR XPanStep: 1 YPanStep: 1 YWrapStep : 0 LineLength : 4096 Accelerator : No Version: 1:7.7+19ubuntu3 Screen 0: minimum 320 x 200, current 4608 x 2231, maximum 8192 x 8192 eDP-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 59.9348.00 1680x1050 59.9559.88
[Touch-packages] [Bug 886449] Re: [USB-Audio - USB Camera-B4.04.27.1 (playstation eye), recording] Pulseaudio fails to detect card
This bug still affects Debian alsa so maybe it should be merged into the
main alsa. It was a problem until there was a kernel update and now the
mic "just works" on newer kernels but the speaker is not working.
alsamixer does see the card and when you select it you get "cannot load
mixer controls: Invalid argument". apaly doesn't see it for some reason:
$ aplay -l
List of PLAYBACK Hardware Devices
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 7/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
However, arecord does see it:
$ arecord -l
List of CAPTURE Hardware Devices
card 1: CameraB409241 [USB Camera-B4.09.24.1], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
This bug affects me currently and I have heard other people were able to
workaround it with a file ~/.asoundrc but I have tried all of those and can't
get any to work.
--
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/886449
Title:
[USB-Audio - USB Camera-B4.04.27.1 (playstation eye), recording]
Pulseaudio fails to detect card
Status in pulseaudio package in Ubuntu:
Expired
Bug description:
Ubuntu 10.10 (working)
ubuntu@ubuntu:~$ dmesg | tail -n 10
[ 171.597554] hda-intel: IRQ timing workaround is activated for card #0.
Suggest a bigger bdl_pos_adj.
[ 230.717829] usb 1-4: USB disconnect, address 4
[ 230.725857] gspca: video0 disconnect
[ 230.725953] gspca: video0 released
[ 234.110162] usb 1-4: new high speed USB device using ehci_hcd and address 5
[ 234.264858] gspca: probing 1415:2000
[ 234.393829] ov534: Sensor ID: 7721
[ 234.443919] ov534: frame_rate: 30
[ 234.444022] gspca: video0 created
[ 234.444148] gspca: probing 1415:2000
Ubuntu 11.10 (not working)
johnny@johnny-System-Product-Name:~$ dmesg | tail -n 10
[6.037901] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
[6.141178] r8169 :05:00.0: eth0: link up
[6.141764] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 17.104110] eth0: no IPv6 routers present
[ 37.732125] usb 1-4: new high speed USB device number 4 using ehci_hcd
[ 39.196154] usb 1-4: usbfs: USBDEVFS_CONTROL failed cmd mtp-probe rqt 128
rq 6 len 1024 ret -110
[ 39.200475] Linux video capture interface: v2.00
[ 39.200745] gspca: v2.13.0 registered
[ 39.372830] usbcore: registered new interface driver ov534
[ 39.376238] usbcore: registered new interface driver snd-usb-audio
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: pulseaudio 1:1.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: CameraB404271 [USB Camera-B4.04.27.1], device 0: USB Audio [USB
Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id',
'/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xfe6bc000 irq 53'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Error: command ['amixer', '-c', '1', 'info'] failed with exit code 1:
amixer: Mixer load hw:1 error: Invalid argument
Card hw:1 'CameraB404271'/'OmniVision Technologies, Inc. USB
Camera-B4.04.27.1 at usb-:00:12.2-4, high'
Mixer name : 'USB Mixer'
Components : 'USB1415:2000'
Controls : 1
Card1.Amixer.values: Error: command ['amixer', '-c', '1'] failed with exit
code 1: amixer: Mixer hw:1 load error: Invalid argument
Date: Sat Nov 5 01:20:09 2011
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: USB-Audio - USB Ca
[Touch-packages] [Bug 1732530] Re: Dejadup is not working b/c duplicity is not installed
This bug was fixed in the package ubuntu-mate-meta - 1.208 --- ubuntu-mate-meta (1.208) bionic; urgency=medium * Refreshed dependencies * Added duplicity to desktop-recommends (LP: #1732530) -- Martin Wimpress Sat, 30 Dec 2017 22:23:35 + ** Changed in: ubuntu-mate-meta (Ubuntu) Status: Fix Committed => Fix Released -- 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/1732530 Title: Dejadup is not working b/c duplicity is not installed Status in ubuntu-mate: Invalid Status in deja-dup package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Bug description: Ubuntu Mate 17.10 Dejadup is not working b/c duplicity is not installed. After a manual install, Deja-Dup works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1732530/+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 1732530] Re: Dejadup is not working b/c duplicity is not installed
** Tags added: artful -- 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/1732530 Title: Dejadup is not working b/c duplicity is not installed Status in ubuntu-mate: Invalid Status in deja-dup package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Bug description: Ubuntu Mate 17.10 Dejadup is not working b/c duplicity is not installed. After a manual install, Deja-Dup works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1732530/+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 1732530] Re: Dejadup is not working b/c duplicity is not installed
** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntu-mate-meta (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: ubuntu-mate-meta (Ubuntu) Importance: Undecided => Medium -- 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/1732530 Title: Dejadup is not working b/c duplicity is not installed Status in ubuntu-mate: Invalid Status in deja-dup package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Bug description: Ubuntu Mate 17.10 Dejadup is not working b/c duplicity is not installed. After a manual install, Deja-Dup works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1732530/+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 1732530] Re: Dejadup is not working b/c duplicity is not installed
It appears that duplicity is now a Suggests: for deja-dup and not installed by default. I will update the ubuntu-mate-meta package to include duplicity. ** Also affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: Confirmed => Invalid ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntukylin-meta (Ubuntu) Importance: Undecided Status: New -- 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/1732530 Title: Dejadup is not working b/c duplicity is not installed Status in ubuntu-mate: Invalid Status in deja-dup package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Bug description: Ubuntu Mate 17.10 Dejadup is not working b/c duplicity is not installed. After a manual install, Deja-Dup works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1732530/+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 1740054] Re: package libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 failed to install/upgrade: triggers looping, abandoned
Looks more like a bug in gnome-icon-theme and bamfdeamon to me. ** Package changed: vlc (Ubuntu) => gnome-icon-theme (Ubuntu) ** Also affects: bamf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1740054 Title: package libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 failed to install/upgrade: triggers looping, abandoned Status in bamf package in Ubuntu: New Status in gnome-icon-theme package in Ubuntu: New Bug description: I have problems upgrading to 17.10 from 17.04. Visually it kept equal to previous version ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 Date: Mon Dec 25 23:16:21 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-08-12 (135 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 SourcePackage: vlc Title: package libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2017-12-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1740054/+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 1740054] [NEW] package libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 failed to install/upgrade: triggers looping, abandoned
You have been subscribed to a public bug: I have problems upgrading to 17.10 from 17.04. Visually it kept equal to previous version ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 Date: Mon Dec 25 23:16:21 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-08-12 (135 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 SourcePackage: vlc Title: package libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2017-12-25 (0 days ago) ** Affects: gnome-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- package libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 failed to install/upgrade: triggers looping, abandoned https://bugs.launchpad.net/bugs/1740054 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. -- 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 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Zesty) Status: New => Confirmed -- 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/1618188 Title: systemd journal should be persistent by default: /var/log/journal should be created Status in systemd package in Ubuntu: Triaged Status in systemd source package in Xenial: Confirmed Status in systemd source package in Zesty: Confirmed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Triaged Bug description: After upgrading 14.04 -> 16.04, key services are now running on systemd and using the systemd journal for logging. In 14.04, key system logs like /var/log/messages and /var/log/syslog were persistent, but after the upgrade to 16.04 there has a been a regression of sorts: Logs sent to systemd's journald are now being thrown away during reboots. This behavior is controlled by the `Storage=` option in `/etc/systemd/journald.conf`. The default setting is `Storage=auto` which will persist logs in `/var/log/journal/`, *only if the directory already exists*. But the directory was not created as part of the 14.04 -> 16.04 upgrade, so logging was being lost for a while before I realized what was happening. This issue could be solved by either creating /var/log/journal or changing the default Storage behavior to `Storage=persistent`, which would create the directory if need be. ## Related reference * `systemd` currently compounds the issue by having ["journal --disk-usage" report memory usage as disk usage](https://github.com/systemd/systemd/issues/4059), giving the impression that the disk is being used for logging when it isn't. * [User wonders where to find logs from previous boots, unaware that the logs were thrown away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts) ## Recommended fix Restoring persistent logging as the default is recommended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+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 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Artful) Status: New => Confirmed -- 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/1618188 Title: systemd journal should be persistent by default: /var/log/journal should be created Status in systemd package in Ubuntu: Triaged Status in systemd source package in Xenial: Confirmed Status in systemd source package in Zesty: Confirmed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Triaged Bug description: After upgrading 14.04 -> 16.04, key services are now running on systemd and using the systemd journal for logging. In 14.04, key system logs like /var/log/messages and /var/log/syslog were persistent, but after the upgrade to 16.04 there has a been a regression of sorts: Logs sent to systemd's journald are now being thrown away during reboots. This behavior is controlled by the `Storage=` option in `/etc/systemd/journald.conf`. The default setting is `Storage=auto` which will persist logs in `/var/log/journal/`, *only if the directory already exists*. But the directory was not created as part of the 14.04 -> 16.04 upgrade, so logging was being lost for a while before I realized what was happening. This issue could be solved by either creating /var/log/journal or changing the default Storage behavior to `Storage=persistent`, which would create the directory if need be. ## Related reference * `systemd` currently compounds the issue by having ["journal --disk-usage" report memory usage as disk usage](https://github.com/systemd/systemd/issues/4059), giving the impression that the disk is being used for logging when it isn't. * [User wonders where to find logs from previous boots, unaware that the logs were thrown away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts) ## Recommended fix Restoring persistent logging as the default is recommended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+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 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1618188 Title: systemd journal should be persistent by default: /var/log/journal should be created Status in systemd package in Ubuntu: Triaged Status in systemd source package in Xenial: Confirmed Status in systemd source package in Zesty: Confirmed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Triaged Bug description: After upgrading 14.04 -> 16.04, key services are now running on systemd and using the systemd journal for logging. In 14.04, key system logs like /var/log/messages and /var/log/syslog were persistent, but after the upgrade to 16.04 there has a been a regression of sorts: Logs sent to systemd's journald are now being thrown away during reboots. This behavior is controlled by the `Storage=` option in `/etc/systemd/journald.conf`. The default setting is `Storage=auto` which will persist logs in `/var/log/journal/`, *only if the directory already exists*. But the directory was not created as part of the 14.04 -> 16.04 upgrade, so logging was being lost for a while before I realized what was happening. This issue could be solved by either creating /var/log/journal or changing the default Storage behavior to `Storage=persistent`, which would create the directory if need be. ## Related reference * `systemd` currently compounds the issue by having ["journal --disk-usage" report memory usage as disk usage](https://github.com/systemd/systemd/issues/4059), giving the impression that the disk is being used for logging when it isn't. * [User wonders where to find logs from previous boots, unaware that the logs were thrown away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts) ## Recommended fix Restoring persistent logging as the default is recommended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+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 1732222] Re: Language support not installed matching locale
** Package changed: language-pack-en (Ubuntu) => language-selector (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en in Ubuntu. https://bugs.launchpad.net/bugs/173 Title: Language support not installed matching locale Status in language-selector package in Ubuntu: New Bug description: When Ubuntu is installed with UK locale settings during setup, all of the language support is not installed and some applications e.g. LibreOffice display with non-UK English. The extra language support is prompted to be installed *the first time* the user accesses the language options (see screenshot attached). When this language support is installed, these applications then (correctly) display menus etc in UK English. Ubuntu setup appears to not install the matching locale languages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/173/+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 1740611] Re: Pulseaudio: please compile with support for sox resampler
** Description changed: The pulseaudio package in Ubuntu is compiled without support for the sox resampling methods (soxr-mq, soxr-hq, soxr-vhq), although they are mentioned in the manpages of pulse-daemon.conf(5). Please consider compiling pulseaudio with sox support. Thanks! + + + EDIT: The debian packages actually *are* compiled with libsoxr-dev. What is the reason to drop that support in Ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1740611 Title: Pulseaudio: please compile with support for sox resampler Status in pulseaudio package in Ubuntu: New Bug description: The pulseaudio package in Ubuntu is compiled without support for the sox resampling methods (soxr-mq, soxr-hq, soxr-vhq), although they are mentioned in the manpages of pulse-daemon.conf(5). Please consider compiling pulseaudio with sox support. Thanks! EDIT: The debian packages actually *are* compiled with libsoxr-dev. What is the reason to drop that support in Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1740611/+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 1740611] [NEW] Pulseaudio: please compile with support for sox resampler
Public bug reported: The pulseaudio package in Ubuntu is compiled without support for the sox resampling methods (soxr-mq, soxr-hq, soxr-vhq), although they are mentioned in the manpages of pulse-daemon.conf(5). Please consider compiling pulseaudio with sox support. Thanks! ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Package changed: pasystray (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1740611 Title: Pulseaudio: please compile with support for sox resampler Status in pulseaudio package in Ubuntu: New Bug description: The pulseaudio package in Ubuntu is compiled without support for the sox resampling methods (soxr-mq, soxr-hq, soxr-vhq), although they are mentioned in the manpages of pulse-daemon.conf(5). Please consider compiling pulseaudio with sox support. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1740611/+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 1740611] [NEW] Pulseaudio: please compile with support for sox resampler
You have been subscribed to a public bug: The pulseaudio package in Ubuntu is compiled without support for the sox resampling methods (soxr-mq, soxr-hq, soxr-vhq), although they are mentioned in the manpages of pulse-daemon.conf(5). Please consider compiling pulseaudio with sox support. Thanks! ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- Pulseaudio: please compile with support for sox resampler https://bugs.launchpad.net/bugs/1740611 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. -- 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 1726309] Re: avahi-daemon[590]: chroot.c: open() failed: No such file or directory
The ubuntu version is outdated, please sync it with Debian http://metadata.ftp- master.debian.org/changelogs/main/a/avahi/avahi_0.7-3_changelog ** Tags added: upgrade-software-version -- 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/1726309 Title: avahi-daemon[590]: chroot.c: open() failed: No such file or directory Status in avahi package in Ubuntu: Confirmed Bug description: Get that error on a fresh mini.iso install [uArtful 3] ~ > journalctl | grep avahi avahi-daemon[581]: Found user 'avahi' (UID 116) and group 'avahi' (GID 122). avahi-daemon[581]: Successfully dropped root privileges. avahi-daemon[581]: avahi-daemon 0.6.32 starting up. avahi-daemon[581]: Successfully called chroot(). avahi-daemon[581]: Successfully dropped remaining capabilities. avahi-daemon[590]: chroot.c: open() failed: No such file or directory avahi-daemon[581]: Failed to open /etc/resolv.conf: Invalid argument avahi-daemon[581]: No service file found in /etc/avahi/services. avahi-daemon[581]: Network interface enumeration completed. avahi-daemon[581]: Server startup complete. Host name is uArtful.local. Local service cookie is 2251384537. avahi-daemon[581]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.1.2. avahi-daemon[581]: New relevant interface enp2s0.IPv4 for mDNS. avahi-daemon[581]: Registering new address record for 192.168.1.2 on enp2s0.IPv4. avahi-daemon[581]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::7285:c2ff:fe23:9b4c. avahi-daemon[581]: New relevant interface enp2s0.IPv6 for mDNS. avahi-daemon[581]: Registering new address record for fe80::7285:c2ff:fe23:9b4c on enp2s0.*. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 10:47:44 2017 SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1726309/+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 1726309] Re: avahi-daemon[590]: chroot.c: open() failed: No such file or directory
https://github.com/lathiat/avahi/issues/153 NetworkManager-wait-online.service must be enable for this to work. To enable this service: # systemctl enable NetworkManager-wait-online.service (ref: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget ) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1726309 Title: avahi-daemon[590]: chroot.c: open() failed: No such file or directory Status in avahi package in Ubuntu: Confirmed Bug description: Get that error on a fresh mini.iso install [uArtful 3] ~ > journalctl | grep avahi avahi-daemon[581]: Found user 'avahi' (UID 116) and group 'avahi' (GID 122). avahi-daemon[581]: Successfully dropped root privileges. avahi-daemon[581]: avahi-daemon 0.6.32 starting up. avahi-daemon[581]: Successfully called chroot(). avahi-daemon[581]: Successfully dropped remaining capabilities. avahi-daemon[590]: chroot.c: open() failed: No such file or directory avahi-daemon[581]: Failed to open /etc/resolv.conf: Invalid argument avahi-daemon[581]: No service file found in /etc/avahi/services. avahi-daemon[581]: Network interface enumeration completed. avahi-daemon[581]: Server startup complete. Host name is uArtful.local. Local service cookie is 2251384537. avahi-daemon[581]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.1.2. avahi-daemon[581]: New relevant interface enp2s0.IPv4 for mDNS. avahi-daemon[581]: Registering new address record for 192.168.1.2 on enp2s0.IPv4. avahi-daemon[581]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::7285:c2ff:fe23:9b4c. avahi-daemon[581]: New relevant interface enp2s0.IPv6 for mDNS. avahi-daemon[581]: Registering new address record for fe80::7285:c2ff:fe23:9b4c on enp2s0.*. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 10:47:44 2017 SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1726309/+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 1736880] Re: systemd[1]: Failed to start Raise network interfaces.
Looks like we need waiting for systemd v236 to get the required patch https://github.com/systemd/systemd/commit/a39f92d391ac1ce06b3618874ff4211ecb11f549 ** Tags added: patch -- 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/1736880 Title: systemd[1]: Failed to start Raise network interfaces. Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I usually do installation via a netboot mini.iso, and was wondering why i was not finding the 'wired' settings into Settings -> Network, only the 'vpn' settings are displayed. A forum thread have told me that 'netplan (package name is nplan) by default doesn't use NetworkManager when installed from netboot' https://ubuntuforums.org/showthread.php?t=2379460 Hope to get the next netboot doing a full installation when the bionic iso will be proposed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nplan 0.32 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 7 08:06:48 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nplan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1736880/+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 1740603] Re: Xorg freeze
i do not launch terminal. i acceses teminal but iam fail mainy time to launch terminal. what i do to solve this problem. ** Changed in: xorg (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/xorg/+question/662396 -- 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/1740603 Title: Xorg freeze Status in xorg package in Ubuntu: Invalid Bug description: terminal do not launched. itried to launch terminal bat iam fail to launch terminal ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 30 20:04:16 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06f0] InstallationDate: Installed on 2017-02-14 (319 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-137-generic.efi.signed root=UUID=34b519c8-589f-4043-b001-a8ab0820892e ro locale=en_IN quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0XPKP0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd01/19/2016:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3460 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 30 18:16:22 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1201 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1740603/+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 1740603] [NEW] Xorg freeze
Public bug reported: terminal do not launched. itried to launch terminal bat iam fail to launch terminal ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 30 20:04:16 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06f0] InstallationDate: Installed on 2017-02-14 (319 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-137-generic.efi.signed root=UUID=34b519c8-589f-4043-b001-a8ab0820892e ro locale=en_IN quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0XPKP0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd01/19/2016:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3460 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 30 18:16:22 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1201 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.11 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 false-gpu-hang freeze trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1740603 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: terminal do not launched. itried to launch terminal bat iam fail to launch terminal ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 30 20:04:16 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06f0] InstallationDate: Installed on 2017-02-14 (319 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-137-generic.efi.signed root=UUID=34b519c8-589f-4043-b001-a8ab0820892e ro locale=en_IN quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_nativ
[Touch-packages] [Bug 1740599] [NEW] Selecting multiple files and dragging them to file manager is broken
Public bug reported: This issue is reproducible every time I try. - Start with two or more files on the desktop - Drag out a selection area around the files to select them - Open "Files" file manager - Drag and drop them to a folder The drag and drop operation fails and the cursor gets stuck as a hand icon. Signing out is the only way I have tried to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libwayland-server0 1.14.0-1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 10:15:56 2017 Dependencies: gcc-7-base 7.2.0-8ubuntu3 libc6 2.26-0ubuntu2 libffi6 3.2.1-6 libgcc1 1:7.2.0-8ubuntu3 DistUpgraded: 2017-11-09 17:38:14,971 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5926] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:075b] InstallationDate: Installed on 2017-10-11 (80 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=4c6cd516-44fe-441d-ad87-7a83e1593848 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: Upgraded to artful on 2017-11-09 (50 days ago) dmi.bios.date: 11/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 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:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session ** Attachment added: "Screenshot from 2017-12-30 10-27-14.png" https://bugs.launchpad.net/bugs/1740599/+attachment/5029105/+files/Screenshot%20from%202017-12-30%2010-27-14.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1740599 Title: Selecting multiple files and dragging them to file manager is broken Status in wayland package in Ubuntu: New Bug description: This issue is reproducible every time I try. - Start with two or more files on the desktop - Drag out a selection area around the files to select them - Open "Files" file manager - Drag and drop them to a folder The drag and drop operation fails and the cursor gets stuck as a hand icon. Signing out is the only way I have tried to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libwayland-server0 1.14.0-1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 10:15:56 2017 Dependencies: gcc-7-base 7.2.0-8ubuntu3 libc6 2.26-0ubuntu2 libffi6 3.2.1-6 libgcc1 1:7.2.0-8ubuntu3 DistUpgraded: 2017-11-09 17:38:14,971 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5926] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:075b] InstallationDate: Installed on 2017-10-11 (80 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=4c6cd516-44fe-441d-ad87-7a83e1593848 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: Upgraded to artful on 2017-11-09 (50 days ago) dmi.bios.date: 11/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell
[Touch-packages] [Bug 1716203] Re: Backport packages for 16.04.4 HWE stack
16.04.4 images will ship with this stack, but they can be pushed to -updates earlier. If you have a radeon capable of running vulkan apps, please verify this on xenial: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-5.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in wayland-protocols source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-ati source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up
Ubuntu 17.10 Changing network.target to network-online.target in /lib/systemd/system/ssh.service worked. I also added Wants=network-online.target (don't know if it's necessary but https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ suggests it) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/216847 Title: sshd will not start at boot if ListenAddress is set, because network interface is not yet up Status in openssh package in Ubuntu: Confirmed Bug description: Binary package hint: openssh-server The sshd will not start at boot if the ListenAddress option in /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 . I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the openssh-server package. I would expect that sshd is started after boot but it will not and I found this in /var/log/auth.log: sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign requested address. sshd[4527]: fatal: Cannot bind any address. Once the System is started you can start/stop the sshd with the /etc/init.d/ssh script without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/216847/+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 1740573] Re: rm command prints non-locale escaped error messages
** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1740573 Title: rm command prints non-locale escaped error messages Status in coreutils package in Ubuntu: New Bug description: If the file "tx" does not exist and the locale is en_US.UTF-8, "rm" will print: $ LANG=en_US.UTF-8 rm tx rm: cannot remove â: No such file or directory $ LANG=en_US rm tx rm: cannot remove 'tx': No such file or directory $ LANG=C rm tx rm: cannot remove 'tx': No such file or directory This is in coreutils 8.21-1ubuntu5.4 on Ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1740573/+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 1732222] Re: Language support not installed matching locale
If it installs all of the language packages in other languages, except for English-UK (and other non-US English locales), then it IS a bug. The ubiquity installer could install every language pack when the user chooses English-UK - it makes sense. The user wants English-UK, so please install all of them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en in Ubuntu. https://bugs.launchpad.net/bugs/173 Title: Language support not installed matching locale Status in language-pack-en package in Ubuntu: New Bug description: When Ubuntu is installed with UK locale settings during setup, all of the language support is not installed and some applications e.g. LibreOffice display with non-UK English. The extra language support is prompted to be installed *the first time* the user accesses the language options (see screenshot attached). When this language support is installed, these applications then (correctly) display menus etc in UK English. Ubuntu setup appears to not install the matching locale languages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/173/+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 1740579] [NEW] Pomalý systém
Public bug reported: SK.LANG.PRACUJE pomaly,pomaly nabieha systém.Nie som dlho užívateľ Ubuntu,zatiaľ sa iba učím. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompositorRunning: None Date: Sat Dec 30 09:50:44 2017 DistUpgraded: 2017-10-23 19:02:47,148 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:13c7] InstallationDate: Installed on 2017-05-30 (214 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170411) MachineType: ASUSTeK Computer Inc. K54C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=6ba22068-04c3-4d1a-8a5e-dac9dd5aec79 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2017-10-23 (67 days ago) dmi.bios.date: 01/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K54C.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K54C dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK54C.204:bd01/20/2012:svnASUSTeKComputerInc.:pnK54C:pvr1.0:rvnASUSTeKComputerInc.:rnK54C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K54C dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 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:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 23 16:35:06 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1740579 Title: Pomalý systém Status in xorg package in Ubuntu: New Bug description: SK.LANG.PRACUJE pomaly,pomaly nabieha systém.Nie som dlho užívateľ Ubuntu,zatiaľ sa iba učím. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompositorRunning: None Date: Sat Dec 30 09:50:44 2017 DistUpgraded: 2017-10-23 19:02:47,148 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:13c7] InstallationDate: Installed on 2017-05-30 (214 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170411) MachineType: ASUSTeK Computer Inc. K54C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=6ba22068-04c3-4d1a-8a5e-dac9dd5aec79 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2017-10-23 (67 days ago) dmi.bios.date: 01/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K54C.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K54C dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK54C.204:bd01/20/2012:svnASUSTeKComputerInc.:pnK54C:pvr1.0:rvnASUSTeKComputerInc.:rnK54C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K54C dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl
