[Touch-packages] [Bug 1882484] Re: Firewall rule in before.rules for dhcp is wrong
Thanks Jamie, Ah, cool, so that ufw config is when the install is a client. I am having issues with the install as a DHCPv4 server. I will revert the UFW changes I have made and add in a new /etc/ufw/application.d/dhcpd config to allow the install to run a DHCPv4 server Thanks Josh PS. isc-dhcp-server when setup, by default is using "raw" sockets and thus the ufw rules are bypassed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1882484 Title: Firewall rule in before.rules for dhcp is wrong Status in ufw package in Ubuntu: Invalid Bug description: The file delivered - /usr/share/ufw/iptables/before.rules which is then copied to - /etc/ufw/before.rules Delivered by Package: # allow dhcp client to work -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT The ports for --sport and --dport are swapped Should be: -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT Package version found in: 0.36-0ubuntu0.1 Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't drop the packets with the incorrect configuration. This has had me stumped for the last hour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882484/+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 1882314] Re: Firewall rule in before6.rules for dhcp6 is wrong
Thanks Jamie, Ah, cool, so that ufw config is when the install is a client. I am having issues with the install as a DHCPv6 server. I will revert the UFW changes I have made and add in a new /etc/ufw/application.d/dhcpd config to allow the install to run a DHCPv6 server Thanks Josh PS. isc-dhcp-server6 when setup, by default is not using "raw" sockets and thus the ufw rules are enforced -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1882314 Title: Firewall rule in before6.rules for dhcp6 is wrong Status in ufw package in Ubuntu: Invalid Bug description: When running DHCPv6, clients are not able get IP address. The firewall rule in ip6table is incorrect, and not allowing client requests in. The ports need to be swapped and the dst address needs to be removed, as it's a broadcast The file delivered - /usr/share/ufw/iptables/before6.rules which is then copied to - /etc/ufw/before6.rules Delivered by Package: # allow dhcp client to work -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 -j ACCEPT The ports for --sport and --dport are swapped -d fe80::/10 needs to be removed Should be: -A ufw6-before-input -p udp -s fe80::/10 --sport 546 --dport 547 -j ACCEPT Package version found in: 0.36-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882314/+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 1882314] Re: Firewall rule in before6.rules for dhcp6 is wrong
** Description changed: When running DHCPv6, clients are not able get IP address. - The firewall rule in ip6table is incorrect, and not allowing client requests in. The ports need to be swapped + The firewall rule in ip6table is incorrect, and not allowing client requests in. The ports need to be swapped and the dst address needs to be removed, as it's a broadcast The file delivered - /usr/share/ufw/iptables/before6.rules which is then copied to - /etc/ufw/before6.rules Delivered by Package: # allow dhcp client to work -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 -j ACCEPT The ports for --sport and --dport are swapped + -d fe80::/10 needs to be removed Should be: - -A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10 - --dport 547 -j ACCEPT + -A ufw6-before-input -p udp -s fe80::/10 --sport 546 --dport 547 -j + ACCEPT Package version found in: 0.36-0ubuntu0.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1882314 Title: Firewall rule in before6.rules for dhcp6 is wrong Status in ufw package in Ubuntu: New Bug description: When running DHCPv6, clients are not able get IP address. The firewall rule in ip6table is incorrect, and not allowing client requests in. The ports need to be swapped and the dst address needs to be removed, as it's a broadcast The file delivered - /usr/share/ufw/iptables/before6.rules which is then copied to - /etc/ufw/before6.rules Delivered by Package: # allow dhcp client to work -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 -j ACCEPT The ports for --sport and --dport are swapped -d fe80::/10 needs to be removed Should be: -A ufw6-before-input -p udp -s fe80::/10 --sport 546 --dport 547 -j ACCEPT Package version found in: 0.36-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882314/+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 1879796] Re: File descriptor leak in libva2
This patch has been merged by libva -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1879796 Title: File descriptor leak in libva2 Status in libva package in Ubuntu: New Bug description: I believe there is a file descriptor leak in libva. I have attached sample code which simply opens and calls vaInitialize and vaTerminate in a loop. Running this code will eventually run out of file descriptors. I have submitted a pull request here: https://github.com/intel/libva/pull/418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1879796/+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 1882484] [NEW] Firewall rule in before.rules for dhcp is wrong
Public bug reported: The file delivered - /usr/share/ufw/iptables/before.rules which is then copied to - /etc/ufw/before.rules Delivered by Package: # allow dhcp client to work -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT The ports for --sport and --dport are swapped Should be: -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT Package version found in: 0.36-0ubuntu0.1 Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't drop the packets with the incorrect configuration. This has had me stumped for the last hour. ** Affects: ufw (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1882484 Title: Firewall rule in before.rules for dhcp is wrong Status in ufw package in Ubuntu: New Bug description: The file delivered - /usr/share/ufw/iptables/before.rules which is then copied to - /etc/ufw/before.rules Delivered by Package: # allow dhcp client to work -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT The ports for --sport and --dport are swapped Should be: -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT Package version found in: 0.36-0ubuntu0.1 Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't drop the packets with the incorrect configuration. This has had me stumped for the last hour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882484/+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 1882314] Re: Firewall rule in before6.rules for dhcp6 is wrong
** Description changed: - Firewall rule in ip6table is incorrect, the ports need to be swapped + When running DHCPv6, clients are not able get IP address. + The firewall rule in ip6table is incorrect, and not allowing client requests in. The ports need to be swapped The file delivered - /usr/share/ufw/iptables/before6.rules - which is then copied to - /etc/ufw/before6.rules + which is then copied to - /etc/ufw/before6.rules Delivered by Package: # allow dhcp client to work -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 -j ACCEPT - The ports for + The ports for --sport and --dport are swapped Should be: -A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10 --dport 547 -j ACCEPT Package version found in: - 0.36-0ubuntu0.1 + 0.36-0ubuntu0.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1882314 Title: Firewall rule in before6.rules for dhcp6 is wrong Status in ufw package in Ubuntu: New Bug description: When running DHCPv6, clients are not able get IP address. The firewall rule in ip6table is incorrect, and not allowing client requests in. The ports need to be swapped The file delivered - /usr/share/ufw/iptables/before6.rules which is then copied to - /etc/ufw/before6.rules Delivered by Package: # allow dhcp client to work -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 -j ACCEPT The ports for --sport and --dport are swapped Should be: -A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10 --dport 547 -j ACCEPT Package version found in: 0.36-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882314/+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 1882317] [NEW] Dual Stack DHCP clobber each other when using /run/dhcp-server/ for pid files
Public bug reported:
When installing dual stack IPv4 and IPv6 DHCP I found that DHCPv4 and
DHCPv6 clobber each others /run/dhcp-server path when you stop or
restart one of the daemons
I found that the config in the systemd unit has the /run path set to the
same location for both DHCPv4 and DHCPv6
In /lib/systemd/system/isc-dhcp-server.service the offending line that
conflicts is:
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf
$CONFIG_FILE $INTERFACES'
In /lib/systemd/system/isc-dhcp-server6.service the offending line that
conflicts is:
exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf
$CONFIG_FILE $INTERFACES'
This means if you stop/restart DHCPv4 or DHCPv6, then it cleans up the
path /run/dhcp-server and removed the pid file for the alternate
process.
I have found a possible fix is to give DHCPv6 it's own /run path, thus I
suggest:
1) update DHCPv6 to use /run/dhcp-server6/
Update /lib/systemd/system/isc-dhcp-server6.service to use /run/dhcp-server6/
ie.
exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server6/dhcpd6.pid
-cf $CONFIG_FILE $INTERFACES'
Now we need to give dhcp access to this path in Apparmor:
2) Update /etc/apparmor.d/usr.sbin.dhcpd and add an additional line
38d39
/var/lib/dhcp/dhcpd{,6}.leases* lrw,
/var/log/ r,
/var/log/** rw,
/{,var/}run/{,dhcp-server/}dhcpd{,6}.pid rw,
+ /{,var/}run/{,dhcp-server6/}dhcpd{,6}.pid rw,
Found in package version:
4.4.1-2ubuntu5
** Affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
When installing dual stack IPv4 and IPv6 DHCP I found that DHCPv4 and
DHCPv6 clobber each others /run/dhcp-server path when you stop or
restart one of the daemons
I found that the config in the systemd unit has the /run path set to the
same location for both DHCPv4 and DHCPv6
-
In /lib/systemd/system/isc-dhcp-server.service the offending line that
conflicts is:
- exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES'
-
+ exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES'
In /lib/systemd/system/isc-dhcp-server6.service the offending line that
conflicts is:
- exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid
-cf $CONFIG_FILE $INTERFACES'
+ exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid
-cf $CONFIG_FILE $INTERFACES'
-
- This means if you stop/restart DHCPv4 or DHCPv6, then it cleans up the path
/run/dhcp-server and removed the pid file for the alternate process.
+ This means if you stop/restart DHCPv4 or DHCPv6, then it cleans up the
+ path /run/dhcp-server and removed the pid file for the alternate
+ process.
I have found a possible fix is to give DHCPv6 it's own /run path, thus I
suggest:
1) update DHCPv6 to use /run/dhcp-server6/
Update /lib/systemd/system/isc-dhcp-server6.service to use /run/dhcp-server6/
ie.
- exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server6/dhcpd6.pid
-cf $CONFIG_FILE $INTERFACES'
+ exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server6/dhcpd6.pid
-cf $CONFIG_FILE $INTERFACES'
Now we need to give dhcp access to this path in Apparmor:
2) Update /etc/apparmor.d/usr.sbin.dhcpd and add an additional line
38d39
- /var/lib/dhcp/dhcpd{,6}.leases* lrw,
- /var/log/ r,
- /var/log/** rw,
- /{,var/}run/{,dhcp-server/}dhcpd{,6}.pid rw,
+ /var/lib/dhcp/dhcpd{,6}.leases* lrw,
+ /var/log/ r,
+ /var/log/** rw,
+ /{,var/}run/{,dhcp-server/}dhcpd{,6}.pid rw,
+ /{,var/}run/{,dhcp-server6/}dhcpd{,6}.pid rw,
+
+ Found in package version:
+ 4.4.1-2ubuntu5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1882317
Title:
Dual Stack DHCP clobber each other when using /run/dhcp-server/ for
pid files
Status in isc-dhcp package in Ubuntu:
New
Bug description:
When installing dual stack IPv4 and IPv6 DHCP I found that DHCPv4 and
DHCPv6 clobber each others /run/dhcp-server path when you stop or
restart one of the daemons
I found that the config in the systemd unit has the /run path set to
the same location for both DHCPv4 and DHCPv6
In /lib/systemd/system/isc-dhcp-server.service the offending line that
conflicts is:
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES'
In /lib/systemd/system/isc-dhcp-server6.service the offending line that
conflicts is:
exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid
-cf $CONFIG_FILE $INTERFACES'
This means if you stop/restart DHCPv4 or DHCPv6, then it cleans up the
path /run/dhcp-server and removed the pid file for the alternate
process.
I have found a possible fix is to give DHCPv6 it's own /
[Touch-packages] [Bug 1882314] [NEW] Firewall rule in before6.rules for dhcp6 is wrong
Public bug reported: Firewall rule in ip6table is incorrect, the ports need to be swapped The file delivered - /usr/share/ufw/iptables/before6.rules which is then copied to - /etc/ufw/before6.rules Delivered by Package: # allow dhcp client to work -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 -j ACCEPT The ports for --sport and --dport are swapped Should be: -A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10 --dport 547 -j ACCEPT Package version found in: 0.36-0ubuntu0.1 ** Affects: ufw (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1882314 Title: Firewall rule in before6.rules for dhcp6 is wrong Status in ufw package in Ubuntu: New Bug description: Firewall rule in ip6table is incorrect, the ports need to be swapped The file delivered - /usr/share/ufw/iptables/before6.rules which is then copied to - /etc/ufw/before6.rules Delivered by Package: # allow dhcp client to work -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 -j ACCEPT The ports for --sport and --dport are swapped Should be: -A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10 --dport 547 -j ACCEPT Package version found in: 0.36-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882314/+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 1879796] [NEW] File descriptor leak in libva2
Public bug reported: I believe there is a file descriptor leak in libva. I have attached sample code which simply opens and calls vaInitialize and vaTerminate in a loop. Running this code will eventually run out of file descriptors. I have submitted a pull request here: https://github.com/intel/libva/pull/418 ** Affects: libva (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Demonstrates leak by opening and closing libva" https://bugs.launchpad.net/bugs/1879796/+attachment/5374841/+files/vainfo.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1879796 Title: File descriptor leak in libva2 Status in libva package in Ubuntu: New Bug description: I believe there is a file descriptor leak in libva. I have attached sample code which simply opens and calls vaInitialize and vaTerminate in a loop. Running this code will eventually run out of file descriptors. I have submitted a pull request here: https://github.com/intel/libva/pull/418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1879796/+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 1638395] Re: Unable to locate remote printer when printing
the remote printing is basically a kind of printing which contains a distant printer. it is used for business purposes mainly while we are traveling it is an alternative term of fax.it make things easy like we don't need to carry papers while we are traveling remote printer make this problem easy for us. but when we can not find this remote printer then it's a big issue to sort out this problem read this article and do step by step as instructed here. www.facebook.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1638395 Title: Unable to locate remote printer when printing Status in cups package in Ubuntu: Confirmed Bug description: My printer (EPSON Stylus Photo RX520) is connected to a Yakkety station called "paris" which is the printing server. Printing is fine from the server. When i configure another Yakkety station to print via this server, the printer is detected OK via dnssd, the driver is installed OK. But i can't print. I get the following message "Unable to locate printer "paris.local"." I used to work on xenial but the connection was through ipps. I tried to configure the connection as in xenial, to no avail ... What i did: add "192.168.1.4 paris.local" in /etc/hosts remove printer from cups, reinstalled it and i finally was able to print on the remote printer! Don't know if this problem is related to cups or avahi ... Ubuntu 16.10 cups 2.2.0-2 What i expected to happen: printing successful What happened: client cannot locate remote printer, add to add a line in /etc/hosts to make it work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638395/+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 1766106] [NEW] ntp.ubuntu.com not reliable, but used in standard configuration
Public bug reported: In systemd-timesyncd ntp.ubuntu.com is used as fall back ntp server. However, one of the addresses it resolves to is not available for quite some while: [...] Apr 14 07:37:42 singold systemd-timesyncd[773]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 14 08:10:45 singold systemd-timesyncd[773]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 15 08:20:48 singold systemd-timesyncd[802]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 15 12:47:56 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 16 07:39:05 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 18 18:11:05 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 19 23:45:04 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 20 14:20:46 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 21 09:42:45 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 22 09:41:52 singold systemd-timesyncd[672]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 22 09:47:03 singold systemd-timesyncd[672]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). [...] It turns out that from all the A and records ntp.ubuntu.com resolves the, 2001:67c:1560:8003::c8 seems to be constantly down. This leads to time synchronisation problems for people using IPv6, as it seems timesyncd keeps returning to the same server over and over again, instead of trying the other ones DNS returns. A practical solution to this would be to simply remove 2001:67c:1560:8003::c8 from the DNS entry for ntp.ubuntu.com. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1766106 Title: ntp.ubuntu.com not reliable, but used in standard configuration Status in systemd package in Ubuntu: New Bug description: In systemd-timesyncd ntp.ubuntu.com is used as fall back ntp server. However, one of the addresses it resolves to is not available for quite some while: [...] Apr 14 07:37:42 singold systemd-timesyncd[773]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 14 08:10:45 singold systemd-timesyncd[773]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 15 08:20:48 singold systemd-timesyncd[802]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 15 12:47:56 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 16 07:39:05 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 18 18:11:05 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 19 23:45:04 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 20 14:20:46 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 21 09:42:45 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 22 09:41:52 singold systemd-timesyncd[672]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 22 09:47:03 singold systemd-timesyncd[672]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). [...] It turns out that from all the A and records ntp.ubuntu.com resolves the, 2001:67c:1560:8003::c8 seems to be constantly down. This leads to time synchronisation problems for people using IPv6, as it seems timesyncd keeps returning to the same server over and over again, instead of trying the other ones DNS returns. A practical solution to this would be to simply remove 2001:67c:1560:8003::c8 from the DNS entry for ntp.ubuntu.com. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766106/+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 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
Excuse me if that is a stupid question: Where can I get the package for trying it out? Or is the only way to way until it has propagated to the mirrors? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Invalid Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP VAProfileH264Main :VAEntrypointVLD VAProfileH264Main :VAEntrypointEncSlice VAProfileH264Main :VAEntrypointEncSliceLP VAProfileH264High :VAEntrypointVLD VAProfileH264High :VAEntrypointEncSlice VAProfileH264High :VAEntrypointEncSliceLP VAProfileH264MultiviewHigh :VAEntrypointVLD VAProfileH264MultiviewHigh :VAEntrypointEncSlice VAProfileH264StereoHigh :VAEntrypointVLD VAProfileH264StereoHigh :VAEntrypointEncSlice VAProfileVC1Simple :VAEntrypointVLD VAProfileVC1Main:VAEntrypointVLD VAProfileVC1Advanced:VAEntrypointVLD VAProfileNone :VAEntrypointVideoProc VAProfileJPEGBaseline :VAEntrypointVLD VAProfileJPEGBaseline :VAEntrypointEncPicture VAProfileVP8Version0_3 :VAEntrypointVLD VAProfileVP8Version0_3 :V
[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
great, multiverse is still better than some ppa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in libva package in Ubuntu: Invalid Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP VAProfileH264Main :VAEntrypointVLD VAProfileH264Main :VAEntrypointEncSlice VAProfileH264Main :VAEntrypointEncSliceLP VAProfileH264High :VAEntrypointVLD VAProfileH264High :VAEntrypointEncSlice VAProfileH264High :VAEntrypointEncSliceLP VAProfileH264MultiviewHigh :VAEntrypointVLD VAProfileH264MultiviewHigh :VAEntrypointEncSlice VAProfileH264StereoHigh :VAEntrypointVLD VAProfileH264StereoHigh :VAEntrypointEncSlice VAProfileVC1Simple :VAEntrypointVLD VAProfileVC1Main:VAEntrypointVLD VAProfileVC1Advanced:VAEntrypointVLD VAProfileNone :VAEntrypointVideoProc VAProfileJPEGBaseline :VAEntrypointVLD VAProfileJPEGBaseline :VAEntrypointEncPicture VAProfileVP8Version0_3 :VAEntrypointVLD VAProfileVP8Version0_3 :VAEntrypointEncSlice VAProfileHEVCMain :VAEntrypointVLD VAProfileHEVCMain
[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
@tjaalton looks like. This is with the ubuntu supplied libva and driver version 2.0.0 from github: > vainfo libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileVP9Profile0: VAEntrypointVLD VAProfileVP9Profile0: VAEntrypointEncSlice VAProfileVP9Profile2: VAEntrypointVLD -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in libva package in Ubuntu: Invalid Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain
[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
I also tried running uupdate on the existing intel-vaapi-driver package and build and install this. Worked right away. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in libva package in Ubuntu: Invalid Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP VAProfileH264Main :VAEntrypointVLD VAProfileH264Main :VAEntrypointEncSlice VAProfileH264Main :VAEntrypointEncSliceLP VAProfileH264High :VAEntrypointVLD VAProfileH264High :VAEntrypointEncSlice VAProfileH264High :VAEntrypointEncSliceLP VAProfileH264MultiviewHigh :VAEntrypointVLD VAProfileH264MultiviewHigh :VAEntrypointEncSlice VAProfileH264StereoHigh :VAEntrypointVLD VAProfileH264StereoHigh :VAEntrypointEncSlice VAProfileVC1Simple :VAEntrypointVLD VAProfileVC1Main:VAEntrypointVLD VAProfileVC1Advanced:VAEntrypointVLD VAProfileNone :VAEntrypointVideoProc VAProfileJPEGBaseline :VAEntrypointVLD VAProfileJPEGBaseline :VAEntrypointEncPicture VAProfileVP8Version0_3 :VAEntrypointVLD VAProfileVP8Version0_3 :VAEntrypointEncSlice VAProfile
[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
I should mention that updating libva is not necessary. It is enough to update the intel-vaapi-driver. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in libva package in Ubuntu: Invalid Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP VAProfileH264Main :VAEntrypointVLD VAProfileH264Main :VAEntrypointEncSlice VAProfileH264Main :VAEntrypointEncSliceLP VAProfileH264High :VAEntrypointVLD VAProfileH264High :VAEntrypointEncSlice VAProfileH264High :VAEntrypointEncSliceLP VAProfileH264MultiviewHigh :VAEntrypointVLD VAProfileH264MultiviewHigh :VAEntrypointEncSlice VAProfileH264StereoHigh :VAEntrypointVLD VAProfileH264StereoHigh :VAEntrypointEncSlice VAProfileVC1Simple :VAEntrypointVLD VAProfileVC1Main:VAEntrypointVLD VAProfileVC1Advanced:VAEntrypointVLD VAProfileNone :VAEntrypointVideoProc VAProfileJPEGBaseline :VAEntrypointVLD VAProfileJPEGBaseline :VAEntrypointEncPicture VAProfileVP8Version0_3 :VAEntrypointVLD VAProfileVP8Version0_3 :VAEntrypointEncSlice VAProfileHEVCMain
[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
** Also affects: libva (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: New Status in libva package in Ubuntu: New Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP VAProfileH264Main :VAEntrypointVLD VAProfileH264Main :VAEntrypointEncSlice VAProfileH264Main :VAEntrypointEncSliceLP VAProfileH264High :VAEntrypointVLD VAProfileH264High :VAEntrypointEncSlice VAProfileH264High :VAEntrypointEncSliceLP VAProfileH264MultiviewHigh :VAEntrypointVLD VAProfileH264MultiviewHigh :VAEntrypointEncSlice VAProfileH264StereoHigh :VAEntrypointVLD VAProfileH264StereoHigh :VAEntrypointEncSlice VAProfileVC1Simple :VAEntrypointVLD VAProfileVC1Main:VAEntrypointVLD VAProfileVC1Advanced:VAEntrypointVLD VAProfileNone :VAEntrypointVideoProc VAProfileJPEGBaseline :VAEntrypointVLD VAProfileJPEGBaseline :VAEntrypointEncPicture VAProfileVP8Version0_3 :VAEntrypointVLD VAProfileVP8Version0_3 :VAEntrypointEncSlice VAProfileHEVCMain :VAEntrypointVLD V
[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
Still Happens in 4.10.0-38-generic. I love ubuntu so much that I have installed as second operating system in my macbook pro. In MacOs I used to connect to Bluetooth speaker with out any problem and audio plays without any stuck or anyting. Here in Ubuntu its not even connecting properly in native bluetooth. I have installed Blueman and able to connect after many tries and even after that I am not able to play anything properly. Ubuntu team please fix this issue. I cant able to full use Ubuntu as my primary machine. Dont make me hate 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/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
This is not just Ubuntu-Gnome, Unity is the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
** Also affects: resolvconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: New Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1671964] Re: DNS fails after reconnecting to a VPN
Restarting NetworkManager didn't work for me. DNS lookups for my network would fail REFUSED if queried against 127.0.1.1(dnsmasq) but work fine if I queried google's dns 8.8.8.8. What did work was to modify the VPN connection and change the ipv4 configuration to address only, then manually add the routes I needed for the VPN (I did a broadstroke and routed 10.0.0.0/8 to the vpn tun) -- 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/1671964 Title: DNS fails after reconnecting to a VPN Status in network-manager package in Ubuntu: Confirmed Bug description: Since update 1.2.2-0ubuntu0.16.04.3 of network-manager, when I reconnect (i.e. connect, disconnect, connect) to a VPN (OpenVPN), DNS resolution stops working. Workaround: systemctl restart NetworkManager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671964/+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 1577208] [NEW] light-locker-settings crashes
Public bug reported:
light-locker-settings is a python program (available from the
'Preferences' menu) that uses a third-party module called 'psutils'.
This module at one point had a method named 'get_pid_list()' which was
renamed to 'pids()'. The old name was deprecated at least two years ago
and then completely removed in the 3.0 release of psutils last June.
light-locker-settings uses the old method name in line 219 of light-
locker-settings.py, resulting in the following exception stack:
london@england:~$ light-locker-settings
/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py:29:
PyGIWarning: Gtk was imported without specifying a version first. Use
gi.require_version('Gtk', '3.0') before import to ensure that the right version
gets loaded.
from gi.repository import Gtk, GLib, Gio
Traceback (most recent call last):
File
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
line 697, in
main = LightLockerSettings()
File
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
line 98, in __init__
self.init_settings()
File
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
line 454, in init_settings
if self.check_running_process("xfce4-power-manager"):
File
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
line 219, in check_running_process
for pid in psutil.get_pid_list():
AttributeError: 'module' object has no attribute 'get_pid_list'
london@england:~$
The easy fix is to simply replace 'get_pid_list' with 'pids'.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: LXDE
Date: Sun May 1 13:20:17 2016
InstallationDate: Installed on 2016-05-01 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
LightdmConfig:
[Seat:*]
autologin-guest=false
autologin-user=london
autologin-user-timeout=0
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-05-01 (0 days ago)
** Affects: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1577208
Title:
light-locker-settings crashes
Status in lightdm package in Ubuntu:
New
Bug description:
light-locker-settings is a python program (available from the
'Preferences' menu) that uses a third-party module called 'psutils'.
This module at one point had a method named 'get_pid_list()' which was
renamed to 'pids()'. The old name was deprecated at least two years
ago and then completely removed in the 3.0 release of psutils last
June. light-locker-settings uses the old method name in line 219 of
light-locker-settings.py, resulting in the following exception stack:
london@england:~$ light-locker-settings
/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py:29:
PyGIWarning: Gtk was imported without specifying a version first. Use
gi.require_version('Gtk', '3.0') before import to ensure that the right version
gets loaded.
from gi.repository import Gtk, GLib, Gio
Traceback (most recent call last):
File
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
line 697, in
main = LightLockerSettings()
File
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
line 98, in __init__
self.init_settings()
File
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
line 454, in init_settings
if self.check_running_process("xfce4-power-manager"):
File
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
line 219, in check_running_process
for pid in psutil.get_pid_list():
AttributeError: 'module' object has no attribute 'get_pid_list'
london@england:~$
The easy fix is to simply replace 'get_pid_list' with 'pids'.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: LXDE
Date: Sun May 1 13:20:17 2016
InstallationDate: Installed on 2016-05-01 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
LightdmConfig:
[Seat:*]
autologin-guest=false
autologin-user=london
autologin-user-timeout=0
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-05-01 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1577208/
[Touch-packages] [Bug 340095] Re: Race condition with two concurrent adduser processes
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect and any other logs that are relevant for this particular issue. ** Changed in: adduser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/340095 Title: Race condition with two concurrent adduser processes Status in adduser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 8.04.2 Release:8.04 adduser: Installed: 3.105ubuntu1 Candidate: 3.105ubuntu1 Version table: *** 3.105ubuntu1 0 500 file: hardy/main Packages 100 /var/lib/dpkg/status Two adduser processes were run at the same time by different administrators. This triggers a race condition where they can both select the same UID and therefore the second process fails. While an obscure race condition, it still does happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/340095/+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 1055272] Re: valgrind
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
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/1055272
Title:
valgrind
Status in mesa package in Ubuntu:
Incomplete
Bug description:
The following program produces 55 errors with valgrind:
int
main()
{
Display* display = XOpenDisplay(0);
int major;
int minor;
glXQueryVersion(display, &major, &minor);
XCloseDisplay(display);
}
51 instances in drm_intel_bufmgr_gem_init: Conditional jump or move depends
on uninitialised value(s)
2 instances in drm_intel_bufmgr_gem_init: Syscall param ioctl(generic) points
to uninitialised byte(s)
2 instances in fun:drmCommandWriteRead: Syscall param ioctl(generic) points
to uninitialised byte(s)
The corresponding suppression entries are:
{
OpenGL-bad-ioctl
Memcheck:Param
ioctl(generic)
fun:ioctl
fun:drmIoctl
fun:drm_intel_bufmgr_gem_init
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
}
{
OpenGL-bad-ioctl-2
Memcheck:Param
ioctl(generic)
fun:ioctl
fun:drmIoctl
fun:drmCommandWriteRead
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
}
{
OpenGL-uninitialized-jump
Memcheck:Cond
fun:drm_intel_bufmgr_gem_init
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
obj:/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1055272/+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 1506336] Re: utopic repositories have been wiped out
Thank you for reporting this to Ubuntu. 14.10 reached EOL on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases You can find the old repo here, but it is no longer a supported distribution. Please upgrade. http://old-releases.ubuntu.com/ubuntu/dists/utopic/ Thanks ** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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/1506336 Title: utopic repositories have been wiped out Status in apport package in Ubuntu: Incomplete Bug description: utopic repositories have been wiped out from main repo servers. Please, restore them. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: apport 2.14.7-0ubuntu8.5 Uname: Linux 4.1.0-pf1+ x86_64 ApportLog: ApportVersion: 2.14.7-0ubuntu8.5 Architecture: amd64 CurrentDesktop: KDE Date: Thu Oct 15 08:46:08 2015 InstallationDate: Installed on 2014-12-01 (317 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1506336/+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 1497741] Re: package mime-support 3.54ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 255
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Changed in: mime-support (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1497741 Title: package mime-support 3.54ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 255 Status in mime-support package in Ubuntu: Incomplete Bug description: plank dock no open, and i try remove in terminal. an have error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: mime-support 3.54ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 AptOrdering: plank: Remove Architecture: amd64 Date: Sun Sep 20 09:47:57 2015 DuplicateSignature: package:mime-support:3.54ubuntu1.1:el subproceso instalado el script post-installation devolvió el código de salida de error 255 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 255 InstallationDate: Installed on 2015-09-19 (1 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: mime-support Title: package mime-support 3.54ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 255 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1497741/+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 1499907] Re: package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: η υποδιεργασία installed pre-removal script επέστρεψε κατάσταση λάθους 1
Sounds more like a process issue rather than a bug. ** Changed in: avahi (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/avahi/+question/272426 -- 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/1499907 Title: package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: η υποδιεργασία installed pre-removal script επέστρεψε κατάσταση λάθους 1 Status in avahi package in Ubuntu: Invalid Bug description: sudo apt-get purge apache2* bind9* samba* ProblemType: Package DistroRelease: Ubuntu 15.04 Package: avahi-dnsconfd 0.6.31-4ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Sat Sep 26 01:28:43 2015 DpkgTerminalLog: Removing account-plugin-salut (3.12.9-1ubuntu1.1) ... Removing avahi-dnsconfd (0.6.31-4ubuntu4) ... Job for avahi-daemon.socket canceled. dpkg: error processing package avahi-dnsconfd (--purge): η υποδιεργασία installed pre-removal script επέστρεψε κατάσταση λάθους 1 DuplicateSignature: package:avahi-dnsconfd:0.6.31-4ubuntu4:η υποδιεργασία installed pre-removal script επέστρεψε κατάσταση λάθους 1 ErrorMessage: η υποδιεργασία installed pre-removal script επέστρεψε κατάσταση λάθους 1 InstallationDate: Installed on 2015-03-19 (190 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: η υποδιεργασία installed pre-removal script επέστρεψε κατάσταση λάθους 1 UpgradeStatus: Upgraded to vivid on 2015-05-01 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1499907/+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 1500085] Re: package python3 3.4.3-1 failed to install/upgrade: podproces nainštalovaný skript pre-removal vrátil chybový kód 127
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Changed in: python3-defaults (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1500085 Title: package python3 3.4.3-1 failed to install/upgrade: podproces nainštalovaný skript pre-removal vrátil chybový kód 127 Status in python3-defaults package in Ubuntu: Incomplete Bug description: I haven't got any. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: python3 3.4.3-1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Fri Sep 25 18:36:01 2015 DuplicateSignature: package:python3:3.4.3-1:podproces nainštalovaný skript pre-removal vrátil chybový kód 127 ErrorMessage: podproces nainštalovaný skript pre-removal vrátil chybový kód 127 InstallationDate: Installed on 2013-12-10 (654 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: python3-defaults Title: package python3 3.4.3-1 failed to install/upgrade: podproces nainštalovaný skript pre-removal vrátil chybový kód 127 UpgradeStatus: Upgraded to vivid on 2015-05-01 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1500085/+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 1500332] Re: package isc-dhcp-server 4.3.1-5ubuntu2.2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 100
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Changed in: isc-dhcp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1500332 Title: package isc-dhcp-server 4.3.1-5ubuntu2.2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 100 Status in isc-dhcp package in Ubuntu: Incomplete Bug description: ? sometihng goes wron on do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: isc-dhcp-server 4.3.1-5ubuntu2.2 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Fri Sep 25 21:34:24 2015 DhServerLeases: ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 100 InstallationDate: Installed on 2015-04-06 (174 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcCmdline: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/hostname--vg-root ro splash=silent nomodeset=1 memmap=0xf100 pci=nocrs video=uvesafb:1280x1024,mtrr:3,ywrap SourcePackage: isc-dhcp Title: package isc-dhcp-server 4.3.1-5ubuntu2.2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 100 UpgradeStatus: Upgraded to wily on 2015-09-25 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1500332/+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 1500545] Re: package dconf-editor (not installed) failed to install/upgrade: pacote dconf-editor não está pronto para configuração não posso configurar (estado atual 'half-insta
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Changed in: d-conf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1500545 Title: package dconf-editor (not installed) failed to install/upgrade: pacote dconf-editor não está pronto para configuração não posso configurar (estado atual 'half-installed') Status in d-conf package in Ubuntu: Incomplete Bug description: package dconf-editor (not installed) failed to install/upgrade: pacote dconf-editor não está pronto para configuração não posso configurar (estado atual 'half-installed') ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dconf-editor (not installed) ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-49-generic i686 ApportVersion: 2.14.1-0ubuntu3.13 AptOrdering: dconf-editor: Configure Architecture: i386 Date: Mon Sep 28 14:39:33 2015 DpkgTerminalLog: dpkg: error processing package dconf-editor (--configure): pacote dconf-editor não está pronto para configuração não posso configurar (estado atual 'half-installed') DuplicateSignature: package:dconf-editor:(not installed):pacote dconf-editor não está pronto para configuração não posso configurar (estado atual 'half-installed') ErrorMessage: pacote dconf-editor não está pronto para configuração não posso configurar (estado atual 'half-installed') InstallationDate: Installed on 2015-03-27 (185 days ago) InstallationMedia: Lubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: d-conf Title: package dconf-editor (not installed) failed to install/upgrade: pacote dconf-editor não está pronto para configuração não posso configurar (estado atual 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1500545/+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 1502438] Re: package avahi-daemon 0.6.31-4ubuntu4 failed to install/upgrade: 子进程 已安装 pre-removal 脚本 返回错误状态 1
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Changed in: avahi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1502438 Title: package avahi-daemon 0.6.31-4ubuntu4 failed to install/upgrade: 子进程 已安装 pre-removal 脚本 返回错误状态 1 Status in avahi package in Ubuntu: Incomplete Bug description: 正在卸载 avahi-daemon (0.6.31-4ubuntu4) ... Job for avahi-daemon.service canceled. invoke-rc.d: initscript avahi-daemon, action "stop" failed. dpkg: 处理软件包 avahi-daemon (--purge)时出错： 子进程 已安装 pre-removal 脚本 返回错误状态 1 update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults 在处理时有错误发生： avahi-daemon E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 15.04 Package: avahi-daemon 0.6.31-4ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Sat Oct 3 21:12:04 2015 DuplicateSignature: package:avahi-daemon:0.6.31-4ubuntu4:子进程 已安装 pre-removal 脚本 返回错误状态 1 ErrorMessage: 子进程 已安装 pre-removal 脚本 返回错误状态 1 InstallationDate: Installed on 2014-12-18 (288 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: avahi Title: package avahi-daemon 0.6.31-4ubuntu4 failed to install/upgrade: 子进程 已安装 pre-removal 脚本 返回错误状态 1 UpgradeStatus: Upgraded to vivid on 2015-04-29 (157 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1502438/+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 1503343] Re: had a bunch of probs not sure what from
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1503343 Title: had a bunch of probs not sure what from Status in xorg package in Ubuntu: Incomplete Bug description: had a previous virus removed and poof not sure whats missing now ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 6 07:49:35 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF100 [GeForce GTX 470] [10de:06cd] (rev a3) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:079f] InstallationDate: Installed on 2015-12-01 (-55 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard Bus 002 Device 003: ID 1532:0016 Razer USA, Ltd DeathAdder Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: XFX XFX nForce 790i Ultra 3-Way SLI ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=2670867f-b36e-445b-85e7-9f56874fd599 ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: XFX nForce 790i Ultra 3-Way SLI dmi.board.vendor: XFX dmi.board.version: 1 dmi.chassis.type: 3 dmi.chassis.vendor: XFX dmi.chassis.version: XFX nForce 790i Ultra 3-Way SLI dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/12/2008:svnXFX:pnXFXnForce790iUltra3-WaySLI:pvr1:rvnXFX:rnXFXnForce790iUltra3-WaySLI:rvr1:cvnXFX:ct3:cvrXFXnForce790iUltra3-WaySLI: dmi.product.name: XFX nForce 790i Ultra 3-Way SLI dmi.product.version: 1 dmi.sys.vendor: XFX version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Oct 6 07:27:06 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputRazer Razer DeathAdder MOUSE, id 8 inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 9 inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3~trusty1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1503343/+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 1056727] Re: reboot, poweroff, ... missing
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect and any other logs that are relevant for this particular issue. ** Changed in: busybox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1056727 Title: reboot, poweroff, ... missing Status in busybox package in Ubuntu: Incomplete Bug description: Hi, as opposed to the upstream version (and the debian wheezy version and the ubuntu hardy version) applets like reboot, poweroff and so on are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1056727/+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 873868] Re: sqlite3 does not run after upgrading Ubtuntu to Oneiric
Thank you for reporting this bug to Ubuntu. 11.10 reached EOL on May 9, 2013. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases However, this sounds like one of the sqlite3 packages may have been installed from source and not been kept upto date with the Ubuntu repo's. Use this link as a starting point: http://stackoverflow.com/questions/25335989/sqlite-header-and-source- version-mismatch-in-linux-ubuntu-12-04-lts Do feel free to report any other bugs you may find. ** Changed in: sqlite3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/873868 Title: sqlite3 does not run after upgrading Ubtuntu to Oneiric Status in sqlite3 package in Ubuntu: Incomplete Bug description: The sqlite3 command-line program worked perfectly under Hardy, Intrepid, Jaunty, Karmic, Lucid, Maverick and Natty. Immediately after the upgrade to Oneiric, sqlite3 is broken: me@box:~$ sqlite3 --version SQLite header and source version mismatch 2010-01-05 15:30:36 28d0d7710761114a44a1a3a425a6883c661f06e7 2011-06-23 19:49:22 4374b7e83ea0a3fbc3691f9c0c936272862f32f2 The following packages are all installed and up-to-date: me@box:~$ dpkg --get-selections | egrep "sqlite*" libaprutil1-dbd-sqlite3 install libmono-sqlite2.0-cil install libmono-sqlite4.0-cil install libqt4-sql-sqlite install libsqlite3-0 install libsqlite3-0:i386 install libsqlite3-0-dbg install libsqlite3-devinstall sqlite3 install sqlite3-doc install sqlitebrowser install sqliteman install sqliteman-doc install Any ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/873868/+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 772302] Re: totem on fresh install of lucid doesnt show video
Thank you for reporting this bug to Ubuntu. 10.04LTS reached EOL on May 9, 2013. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again. Do feel free to report any other bugs you may find. ** Changed in: gstreamer0.10 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/772302 Title: totem on fresh install of lucid doesnt show video Status in gstreamer0.10 package in Ubuntu: Incomplete Bug description: totem doesnt play video files properly in lucid lynx.i see video sometimes and sometimes it disappears ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libgstreamer0.10-0 0.10.28-1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Thu Apr 28 17:01:59 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANG=en_IN SHELL=/bin/bash SourcePackage: gstreamer0.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/772302/+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
