[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly
I have the same issue. I may be wrong, but it seem to me that it's related to the following DHCP options : DHCP option 1 : [SubnetMask] DHCP option 121 : classless static route [DestCIDR] [Gateway] When DestCIDR is within the subnet, the gateway is dropped by systemd-networkd : the route is added, without gateway. @Pedro Lopes : does this match your occurrence of the issue. Note that dhclient does not have this bug : running dhclient adds the correct routes. Unfortunately for me, the concerned machines are in production. So further testing is not easy. -- 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/2009743 Title: networkd: classless routes served by DHCP are created incorrectly Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading 20.04 systems to 22.04, the classless routes served via DHCP are not being registered correctly - they are missing the gateway address. Expected routes - these are taken from a 20.04 system on the same network: $ ip route default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100 10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12 10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100 10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100 Actual routes - these are the routes created in one of the affected 22.04 systems: $ ip route default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100 8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100 10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100 10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" gateway address, and therefore don't work. (For some reason there are also static routes created for DNS server (8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but harmless.) Both the working and non-working systems are being managed by netplan. The non-working system has a bonded interface but I have checked that is not the cause of the problem - using a physical interface directly has the same result. I have attached the files /etc/netplan/00-installer-config.yaml and /run/systemd/network/10-netplan-bond0.network of the affected system. Affected system: Ubuntu version: Ubuntu 22.04.2 LTS systemd version: 249.11-0ubuntu3.6 Older system not affected: Ubuntu version: Ubuntu 20.04.5 LTS systemd version: 245.4-4ubuntu3.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009743/+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 1928989] Re: expiring trust anchor compatibility issue
@xnox I'm working on an update for Debian Jessie (1.0.1t) as part of Debian ELTS. I got one test suite failure in 'verify_extra_test' that I fixed by partially reverting https://github.com/openssl/openssl/commit/cb22d2ae5a5b6069dbf66dbcce07223ac15a16de (hence aligning the test with later OpenSSL versions). Attached is my current debdiff, I'm open to exchanging code reviews :) ** Attachment added: "debdiff.txt" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1928989/+attachment/5525428/+files/debdiff.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1928989 Title: expiring trust anchor compatibility issue Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Trusty: Confirmed Status in openssl source package in Xenial: Fix Released Bug description: [Impact] * openssl fails to talk to letsencrypt website past September 2021, despite trusting the letsencrypt root certificate. [Test Plan] * Import staging cert equivalent to ISRG Root X1 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem * Import expired staging cert equivalen tto DST Root CA X3 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem * Test connectivity to the expired-root-ca test website https://expired-root-ca-test.germancoding.com setup: apt install openssl ca-certificates wget wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem cat letsencrypt-stg-root-x1.pem letsencrypt-stg-root-dst.pem >> ca.pem test case: openssl s_client -connect expired-root-ca-test.germancoding.com:443 -servername expired-root-ca-test.germancoding.com -verify 1 -verifyCAfile ca.pem bad result: connection failed verify depth is 1 CONNECTED(0003) depth=3 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Doctored Durian Root CA X3 verify error:num=10:certificate has expired notAfter=Jan 30 14:01:15 2021 GMT 140672978626200:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264: good result: connection successful verify depth is 1 CONNECTED(0003) depth=2 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Pretend Pear X1 verify return:1 depth=1 C = US, O = (STAGING) Let's Encrypt, CN = (STAGING) Artificial Apricot R3 verify return:1 depth=0 CN = expired-root-ca-test.germancoding.com verify return:1 --- Certificate chain 0 s:/CN=expired-root-ca-test.germancoding.com i:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 1 s:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 2 s:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Doctored Durian Root CA X3 --- Server certificate -BEGIN CERTIFICATE- Connection should be successful and trusted with correctly working openssl s_client that can manage to ignore expired CA, and build a valid trust path using non-expired CA in the chain. [Testcase #2] $ sudo apt install ca-certificates wget faketime # Good connectivity $ wget -O /dev/null https://canonical.com --2021-07-13 11:54:20-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[>] 30.21K --.-KB/sin 0.001s 2021-07-13 11:54:20 (22.3 MB/s) - '/dev/null' saved [30933/30933] # Jump to october to experience failure $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. ERROR: cannot verify canonical.com's certificate, issued by 'CN=R3,O=Let\'s Encrypt,C=US': Issued certificate has expired. To connect to canonical.com insecurely, use `--no-check-certificate'. # upgrade to new openssl, to see that connectivity is restored, even in october $ dpkg-query -W libssl1.0.0 libssl1.0.0:amd64 1.0.2g-1ubuntu4.20 $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2c, 2001:67c:1360:8001::2b, 91.18
[Touch-packages] [Bug 1886493] [NEW] Galaxy Book Ion, sof-hda-dsp detected but no soound (ubuntu 20.04)
Public bug reported: Ubuntu Release : ubuntu 20.04 LTS release 20.04 Driver : alsa-base : 1.0.25+dfsg-0ubuntu5 On Galaxy Book Ion (model NP950XCJ-X01, from 2020) The audio device (AKG Stereo Speakers) is detected as : sof-hda-dsp Profile : Play HiFi quality music But I get no sound either from the speakers of headphone jack. Guessing a driver issue, hardware not properly detected. Note : Laptop was provided with windows10, sound is ok on windows (so it's not an hardware issue). Thanks. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu Release : ubuntu 20.04 LTS release 20.04 Driver : alsa-base : 1.0.25+dfsg-0ubuntu5 On Galaxy Book Ion (model NP950XCJ-X01, from 2020) The audio device (AKG Stereo Speakers) is detected as : sof-hda-dsp Profile : Play HiFi quality music But I get no sound either from the speakers of headphone jack. Guessing a driver issue, hardware not properly detected. - Note : Laptop was provided with windows10, no sound ok here (so it's not - an hardware issue). - + Note : Laptop was provided with windows10, sound is ok on windows (so + it's not an hardware issue). Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1886493 Title: Galaxy Book Ion, sof-hda-dsp detected but no soound (ubuntu 20.04) Status in alsa-driver package in Ubuntu: New Bug description: Ubuntu Release : ubuntu 20.04 LTS release 20.04 Driver : alsa-base : 1.0.25+dfsg-0ubuntu5 On Galaxy Book Ion (model NP950XCJ-X01, from 2020) The audio device (AKG Stereo Speakers) is detected as : sof-hda-dsp Profile : Play HiFi quality music But I get no sound either from the speakers of headphone jack. Guessing a driver issue, hardware not properly detected. Note : Laptop was provided with windows10, sound is ok on windows (so it's not an hardware issue). Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886493/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
It work ! Thank-you so much :-) ● State: routable Address: 192.168.2.1 on enp2s0 192.168.1.166 on br1 192.168.122.1 on virbr0 Gateway: 192.168.1.1 (Ubiquiti Networks Inc.) on br1 DNS: 192.168.1.11 192.168.1.12 1.1.1.1 Search Domains: maison.com -- Reboot -- Apr 27 11:31:09 leblancs-Z170X-UD3 systemd[1]: Starting Network Service... Apr 27 11:31:10 leblancs-Z170X-UD3 systemd-networkd[2621]: br1: netdev ready Apr 27 11:31:10 leblancs-Z170X-UD3 systemd-networkd[2621]: bond0: netdev ready Apr 27 11:31:10 leblancs-Z170X-UD3 systemd-networkd[2621]: Enumeration completed Apr 27 11:31:10 leblancs-Z170X-UD3 systemd[1]: Started Network Service. Apr 27 11:31:10 leblancs-Z170X-UD3 systemd-networkd[2621]: br1: Link UP Apr 27 11:31:10 leblancs-Z170X-UD3 systemd-networkd[2621]: br1: Gained carrier Apr 27 11:31:11 leblancs-Z170X-UD3 systemd-networkd[2621]: br1: Lost carrier Apr 27 11:31:11 leblancs-Z170X-UD3 systemd-networkd[2621]: enp2s0: Link UP Apr 27 11:31:11 leblancs-Z170X-UD3 systemd-networkd[2621]: enp0s31f6: Link UP Apr 27 11:31:11 leblancs-Z170X-UD3 systemd-networkd[2621]: enp14s0f0: Link UP Apr 27 11:31:11 leblancs-Z170X-UD3 systemd-networkd[2621]: bond0: Link UP Apr 27 11:31:13 leblancs-Z170X-UD3 systemd-networkd[2621]: enp14s0f0: Gained carrier Apr 27 11:31:13 leblancs-Z170X-UD3 systemd-networkd[2621]: bond0: Gained carrier Apr 27 11:31:13 leblancs-Z170X-UD3 systemd-networkd[2621]: br1: Gained carrier Apr 27 11:31:15 leblancs-Z170X-UD3 systemd-networkd[2621]: veth29aacaed: Link UP Apr 27 11:31:15 leblancs-Z170X-UD3 systemd-networkd[2621]: enp0s31f6: Gained carrier Apr 27 11:31:16 leblancs-Z170X-UD3 systemd-networkd[2621]: veth29aacaed: Gained carrier Apr 27 11:31:16 leblancs-Z170X-UD3 systemd-networkd[2621]: veth9b9e65cf: Link UP Apr 27 11:31:17 leblancs-Z170X-UD3 systemd-networkd[2621]: veth9b9e65cf: Gained carrier Apr 27 11:31:17 leblancs-Z170X-UD3 systemd-networkd[2621]: enp2s0: Gained carrier Apr 27 11:31:22 leblancs-Z170X-UD3 systemd-networkd[2621]: rtnl: received neighbor for link '14' we don't know about, ignoring. Apr 27 11:31:22 leblancs-Z170X-UD3 systemd-networkd[2621]: rtnl: received neighbor for link '14' we don't know about, ignoring. Apr 27 11:31:22 leblancs-Z170X-UD3 systemd-networkd[2621]: rtnl: received neighbor for link '14' we don't know about, ignoring. Apr 27 11:31:22 leblancs-Z170X-UD3 systemd-networkd[2621]: rtnl: received neighbor for link '14' we don't know about, ignoring. Apr 27 11:31:22 leblancs-Z170X-UD3 systemd-networkd[2621]: virbr0-nic: Link UP Apr 27 11:31:22 leblancs-Z170X-UD3 systemd-networkd[2621]: virbr0-nic: Gained carrier Apr 27 11:31:22 leblancs-Z170X-UD3 systemd-networkd[2621]: virbr0: Link UP Apr 27 11:31:23 leblancs-Z170X-UD3 systemd-networkd[2621]: virbr0-nic: Link DOWN Apr 27 11:31:23 leblancs-Z170X-UD3 systemd-networkd[2621]: virbr0-nic: Lost carrier Apr 27 11:31:23 leblancs-Z170X-UD3 systemd-networkd[2621]: enp2s0: Lost carrier Apr 27 11:31:28 leblancs-Z170X-UD3 systemd-networkd[2621]: enp2s0: Gained carrier -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Not SRU - N/A [scope] This is not reproducable on Eoan or Bionic; this is needed only for Focal. [original description] Fresh
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
Here is the output from networkctl root@leblancs-Z170X-UD3:~# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp14s0f0etherenslavedconfigured 3 enp14s0f1etheroff unmanaged 4 enp0s31f6etherenslavedconfigured 5 enp2s0 etherroutableconfigured 6 enp15s0f0etheroff unmanaged 7 enp15s0f1etheroff unmanaged 8 bond0bond enslavedconfigured 9 br1 bridge routableconfigured 11 veth29aacaed ethercarrier unmanaged 13 veth9b9e65cf ethercarrier unmanaged 14 virbr0 bridge no-carrier unmanaged 15 virbr0-nic etheroff unmanaged 13 links listed. -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Not SRU - N/A [scope] This is not reproducable on Eoan or Bionic; this is needed only for Focal. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 979 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 4.1M CGroup: /system.slice/systemd-networkd.service └─979 /lib/systemd/systemd-networkd Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for link '5' we don't know about, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
Doing the test now, will report back in 5 minutes. -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Not SRU - N/A [scope] This is not reproducable on Eoan or Bionic; this is needed only for Focal. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 979 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 4.1M CGroup: /system.slice/systemd-networkd.service └─979 /lib/systemd/systemd-networkd Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for link '5' we don't know about, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring. systemctl restart systemd-networkd resolved the issue and a systemctl status systemd-network producessystemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 1650 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 1.6M CGroup: /system.slice/systemd-networkd.service └─1650 /lib/systemd/systemd-networkd Jan 26 16:39:28 firebolt systemd[1]: Starting Network Service... Jan
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
If that help here is my netplan setup that was working perfect in 18.04,
19.04, 19.10
network:
version: 2
renderer: networkd
ethernets:
enp0s31f6:
dhcp4: false
dhcp6: false
match:
macaddress: 1c:1b:0d:61:85:40
mtu: 9000
enp12s0f0:
dhcp4: false
dhcp6: false
match:
macaddress: 00:1b:21:66:6c:c8
mtu: 9000
enp2s0:
addresses:
- 192.168.2.1/24
dhcp4: false
dhcp6: false
match:
macaddress: 00:17:b6:00:97:8a
mtu: 9000
vlans: {}
wifis: {}
bonds:
bond0:
interfaces: [enp0s31f6, enp12s0f0]
mtu: 9000
parameters:
lacp-rate: slow
mode: 802.3ad
transmit-hash-policy: layer2+3
bridges:
br1:
link-local: [ ]
addresses: [ 192.168.1.166/24 ]
dhcp4: false
dhcp6: false
gateway4: 192.168.1.1
interfaces: [ bond0 ]
nameservers:
search: [maison.com]
addresses: [192.168.1.11, 192.168.1.12, 1.1.1.1]
--
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/1860926
Title:
Ubuntu 20.04 Systemd fails to configure bridged network
Status in systemd package in Ubuntu:
Confirmed
Status in systemd source package in Focal:
Confirmed
Bug description:
[impact]
A bridged interface with static ipv4 address and gateway configuration
will fail to properly add the route via the gateway, leaving the
system without a globally working network.
[test case]
On a Focal system, remove all network configuration and create this
netplan:
network:
version: 2
renderer: networkd
ethernets:
enp4s0:
dhcp4: false
bridges:
br0:
interfaces: [enp4s0]
dhcp4: no
addresses: [192.168.0.4/24]
gateway4: 192.168.0.1
nameservers:
search: [mydomain]
addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
Replace the interface name 'enp4s0' with the actual interface name on
the test system.
Reboot the system, and check the route to the gateway, which will be
missing:
root@lp1860926-f:~# ip r
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4
The route is expected to be present, e.g.:
ubuntu@lp1860926-e:~$ ip r
default via 192.168.0.1 dev br0 proto static
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4
[regression potential]
Not SRU - N/A
[scope]
This is not reproducable on Eoan or Bionic; this is needed only for
Focal.
[original description]
Freshly installed Ubuntu 20.04 fully patched to days date with static
IP address works fine and survives a reboot
network:
version: 2
renderer: networkd
ethernets:
enp4s0:
dhcp4: false
addresses: [192.168.0.4/24]
gateway4: 192.168.0.1
nameservers:
search: [mydomain]
addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
however when converted to a bridged network for kvm
network:
version: 2
renderer: networkd
ethernets:
enp4s0:
dhcp4: false
bridges:
br0:
interfaces: [enp4s0]
dhcp4: no
addresses: [192.168.0.4/24]
gateway4: 192.168.0.1
nameservers:
search: [mydomain]
addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
will not survive a reboot and required systemd-network to be restarted or
@reboot /usr/sbin/netplan apply
added to the crontab
after a reboot the network can not b eaccseed and a
systemctl status systemd-networkd produces
systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled;
vendor preset: enabled)
Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
TriggeredBy: ● systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
Main PID: 979 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 57662)
Memory: 4.1M
CGroup: /system.slice/systemd-networkd.service
└─979 /lib/systemd/systemd-networkd
Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for
link '5' we don't know about, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic:
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
Cloundinit is not install neither networkmanager !!! :-( -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Not SRU - N/A [scope] This is not reproducable on Eoan or Bionic; this is needed only for Focal. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 979 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 4.1M CGroup: /system.slice/systemd-networkd.service └─979 /lib/systemd/systemd-networkd Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for link '5' we don't know about, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring. systemctl restart systemd-networkd resolved the issue and a systemctl status systemd-network producessystemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 1650 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 1.6M CGroup: /system.slice/systemd-networkd.service └─1650 /lib/systemd/systemd-networkd Jan 26 16:39:28 firebolt systemd[1]: Starting Network Service...
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
I have this exact bug after upgrading from 19.10 workstation to 20.04, please notice I use the workstation has a LXD container server, all my nfs mount point failed to mount, and I also never get an Ip address on my bridge interface, to fix this manually I have todo netplan apply and mount -a ! -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Not SRU - N/A [scope] This is not reproducable on Eoan or Bionic; this is needed only for Focal. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 979 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 4.1M CGroup: /system.slice/systemd-networkd.service └─979 /lib/systemd/systemd-networkd Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for link '5' we don't know about, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring. systemctl restart systemd-networkd resolved the issue and a systemctl status systemd-network producessystemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 1650 (systemd-network) Status: "Processing
[Touch-packages] [Bug 1832689] Re: TPM certification tests now failing after update to 1.1.1 (test_output_formats)
** Changed in: plainbox-provider-tpm2 Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832689 Title: TPM certification tests now failing after update to 1.1.1 (test_output_formats) Status in Provider for Plainbox - TPM2: Invalid Status in openssl package in Ubuntu: Expired Bug description: The certification team is running automated tests for every supported ubuntu-core device for every new core18 snap update. The recent core18 includes the openssl 1.1.1 update and seems to have caused regressions in the TPM test suite (for the dawson-i device). I was able to dig out the test suite itself, with the failing test code located here: https://git.launchpad.net/plainbox-provider- tpm2/tree/data/tpm2-tools-3.0.4/test/system/test_output_formats.sh Test failure log seems to be this: openssl rsa -pubin -inform "$fmt" -text -in "$this_key" &> /dev/null on line 95 failed: 1 The certification team will follow up with more information. This is currently causing core18 promotions to be blocked (and there has been over a month without a new core18 stable snap). Setting to critical. I noticed a follow-up SRU for openssl with fix for LP: #1828215 and was wondering if it might be related? To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-tpm2/+bug/1832689/+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 1830146] Re: Checkbox detect an extra webcam "video1"
** Changed in: checkbox-support Status: In Progress => Fix Committed -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Checkbox Support Library: Fix Committed Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-support/+bug/1830146/+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 1830146] Re: Checkbox detect an extra webcam "video1"
** Changed in: checkbox-support Status: Confirmed => In Progress -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Checkbox Support Library: In Progress Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-support/+bug/1830146/+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 1830146] Re: Checkbox detect an extra webcam "video1"
** Changed in: checkbox-support Status: In Progress => Fix Committed -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Checkbox Support Library: Fix Committed Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-support/+bug/1830146/+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 1830146] Re: Checkbox detect an extra webcam "video1"
** Changed in: checkbox-support Status: Confirmed => In Progress -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Checkbox Support Library: In Progress Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-support/+bug/1830146/+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 1830146] Re: Checkbox detect an extra webcam "video1"
** Project changed: plainbox-provider-checkbox => checkbox-support ** Changed in: checkbox-support Milestone: 0.49.0 => None ** Changed in: checkbox-support Milestone: None => 0.42.0 ** Merge proposal linked: https://code.launchpad.net/~sylvain-pineau/checkbox-support/+git/checkbox-support/+merge/369092 -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Checkbox Support Library: Confirmed Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-support/+bug/1830146/+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 1830146] Re: Checkbox detect an extra webcam "video1"
Thanks @Gene, for this system I think it's a combo color + IR webcam for windows hello compatibility. See https://www.dell.com/en- us/work/shop/cty/pdp/spd/latitude-15-5501-laptop/s009l550115us "Bypass passwords: Start the workday faster by signing on with an optional fingerprint reader integrated into the power button or with the optional IR camera + Windows Hello for seamless authentication. " Such webcams are sometimes very well designed and almost invisible in the screen chassis but a closer look can reveal the two sensors. Can you confirm it's a system with two cameras? -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Provider for Plainbox - Checkbox: Confirmed Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1830146/+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 1830146] Re: Checkbox detect an extra webcam "video1"
** Changed in: plainbox-provider-checkbox Importance: High => Critical ** Changed in: plainbox-provider-checkbox Milestone: None => 0.49.0 -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Provider for Plainbox - Checkbox: Confirmed Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1830146/+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 1830146] Re: Checkbox detect an extra webcam "video1"
In the goal of teaching the checkbox udev parser how to discard the metadata device node, @Gene and @Betty could you please run this command on all devices listed as video under /dev and mention the CID on the corresponding system? v4l2-ctl --device=/dev/video0 --all v4l2-ctl --device=/dev/video1 --all v4l2-ctl --device=/dev/video2 --all v4l2-ctl --device=/dev/video3 --all ... Thanks -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Provider for Plainbox - Checkbox: Confirmed Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1830146/+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 1318584] Re: qt crashed when switching video out mode to external or internal only mode
** Changed in: qt Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1318584 Title: qt crashed when switching video out mode to external or internal only mode Status in Checkbox GUI (Legacy): Won't Fix Status in OEM Priority Project: Won't Fix Status in OEM Priority Project trusty series: Won't Fix Status in Qt: Invalid Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: checkbox-gui crashed with following console outputs: pure virtual method called terminate called without an active exception Aborted (core dumped) Steps to reproduce: 1. open checkbox-gui 2. connected external display 3. switch video output mode, usually by using the common video output switch hotkey. Expected result: checkbox-gui still running when switching back to extended desktop video out mode. Actual result: checkbox-gui crashed --- https://bugreports.qt-project.org/browse/QTBUG-39663 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-gui/+bug/1318584/+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 1294940] Re: Text.AlignJustify does not properly justify text
** Changed in: hundredpapercuts
Status: Confirmed => Invalid
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1294940
Title:
Text.AlignJustify does not properly justify text
Status in One Hundred Papercuts:
Invalid
Status in qtdeclarative-opensource-src package in Ubuntu:
Invalid
Bug description:
Consider the following QML scene:
import QtQuick 2.0
Rectangle {
width: 200
height: 200
color: "white"
Text {
anchors.fill: parent
anchors.margins: 10
horizontalAlignment: Text.AlignJustify
text: "aa aa aaa aaa" +
"aaa aaa aaa aaa aaa " +
"aaa aaa aaa aaa aaa"
wrapMode: Text.WordWrap
}
}
Attempting to run the file in qmlscene results in the attached
screenshot. Clearly the text is not justified (as one would expect)
and is instead left-aligned.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: qmlscene 5.2.1-3ubuntu10
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 19 19:04:52 2014
InstallationDate: Installed on 2014-03-16 (3 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140314)
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1294940/+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 1165173] Re: Scrollbars should be interactive and have a thumb when running on a desktop (like regular Ubuntu overlay scrollbars)
** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1165173
Title:
Scrollbars should be interactive and have a thumb when running on a
desktop (like regular Ubuntu overlay scrollbars)
Status in Ubuntu UI Toolkit:
Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Status in ubuntu-ui-toolkit source package in Vivid:
Invalid
Bug description:
The new Friends GUI/Timeline does not seem to support overlay
scrollbars. Right now you have to click and drag the timeline which
does not seem consistent with now the rest of the desktop GUI work.
The good news is that interactive scrollbars with a thumb (== overlay
scrollbars as we know them on the desktop) are implemented in the UI
toolkit. However they are not configured to behave like that. To
configure them in that manner a couple of theme properties need to be
changed in themes/Ambiance/qmltheme/default.qmltheme:
.scrollbar {
interactive: true;
overlay: false;
overlayOpacityWhenShown: 1.0;
[...]
}
Now the idea is to have the thumbs enabled automatically when and only
when the app is running on a 'desktop' computer (ie. when a mouse is
available).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1165173/+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 1690836] [NEW] libnl-genl-3.0 memory leak
Public bug reported: It seems that there is a memory leak in the libnl-genl-3.0 library. The memory-leak can be seen when the function genl_ctrl_resolve() fails. It seems that this function copy a buffer and forget to deallocate it properly: 258 cb = nl_cb_clone(orig); // buffer copied not freed - The following attached source-code can help you to reproduce this behavior on Ubuntu 14.04. It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family. To compile program: g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main To detect memory-leak using Valgrind: valgrind --leak-check=full ./main - Executing it on Debian 8.0 shows "no memory leak": sylvain@debian:~/test$ lsb_release -rd Description:Debian GNU/Linux 8.8 (jessie) Release: 8.8 sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main sylvain@debian:~/test$ valgrind --leak-check=full ./main ==26390== Memcheck, a memory error detector ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==26390== Command: ./main ==26390== start test error: can't retrieve the netlink-family id end test ==26390== ==26390== HEAP SUMMARY: ==26390== in use at exit: 0 bytes in 0 blocks ==26390== total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated ==26390== ==26390== All heap blocks were freed -- no leaks are possible ==26390== ==26390== For counts of detected and suppressed errors, rerun with: -v ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) - Executing it on Ubuntu 14.04 shows a memory leak: ubuntu@ubuntu:~$ lsb_release -rd Description:Ubuntu 14.04.5 LTS Release:14.04 ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main ubuntu@ubuntu:~$ valgrind --leak-check=full ./main ==37377== Memcheck, a memory error detector ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==37377== Command: ./main ==37377== start test error: can't retrieve the netlink-family id end test ==37377== ==37377== HEAP SUMMARY: ==37377== in use at exit: 224 bytes in 1 blocks ==37377== total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated ==37377== ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==37377==at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==37377==by 0x5048FAA: nl_cb_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x504CB1E: nl_socket_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main) ==37377==by 0x401189: main (in /home/ubuntu/main) ==37377== ==37377== LEAK SUMMARY: ==37377==definitely lost: 224 bytes in 1 blocks ==37377==indirectly lost: 0 bytes in 0 blocks ==37377== possibly lost: 0 bytes in 0 blocks ==37377==still reachable: 0 bytes in 0 blocks ==37377== suppressed: 0 bytes in 0 blocks ==37377== ==37377== For counts of detected and suppressed errors, rerun with: -v ==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Thanks, Sylvain Trinquet ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: leak libnl memory ** Attachment added: "trigger the memory leak" https://bugs.launchpad.net/bugs/1690836/+attachment/4876902/+files/main.cpp ** Description changed: It seems that there is a memory leak in the libnl-genl-3.0 library. The memory-leak can be seen when the function genl_ctrl_resolve() fails. It seems that this function copy a buffer and forget to deallocate it properly: - 258 cb = nl_cb_clone(orig); // buffer copied not freed + 258 cb = nl_cb_clone(orig); // buffer copied not freed - + - The following attached source-code can help you to reproduce this behavior on Ubuntu 14.04. It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family. To compile program: g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main To detect memory-leak using Valgrind: valgrind --leak-check=full ./main - + - Exe
[Touch-packages] [Bug 1675722] Re: thunderbird import gpg key with enigmail: systemd-resolved crashed with SIGABRT in log_assert_failed()
*** This bug is a duplicate of bug 1666193 *** https://bugs.launchpad.net/bugs/1666193 Bug 1666193 cannot be found Which one? -- 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/1675722 Title: thunderbird import gpg key with enigmail: systemd-resolved crashed with SIGABRT in log_assert_failed() Status in systemd package in Ubuntu: New Bug description: I was trying to import a gpg key from thunderbird. It crashed, and reported about systemd?? To be continued… ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-9ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Fri Mar 24 11:28:54 2017 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2016-11-22 (121 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E6430 ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=69d632c8-caac-4ae9-8716-20dc726dfcfe ro persistent quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: log_assert_failed () from /lib/systemd/libsystemd-shared-231.so ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGABRT in log_assert_failed() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/08/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0CPWYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0CPWYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1675722/+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 785537] Re: Montreal shows location as America/Toronto
The probleme is with ubuntu 16 as well and to fix it you must choose (during install) "Mont-real" and not "Montreal" The city name is miss spell ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/785537 Title: Montreal shows location as America/Toronto Status in tzdata package in Ubuntu: Invalid Bug description: Binary package hint: tzdata Ubuntu 11.04. Montreal shows America/Toronto instead of Americas/Montreal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/785537/+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 1551897] Re: Excessive CPU utilization
Hello, I've the same problem with my laptop (Dell Latitude E7450). If I can help don't hesitate to ask me. I can give you some logs if you want. Best regards, Sylvain -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in ccid package in Ubuntu: Fix Released Status in pcsc-lite package in Ubuntu: Invalid Status in ccid source package in Xenial: In Progress Status in pcsc-lite source package in Xenial: Invalid Status in pcsc-lite package in Debian: Fix Released Bug description: [Impact] When hotplugging a composite USB device that expose multiple interfaces (such as a Yubikey NEO or Yubikey 4), libccid does not correctly de-initialize the USB library when it skips over the non- CCID interface. This subsequently results in pcscd (or, presumably, anything that loads libccid, though I don't think anything else does) either using 100% CPU or segfaulting when the device is unplugged. This seems worthy of an SRU as it is an easily reproducible bug with a simple, targeted fix. [Test Case] 1. Make sure pcscd is running (sudo systemctl start pcscd; possibly sudo systemctl restart pcscd if a potentially fixed package has just been installed) 2. Plug and then unplug a composite USB device that includes a CCID interface (such as a Yubikey NEO) 3. Observe that pcscd has crashed with a segfault (sudo systemctl status pcscd) [Regression Potential] The patch is quite narrow, and thus the potential for regression should be limited. The new code adds calls to close_libusb_if_needed, which is already written to be fairly conservative. The worst case here is likely an unexpected call to libusb_exit, which could cause libusb to get into an inconsistent state. However, in practice the call seems quite safe, and the likelihood of regression low. == Original bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1551897/+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 1558125] [NEW] ntpd doesn't synchronize to local clock (ntpd 4.2.8p4/xenial)
Public bug reported: Ubuntu 16.04 (Xenial Xerus development branch) ntpd version: 1:4.2.8p4+dfsg-3ubuntu3 Source available at: http://packages.ubuntu.com/source/xenial/ntp Using the local clock as a source for ntpd doesn't work anymore This appears to have already been fixed in 4.2.8p5 as per the bug report referenced below http://bugs.ntp.org/show_bug.cgi?id=2965 Sample config extract from /etc/ntp.conf: server 127.127.1.0 fudge 127.127.1.0 stratum 3 Results from ntpq, we would expected the server to be reachable and synced : # ntpd -p remote refid st t when poll reach delay offset jitter == LOCAL(0).LOCL. 3 l- 6400.0000.000 0.000 # ntpq ntpq> as ind assid status conf reach auth condition last_event cnt = 1 4979 8011 yes nonone reject mobilize 1 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1558125 Title: ntpd doesn't synchronize to local clock (ntpd 4.2.8p4/xenial) Status in ntp package in Ubuntu: New Bug description: Ubuntu 16.04 (Xenial Xerus development branch) ntpd version: 1:4.2.8p4+dfsg-3ubuntu3 Source available at: http://packages.ubuntu.com/source/xenial/ntp Using the local clock as a source for ntpd doesn't work anymore This appears to have already been fixed in 4.2.8p5 as per the bug report referenced below http://bugs.ntp.org/show_bug.cgi?id=2965 Sample config extract from /etc/ntp.conf: server 127.127.1.0 fudge 127.127.1.0 stratum 3 Results from ntpq, we would expected the server to be reachable and synced : # ntpd -p remote refid st t when poll reach delay offset jitter == LOCAL(0).LOCL. 3 l- 6400.0000.000 0.000 # ntpq ntpq> as ind assid status conf reach auth condition last_event cnt = 1 4979 8011 yes nonone reject mobilize 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1558125/+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 1558125] Re: ntpd doesn't synchronize to local clock (ntpd 4.2.8p4/xenial)
Tested and confirmed it's working now. There appears to be a behavioural change from 4.2.6 to 4.2.8 when using the local clock as a source. In 4.2.6 the sync would be almost instantaneous while on 4.2.8 it will poll itself for a while before syncing as if it were an external resource. I was able to overcome this delay by setting the local source as preferred The new config in /etc/ntp.conf server 127.127.1.0 prefer fudge 127.127.1.0 stratum 3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1558125 Title: ntpd doesn't synchronize to local clock (ntpd 4.2.8p4/xenial) Status in ntp package in Ubuntu: Fix Released Bug description: Ubuntu 16.04 (Xenial Xerus development branch) ntpd version: 1:4.2.8p4+dfsg-3ubuntu3 Source available at: http://packages.ubuntu.com/source/xenial/ntp Using the local clock as a source for ntpd doesn't work anymore This appears to have already been fixed in 4.2.8p5 as per the bug report referenced below http://bugs.ntp.org/show_bug.cgi?id=2965 Sample config extract from /etc/ntp.conf: server 127.127.1.0 fudge 127.127.1.0 stratum 3 Results from ntpq, we would expected the server to be reachable and synced : # ntpd -p remote refid st t when poll reach delay offset jitter == LOCAL(0).LOCL. 3 l- 6400.0000.000 0.000 # ntpq ntpq> as ind assid status conf reach auth condition last_event cnt = 1 4979 8011 yes nonone reject mobilize 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1558125/+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 1318584] Re: qt crashed when switching video out mode to external or internal only mode
I'm setting this as WONTFIX since we're deprecating checkbox-gui. ** Changed in: checkbox-gui Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1318584 Title: qt crashed when switching video out mode to external or internal only mode Status in Next Generation Checkbox (GUI): Won't Fix Status in OEM Priority Project: Won't Fix Status in OEM Priority Project trusty series: Won't Fix Status in Qt: New Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: checkbox-gui crashed with following console outputs: pure virtual method called terminate called without an active exception Aborted (core dumped) Steps to reproduce: 1. open checkbox-gui 2. connected external display 3. switch video output mode, usually by using the common video output switch hotkey. Expected result: checkbox-gui still running when switching back to extended desktop video out mode. Actual result: checkbox-gui crashed --- https://bugreports.qt-project.org/browse/QTBUG-39663 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-gui/+bug/1318584/+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 1393744] Re: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04
bad news... even with these commands, the connection is rather unstable... -- 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/1393744 Title: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04 Status in network-manager package in Ubuntu: Triaged Bug description: lsb_release -rd :Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 wi-fi disconnects and unable to reconnect since updates on 13-11-2014. Also affects Lubuntu 15.04 on same machine. Ubuntu 12.04.1 on same machine does not disconnect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.8.8-0ubuntu34 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 CurrentDesktop: XFCE Date: Tue Nov 18 11:12:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-01-14 (307 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140114) IpRoute: RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Petersbergd473a136-74dc-4695-aac3-1fffc9cc8095 802-11-wireless 1416308390 Tue 18 Nov 2014 10:59:50 GMT yes no /org/freedesktop/NetworkManager/Settings/2 BTWifi-with-FON a2b63b98-159a-49f4-9247-d46a0d67ed41 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 Petersberg 1 4fc01379-d340-479e-a016-9af1ab717c83 802-11-wireless 1416303120 Tue 18 Nov 2014 09:32:00 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8disconnectedenabled enabled enabledenabled disabled --- ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1938 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ffe4c76c-645c-4847-ba8c-b2323517a10f InstallationDate: Installed on 2014-01-14 (318 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140114) MachineType: VIA Technologies, Inc. VT8363 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=ed3144cc-8873-40a1-9670-bb2bfc9190a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: vivid Uname: Linux 3.16.0-25-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/01/2000 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 6.00 PG dmi.board.name: 8363-686A dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd08/01/2000:svnVIATechnologies,Inc.:pnVT8363:pvr:rvn:rn8363-686A:rvr:cvn:ct3:cvr: dmi.product.name: VT8363 dmi.sys.vendor: VIA Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393744/+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 1393744] Re: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04
modprobe -v rt61pci nohwcrypt=y did the job for me... seems to be quite stable now.. I'm still testing is the connection keeps running. -- 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/1393744 Title: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04 Status in network-manager package in Ubuntu: Triaged Bug description: lsb_release -rd :Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 wi-fi disconnects and unable to reconnect since updates on 13-11-2014. Also affects Lubuntu 15.04 on same machine. Ubuntu 12.04.1 on same machine does not disconnect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.8.8-0ubuntu34 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 CurrentDesktop: XFCE Date: Tue Nov 18 11:12:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-01-14 (307 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140114) IpRoute: RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Petersbergd473a136-74dc-4695-aac3-1fffc9cc8095 802-11-wireless 1416308390 Tue 18 Nov 2014 10:59:50 GMT yes no /org/freedesktop/NetworkManager/Settings/2 BTWifi-with-FON a2b63b98-159a-49f4-9247-d46a0d67ed41 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 Petersberg 1 4fc01379-d340-479e-a016-9af1ab717c83 802-11-wireless 1416303120 Tue 18 Nov 2014 09:32:00 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8disconnectedenabled enabled enabledenabled disabled --- ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1938 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ffe4c76c-645c-4847-ba8c-b2323517a10f InstallationDate: Installed on 2014-01-14 (318 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140114) MachineType: VIA Technologies, Inc. VT8363 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=ed3144cc-8873-40a1-9670-bb2bfc9190a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: vivid Uname: Linux 3.16.0-25-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/01/2000 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 6.00 PG dmi.board.name: 8363-686A dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd08/01/2000:svnVIATechnologies,Inc.:pnVT8363:pvr:rvn:rn8363-686A:rvr:cvn:ct3:cvr: dmi.product.name: VT8363 dmi.sys.vendor: VIA Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393744/+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 1387219] Re: Mouse pointer disappears and cursor stops blinking
Same here on Ubuntu 14.10 utopic. - Cursor disappears - 100% CPU usage by ibus daemon. (save) makes the cursor re-appear. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in GtkSourceView Widget: Expired Status in anjuta package in Ubuntu: Confirmed Status in gedit package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. Notice that the mouse ponter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. ***Workaround*** sudo apt-get install ibus-gtk $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1387219/+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 1269773] Re: unidentified fglrx video glitch under firefox which can end in video half shifted
Hi, Same computer bug xubuntu 14.04. No more this bug for me. I think you can close. Sylvain. -- 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/1269773 Title: unidentified fglrx video glitch under firefox which can end in video half shifted Status in xorg package in Ubuntu: Incomplete Bug description: Hi, I don't known where I should exactly post this bug. I will try to describe it. Seems to appear since I upgraded from xubuntu 12.04.3 LTS to 13.10. I'm running it on a Compaq laptop : compaq pressario cq57-421 with Graphiques AMD Radeon HD 6310 lspci -nn | grep VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] This is a sporadic bug which seems to start under some web pages only. It starts by glitching the screen, slowly more or less frequently depending on the "faulty" web pages. Some small glitch 2 or 3 by minute to 1 by second. If I stay on the page it could end to screen to be half shifted. See attached picture. Today, after reinstalling the fglrx package. It ended on a simple 3 or 4 pixels bottom glitching video, only on the faulty web page. The whole system seems not te be impacted as on the picture. During the glitching phase the frequency was 1 by sec or more. It could become form a bad upgrade, from the OS, the graphic driver, the X11 configuration, or the browser… Sorry to be such evasive at the moment. Trying the Open source graphical driver (xserver-xorg-video-radeon) but ended to a blank or unusable desktop after lightdm auth. Sorry if this report is in the wrong place, please point me to a more appropriate one. I've bookmarked a URL which reproduce the bug: a linkedin.com profile when I'm logged in, not very useful. only at the top of the page, scrolling stop the glitching… Some versions information… lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 uname -a Linux xubuntu-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:16:27 UTC 2013 i686 athlon i686 GNU/Linux dpkg -l | grep fglrx ii fglrx 2:13.200~beta-0ubuntu1~xedgers~saucy2 i386 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:13.200~beta-0ubuntu1~xedgers~saucy2 i386 Catalyst Control Center for the AMD graphics accelerators glxinfo | grep OpenGL OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 6310 Graphics OpenGL core profile version string: 4.3.12438 Core Profile Context 13.20.5 OpenGL core profile shading language version string: 4.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.3.12438 Compatibility Profile Context 13.20.5 OpenGL shading language version string: 4.30 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: fglrxinfo -v | grep OpenGL OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 6310 Graphics OpenGL version string: 4.3.12438 Compatibility Profile Context 13.20.5 OpenGL extensions: Nom: Firefox Version: 26.0 Agent utilisateur: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0 Nom: Ubuntu Firefox Modifications Version: 2.8 Activée: false ID: ubu...@ubuntu.com Accélération graphique -- Description de la carte: ATI Technologies Inc. -- AMD Radeon HD 6310 Graphics Fenêtres avec accélération graphique: 0/3 Basic ID du périphérique: AMD Radeon HD 6310 Graphics ID du vendeur: ATI Technologies Inc. Rendu WebGL: ATI Technologies Inc. -- AMD Radeon HD 6310 Graphics Version du pilote: 4.3.12438 Compatibility Profile Context 13.20.5 windowLayerManagerRemote: false AzureCanvasBackend: cairo AzureContentBackend: none AzureFallbackCanvasBackend: none AzureSkiaAccelerated: 0 apt-cache policy fglrx fglrx: Installé : 2:13.200~beta-0ubuntu1~xedgers~saucy2 Candidat : 2:13.200~beta-0ubuntu1~xedgers~saucy2 Table de version : *** 2:13.200~beta-0ubuntu1~xedgers~saucy2 0 500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status 2:13.101-0ubuntu3 0 500 http://fr.archive.ubuntu.com/ubuntu/ saucy/restricted i386 Packages apt-cache policy firefox firefox: Installé : 26.0+build2-0ubuntu0.13.10.2 Candidat : 26.0+build2-0ubuntu0.13.10.2 Table de version : *** 26.0+build2-0ubuntu0.13.10.2 0 500 http://fr.archive.ubuntu.com/ubuntu/ saucy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ sauc
[Touch-packages] [Bug 1313155] Re: Screen stays blank after screen saver triggered
On Ubuntu 14.10, compiz 1:0.9.12+14.10.20140918-0ubuntu1, I just tested a couple of times to let the screen saver turn off the screen and I can show the lock screen again. The bug seems resolved in this version. -- 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/1313155 Title: Screen stays blank after screen saver triggered Status in “xorg” package in Ubuntu: New Bug description: To reproduce: - Set the screen saver in System Settings / Brightness&Lock to 1 minute to speed up testing. Disable screen lock. - Wait one minute - The screen fade to black - The monitor indicate entering in power save mode, wait a couple of seconds. - Press a key to show the screen again. - The monitor turn on again but the screen is dark (but not as dark as when the monitor is off). I tried switching with CTRL-ALT-F1 to console but I don't see it. With another machine I can still login by ssh so the machine is not dead. I can also use the console to login and sudo reboot (without seeing anything). It happen once that I saw the Ubuntu desktop instead of a blank screen but the left border was shifted 80% to the right. The desktop and mouse was responsive but it is too weird to work with. Rebooting fix the problem. I tried different xrandr commands with ssh with another machine (--off, --mode to switch resolutions) but without success. As a temporary measure, I disabled the screen saver and the automatic lock. When I want to stop working on my computer, I do CTLR-ALT-L to lock and CTRL-ALT-F1 to switch to console. Then I manually close my monitor. When I come back, I open the monitor again and I switch to CTRL-ALT-F7. The lock screen is visible and I can unlock and work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 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 Apr 26 13:26:04 2014 DistUpgraded: 2014-04-19 19:21:14,189 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.11.0-19-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0477] InstallationDate: Installed on 2013-12-18 (129 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=c2e5aa1a-ee79-434d-a13c-6969ef5102c0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-19 (6 days ago) dmi.bios.date: 04/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0311:bd04/18/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Apr 25 22:30:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1313155/+subscrip
[Touch-packages] [Bug 1379777] Re: Allow applications to specify the orientations supported
Hello, I am the one who talks/asks Gerry about this feature. My applications/games require a specific orientation : some require Landscape, others Portrait. So they need a way to request/lock this kind of configuration. The file ".desktop" would be really convenient to use (though it may not be dynamic as Michal said). If you make it an API, please note this is not specific to QtMir. My applications don't use QT at all. They are directly using MIR Client + OpenGL. Cheers, Sylvain -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1379777 Title: Allow applications to specify the orientations supported Status in Qt integration with the Mir display server: New Status in Ubuntu UI Toolkit: Triaged Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: Currently unity8 shell has a partial implementation of orientation support. It trusts applications to rotate their own contents, if they want to. The shell doesn't reposition the panel (at the top) though, so a landscape app still has a portrait panel on the side. For proper orientation support in the shell, shell needs to know if the application wants to rotate its contents or not. To animate correctly, we really need shell to be responsible for rotating the app surface, not the app itself. Therefore an application needs to tell shell what orientations it supports, so shell can respect its wishes. A hint in the desktop file may be sufficient. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1379777/+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
