[Bug 2043373] Re: Ubuntu shows "Software Update Installed" every time I log in
*** This bug is a duplicate of bug 2024392 *** https://bugs.launchpad.net/bugs/2024392 I found the solution to the issue that I raised this bug for here: https://askubuntu.com/questions/1490410/how-can-i-dismiss-software- updates-installed-notification-the-saga-continues This bug can be closed. Thanks, Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043373 Title: Ubuntu shows "Software Update Installed" every time I log in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2043373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068543] Re: Config variable $nrconf{restart} is no longer accurate: it always restarts
I have noticed the same thing on 3 servers after they were upgraded to
24.04.
I also tested the following:
sudo NEEDRESTART_MODE=l apt full-upgrade --autoremove
i.e. specifying the restart mode in an environment variable (which I
found by Googling), but this also had no effect.
I could be wrong about this, but it seems to me as though when
needrestart is run manually, it DOES observe the settings in
/etc/needrestart/needrestart.conf, but when it is run automatically by
apt, it DOESN'T observe the settings and always restarts services. Could
apt be passing in a NEEDRESTART_MODE=a environment variable to cause
this behaviour?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068543
Title:
Config variable $nrconf{restart} is no longer accurate: it always
restarts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2068543/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965521] Re: named.service starts too early: Unable to fetch DNSKEY set '.': failure
Thanks Simon & Paride. That is reassuring to know that BIND will retry. Based on that I'm happy for you to treat this as a low priority issue. I still do think it is worth fixing (somehow), but better to deal with it in a generic way that helps other packages too, rather than trying to cobble together a BIND- specific fix. I have a workaround that stops this error from bugging me (i.e. using systemd-networkd-wait-online) so I'm happy. :-) Thanks for your all your time and efforts. Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965521 Title: named.service starts too early: Unable to fetch DNSKEY set '.': failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1965521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965521] Re: named.service starts too early: Unable to fetch DNSKEY set '.': failure
Hi Paride. The fundamental problem I see with your last statement is how do you know what "the right one(s)" are? That will depend on BIND configuration, such as whether named is launched with a '-4' or '-6' option, and possibly even the value of configuration options such as 'listen-on' and 'listen-on-v6'? Perhaps if we start with the 'need' that BIND has, and then work backwards, we will converge on a solution? Here is my thinking: 1. The "Unable to fetch DNSKEY set '.': failure" error results from BIND trying to query the root DNS servers when it starts up, but not having the requisite level of network connectivity to do so. 2. In order to access the root DNS servers, the host needs access to the Internet... 3. The best indicator that Internet connectivity is available is the presence of a default route. 4. The default route requirement could be met by IPv4 or IPv6, so this could be satisfied by either of the following: * The IPv4 'main' routing table contains an entry for "0.0.0.0/0" * The IPv6 'main' routing table contains an entry for "::/0" 5. Therefore I believe we need a command that can be added as an 'ExecStartPre' option in named.service, that will wait until either of the above conditions (described in 5 above) are met. 6. Some potential solutions could be: a) Invocation of "systemd-networkd-wait-online" with a combination of existing parameters that the program will interpret to mean "wait until either of the requirements described in 5 above are met". b) Invocation of "systemd-networkd-wait-online" with a new parameter that the program will interpret to mean "wait until either of the requirements described in 5 above are met". c) Use of a different (new?) tool whose specific purpose is to "wait until either of the requirements described in 5 above are met". 7. Whichever solution is chosen, the tool should be generic enough that it can be used for other services, and should provide the ability to select only IPv4 or only IPv6, or both. This should be controlled via a command-line parameter, which for consistency with other Linux programs should be: * "-4" = use only IPv4, even if the host machine is capable of IPv6. * "-6" = use only IPv6, even if the host machine is capable of IPv4. * Specifying neither option should mean both IPv4 and IPv6. * NB: "-4" and "-6" are mutually exclusive. My suggestion in my earlier comment #4 is an example of solution (a), but it doesn't satisfy 7 above. So I concede there are other (better) options that probably need to be considered? Keen to hear your thoughts? Thanks, Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965521 Title: named.service starts too early: Unable to fetch DNSKEY set '.': failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1965521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965521] Re: named.service starts too early: Unable to fetch DNSKEY set '.': failure
Hi Paride. Thanks for your updates. It is good news that there is a fix for #1909822. However this fix won't help with the current issue, because the problem here isn't whether or not BIND uses interfaces that are added after BIND is running, but rather the fact that BIND doesn't have connectivity to the root DNS servers when it starts. After reading your first update, I do agree that improving systemd- networkd-wait-online "network ready enough" is the preferred way to go, so lets focus on that solution... In update #1 I mentioned: I experimented with including "--any" in the systemd-networkd-wait-online arguments, but found this wasn't 100% reliable and TBH I'm not entirely sure why. The ExecStartPre command I'd tested was: ExecStartPre=-/lib/systemd/systemd-networkd-wait-online --operational- state=routable --any --timeout=10 --quiet I don't know why adding "--any" didn't work, because this particular server only has one network interface. I wondered if it was actually picking up the "lo" interface? I only just now noticed there is an option to ignore interfaces, so maybe I should have tried adding "-- ignore=lo" above? But TBH if that is the problem it seems like something that should be fixed in systemd-networkd-wait-online? Regardless of why it didn't work, can I please specify the behaviour that I believe the above command should implement: Where you've specified a state of "routeable" and said "any" interface, IMO the goal should be the existence of a static route in the main routing table? What do you think? Thanks, Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965521 Title: named.service starts too early: Unable to fetch DNSKEY set '.': failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1965521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965521] Re: named.service starts too early: Unable to fetch DNSKEY set '.': failure
I discovered that above workaround isn't ideal when the server has multiple network interfaces because the systemd-networkd-wait-online command above will wait for all interfaces to reach routable status. This may cause systemd-networkd-wait-online to timeout (after 10 seconds as per --timeout argument), and if you then run "systemctl status named.service", it shows a failed status for the ExecStartPre command, which isn't ideal. I experimented with including "--any" in the systemd-networkd-wait- online arguments, but found this wasn't 100% reliable and TBH I'm not entirely sure why. But for now I've resorted to including the interface name in the above command instead, such as: ExecStartPre=-/lib/systemd/systemd-networkd-wait-online --interface=eno1:routable --timeout=10 --quiet Obviously the interface name is machine-specific, which makes it impractical to include this command as a general purpose fix in the repo version of named.service. So I've now come to the conclusion that the best way to fix this issue is to implement a change to BIND itself (i.e. /usr/sbin/named), to make it retry a few times before logging the error message above? (FYI This is outside of the realm of my skill set so I guess I'm asking for the maintainer of BIND to determine the feasibility of this request?) Thanks, Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965521 Title: named.service starts too early: Unable to fetch DNSKEY set '.': failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1965521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909822] Re: named fails to listen dynamic ipv6 address on startup
FYI I've reported a similar (but different) bug: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1965521 I believe the workaround that I've offered is slightly more optimal than the 10-second sleep offered above. (It is however reassuring to know that you solved this problem in almost exactly the same way.) Thanks, Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909822 Title: named fails to listen dynamic ipv6 address on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965521] [NEW] named.service starts too early: Unable to fetch DNSKEY set '.': failure
Public bug reported: I have two servers that run named.service, and I recently discovered that (on both servers), when I reboot and then run "systemctl status named.service" (or "journalctl -u named.service"), I see messages like this: Mar 18 21:03:05 mail named[859]: managed-keys-zone/xxx: Unable to fetch DNSKEY set '.': failure ...where xxx is the view name, and this error is repeated for each view. (I have many views.) (OTOH if the server is already up and running, and then I start named.service it starts up with no errors.) By creating a shell script that ran various "ip" diagnostic commands, and adding this to named.service as a "ExecStartPre" hook, I was able to determine that the error above occurs because BIND is being started before the network is available. (The network interfaces didn't even have IP addresses at that time.) I should highlight at this point that in spite of the error, as far as I know BIND was running OK, serving DNS as normal. I can only guess that it had cached copies of the required records or something like that? Anyway I don't like seeing errors like this in my logs, so... My initial attempt to solve this problem involved setting named.service to start after network-online.target. Results were mixed. Sometimes there were no errors on reboot, but more often than not the same errors were there. Then I worked out that network-online.target is based on systemd- networkd-wait-online, which by default only waits until IP addresses are assigned to interfaces. To solve the error above, I needed it to wait for the operational status to become "routable". I was able to achieve this by specifying the following in /etc/systemd/system/named.service.d/override.conf (i.e. file content is between the "-" lines) - [Unit] After=network-online.target [Service] ExecStartPre=-/lib/systemd/systemd-networkd-wait-online --operational-state=routable --timeout=10 --quiet - Effectively this causes systemd to delay starting named.service until the network interfaces have addresses, and then when it does start named.service, the ExecStartPre line above waits (for up to 10 seconds) until network routes are added before BIND (i.e. /usr/sbin/named) is launched. Can I please request that the named.service definition in the bind9 package is updated to include the options above? Final note: Although this bug would appear to be similar to 1909822 ( https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909822 ), the error message I observed is different, and so I've raised this as a separate bug report. Having said that, I suspect the solution that I'm offering above would fix both issues (and would be slightly more optimal than that offered by 1909822). System-specific information follows: # lsb_release -rd Description:Ubuntu 21.10 Release:21.10 # apt-cache policy bind9 bind9: Installed: 1:9.16.15-1ubuntu1.2 Candidate: 1:9.16.15-1ubuntu1.2 Version table: *** 1:9.16.15-1ubuntu1.2 500 500 http://nz.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://nz.archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 1:9.16.15-1ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu impish/main amd64 Packages Thanks, Nick. ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965521 Title: named.service starts too early: Unable to fetch DNSKEY set '.': failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1965521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885403] Re: posttls-finger fails to connect to private/tlsmgr
Thanks everyone for fixing this issue. Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885403 Title: posttls-finger fails to connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1885403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915501] Re: init.d script fails to set socket ownership and permissions on slower systems
Hi Harald. I'm happy for this bug to be closed. (FYI I'm currently in the process of decommissioning this old server, and replacing it with a new machine which supports the latest Ubuntu distro.) Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915501 Title: init.d script fails to set socket ownership and permissions on slower systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1915501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915501] Re: init.d script fails to set socket ownership and permissions on slower systems
Here is the fix that I'm using (complete updated file is also attached). The updated init.d script checks that the socket exists before executing the chown/chmod commands. If it doesn't exist, it sleeps for 1 second and rechecks, repeating if necessary up to 5 times, before logging a warning if the socket still doesn't exist. $ diff amavisd-milter.old amavisd-milter 82d81 < log_end_msg 0 84,88c83,99# Wait for up to 5 seconds for unix socket to be created >for i in 1 2 3 4 5; do > if [ -S "$MILTERSOCKET" ]; then >break > fi > sleep 1 >done ># Set ownership and permissions on unix socket as > appropriate >if [ -S "$MILTERSOCKET" ]; then > if [ "$MILTERSOCKETOWNER" ]; then >chown "$MILTERSOCKETOWNER" "$MILTERSOCKET" > fi > if [ "$MILTERSOCKETMODE" ]; then >chmod "$MILTERSOCKETMODE" "$MILTERSOCKET" > fi >else > log_warning_msg "timed out waiting for pipe to be > created" 90a102 > log_end_msg 0 ** Attachment added: "Updated init.d script (containing fix)" https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1915501/+attachment/5463509/+files/amavisd-milter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915501 Title: init.d script fails to set socket ownership and permissions on slower systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1915501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915501] [NEW] init.d script fails to set socket ownership and permissions on slower systems
Public bug reported: I've just started using amavisd-milter on an 'older' (i.e. slow) server, and I encountered a problem with the init.d startup script (/etc/init.d /amavisd-milter): The script would successfully use "start-stop-daemon $START" to launch the /usr/sbin/amavisd-milter process, but would then attempt to set the ownership (chown) and permissions (chmod) on the unix socket before the /usr/sbin/amavisd-milter process had created the socket. This meant that the ownership and permissions specified in /etc/default /amavisd-milter would fail to have any effect (or in some cases, setting the ownership would fail but setting the permissions would succeed). The solution to this problem is to have the startup script wait until the socket is created, before attempting to set the ownership and permissions. I've updated the script on my server to resolve the problem, and I'd like to submit this as a patch, but I'm having trouble finding out which project to check out (i.e. with bzr branch lp:PROJECT-NAME)? Perhaps it is because there is an upstream project that I should be using instead? Please point me in the right direction? System information: # lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 # apt-cache policy amavisd-milter amavisd-milter: Installed: 1.5.0-5 Candidate: 1.5.0-5 Version table: *** 1.5.0-5 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status Thanks, Nick. ** Affects: amavisd-milter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915501 Title: init.d script fails to set socket ownership and permissions on slower systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1915501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914889] [NEW] dns timeout didn't result in tempfail
Public bug reported: My mail logs show that OpenDKIM experienced a DNS timeout when validating the DKIM signature on an inbound email, but then accepted the message. As a result the DMARC policy was applied and the message was quarantined. The expected behaviour in the event of a DNS timeout is that it would use the On-DNSError setting, which defaults to tempfail, and would cause the sending MTA to retry at a later time, and when this happened it is expected that the result of the earlier DNS query would be immediately available because it would have been cached by the DNS server, and so the signature would have been successfully verified and therefore would have passed DMARC check (and the email would have been accepted). Here is what my mail logs showed: Jan 28 11:27:33 mx postfix/postscreen[19584]: CONNECT from [168.100.1.4]:14353 to [192.168.20.197]:25 Jan 28 11:27:33 mx postfix/postscreen[19584]: PASS OLD [168.100.1.4]:14353 Jan 28 11:27:33 mx postfix/smtpd[19585]: connect from russian-caravan.cloud9.net[168.100.1.4] Jan 28 11:27:34 mx postfix/smtpd[19585]: Anonymous TLS connection established from russian-caravan.cloud9.net[168.100.1.4]: TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits) Jan 28 11:27:35 mx policyd-spf[19610]: prepend Received-SPF: None (mailfrom) identity=mailfrom; client-ip=168.100.1.4; helo=russian-caravan.cloud9.net; envelope-from=owner-postfix-us...@postfix.org; receiver= Jan 28 11:27:35 mx policyd-spf[19615]: prepend Received-SPF: None (mailfrom) identity=mailfrom; client-ip=168.100.1.4; helo=russian-caravan.cloud9.net; envelope-from=owner-postfix-us...@postfix.org; receiver= Jan 28 11:27:35 mx postfix/smtpd[19585]: 5481E5E10A6: client=russian-caravan.cloud9.net[168.100.1.4] Jan 28 11:27:35 mx postfix/cleanup[19627]: 5481E5E10A6: message-id= Jan 28 11:27:40 mx opendkim[1731]: 5481E5E10A6: key retrieval failed (s=202101-e055eb0c, d=patpro.net): '202101-e055eb0c._domainkey.patpro.net' query timed out Jan 28 11:27:40 mx opendmarc[1534]: implicit authentication service: mx.tait.net.nz Jan 28 11:27:40 mx opendmarc[1534]: 5481E5E10A6: SPF(mailfrom): owner-postfix-us...@postfix.org none Jan 28 11:27:44 mx opendmarc[1534]: 5481E5E10A6: patpro.net fail Jan 28 11:27:44 mx postfix/cleanup[19627]: 5481E5E10A6: milter-hold: END-OF-MESSAGE from russian-caravan.cloud9.net[168.100.1.4]: milter triggers HOLD action; from= to= proto=ESMTP helo= Jan 28 11:27:44 mx postfix/smtpd[19585]: disconnect from russian-caravan.cloud9.net[168.100.1.4] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Here is the content of opendkim.conf (with comments and blank lines removed): Syslog yes UMask 007 Domain tait.net.nz KeyFile /etc/dkimkeys/20201017.private Selector20201017 InternalHosts 127.0.0.0/8,::1,192.168.20.192/28 Canonicalizationrelaxed/simple AlwaysAddARHeader yes Socket local:/var/run/opendkim/opendkim.sock PidFile /var/run/opendkim/opendkim.pid OversignHeaders From TrustAnchorFile /usr/share/dns/root.key UserIDopendkim You can see there is no DNSTimeout setting, meaning it uses the default value of 5 seconds. Also there are no On-... options, so these are also using default settings. My expectation is that a DNS timeout would use On-DNSError default value, which is documented as tempfail. However it would appear that it is using some other setting which defaults to accept? Version info: $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ apt-cache policy opendkim opendkim: Installed: 2.11.0~alpha-11build1 Candidate: 2.11.0~alpha-11build1 Version table: *** 2.11.0~alpha-11build1 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status As far as I can tell this is a one-off occurrence, and not something I can easily recreate. But hopefully there is enough information here to determine what happened? Thanks, Nick. ** Affects: opendkim (Ubuntu) Importance: Undecided Status: New ** Description changed: My mail logs show that OpenDKIM experienced a DNS timeout when validating the DKIM signature on an inbound email, but then accepted the message. As a result the DMARC policy was applied and the message was quarantined. The expected behaviour in the event of a DNS timeout is that it would use the On-DNSError setting, which defaults to tempfail, and would cause the sending MTA to retry at a later time, and when this happened it is expected that the result of the earlier DNS query would be immediately available because it would have been cached by the DNS server, and so the signature would have been successfully verified and therefore would have passed DMARC check (and the email would have been accepted). Here is what my mail logs showed: Jan 28 11:27:33 mx postfix/p
[Bug 1874639] Re: desktop pcs start to suspend by default
I thought that I had this problem, until I realised that I hadn't tried the systemctl stuff mentioned above. FYI The following command resolved the issue for me: sudo systemctl mask sleep.target suspend.target hibernate.target hybrid- sleep.target -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874639 Title: desktop pcs start to suspend by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885403] Re: posttls-finger fails to connect to private/tlsmgr
Hi Scott. I was thinking it was something along those lines, but based on what I've read this issue is specific to focal. >From Jan's original bug report - https://bugs.launchpad.net/ubuntu/focal/+source/postfix/+bug/1868955/comments/2 (which eventually focussed on just the DANE issue): > ... However the problem is *not* present in Debian sid or Buster, nor I could find a Debian bug referencing to it. FYI I can also confirm that this issue doesn't occur on bionic. Did something relating to the chroot thing change in focal? Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885403 Title: posttls-finger fails to connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1885403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: [SRU] after upgrade to 20.04: dane support is not working
FYI I've created the following bug report for the posttls-finger issue: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1885403 Thanks, Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: [SRU] after upgrade to 20.04: dane support is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885403] [NEW] posttls-finger fails to connect to private/tlsmgr
Public bug reported: When running posttls-finger on focal, it attempts to connect to private/tlsmgr, and unless the program is being run from /var/spool/postfix as root, this fails and posttls-finger disables TLS in the subsequent connection that it makes to the specified SMTP server. If the user doesn't notice the "disabling TLS support" message in the output, they might infer that the test has successfully verified their TLS configuration, when in fact all it has verified is that it can connect to the SMTP server without TLS. The following command shows the problem: root@maimbo:/# posttls-finger mx.dmz.tait.net.nz posttls-finger: warning: connect to private/tlsmgr: No such file or directory posttls-finger: warning: connect to private/tlsmgr: No such file or directory posttls-finger: warning: problem talking to server private/tlsmgr: No such file or directory posttls-finger: warning: no entropy for TLS key generation: disabling TLS support posttls-finger: using DANE RR: _25._tcp.mx.dmz.tait.net.nz -> mx.dane.tait.net.nz IN TLSA 3 1 1 19:D6:84:A7:45:FF:A1:46:0E:09:1B:10:CE:B8:4D:68:BF:EA:A9:C4:EA:51:2D:0F:30:A4:1D:D4:41:DE:0F:AC posttls-finger: Connected to mx.dmz.tait.net.nz[192.168.20.196]:25 posttls-finger: < 220 mx.tait.net.nz ESMTP Postfix (Ubuntu) posttls-finger: > EHLO maimbo.tait.net.nz posttls-finger: < 250-mx.tait.net.nz posttls-finger: < 250-PIPELINING posttls-finger: < 250-SIZE 2048 posttls-finger: < 250-ETRN posttls-finger: < 250-STARTTLS posttls-finger: < 250-ENHANCEDSTATUSCODES posttls-finger: < 250-8BITMIME posttls-finger: < 250-DSN posttls-finger: < 250 SMTPUTF8 posttls-finger: > QUIT posttls-finger: < 221 2.0.0 Bye In contrast, if the same command is run from /var/spool/postfix as root, the output is as follows: root@maimbo:/var/spool/postfix# posttls-finger mx.dmz.tait.net.nz posttls-finger: using DANE RR: _25._tcp.mx.dmz.tait.net.nz -> mx.dane.tait.net.nz IN TLSA 3 1 1 19:D6:84:A7:45:FF:A1:46:0E:09:1B:10:CE:B8:4D:68:BF:EA:A9:C4:EA:51:2D:0F:30:A4:1D:D4:41:DE:0F:AC posttls-finger: Connected to mx.dmz.tait.net.nz[192.168.20.196]:25 posttls-finger: < 220 mx.tait.net.nz ESMTP Postfix (Ubuntu) posttls-finger: > EHLO maimbo.tait.net.nz posttls-finger: < 250-mx.tait.net.nz posttls-finger: < 250-PIPELINING posttls-finger: < 250-SIZE 2048 posttls-finger: < 250-ETRN posttls-finger: < 250-STARTTLS posttls-finger: < 250-ENHANCEDSTATUSCODES posttls-finger: < 250-8BITMIME posttls-finger: < 250-DSN posttls-finger: < 250 SMTPUTF8 posttls-finger: > STARTTLS posttls-finger: < 220 2.0.0 Ready to start TLS posttls-finger: mx.dmz.tait.net.nz[192.168.20.196]:25: depth=0 matched end entity public-key sha256 digest=19:D6:84:A7:45:FF:A1:46:0E:09:1B:10:CE:B8:4D:68:BF:EA:A9:C4:EA:51:2D:0F:30:A4:1D:D4:41:DE:0F:AC posttls-finger: mx.dmz.tait.net.nz[192.168.20.196]:25: subjectAltName: mx.tait.net.nz posttls-finger: mx.dmz.tait.net.nz[192.168.20.196]:25 CommonName mx.tait.net.nz posttls-finger: mx.dmz.tait.net.nz[192.168.20.196]:25: subject_CN=mx.tait.net.nz, issuer_CN=Nick's Domain CA, fingerprint=FD:88:18:3D:9D:33:4C:0B:B8:F9:E8:64:4B:23:D6:05:F1:DB:8D:21, pkey_fingerprint=03:6B:E4:D3:73:82:D5:B4:EB:98:96:BB:56:77:A2:48:C2:73:A0:03 posttls-finger: Verified TLS connection established to mx.dmz.tait.net.nz[192.168.20.196]:25: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 posttls-finger: > EHLO maimbo.tait.net.nz posttls-finger: < 250-mx.tait.net.nz posttls-finger: < 250-PIPELINING posttls-finger: < 250-SIZE 2048 posttls-finger: < 250-ETRN posttls-finger: < 250-ENHANCEDSTATUSCODES posttls-finger: < 250-8BITMIME posttls-finger: < 250-DSN posttls-finger: < 250 SMTPUTF8 posttls-finger: > QUIT posttls-finger: < 221 2.0.0 Bye Which of course now includes the "Verified TLS connection established..." line. ** Affects: postfix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885403 Title: posttls-finger fails to connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1885403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: [SRU] after upgrade to 20.04: dane support is not working
Hi everyone. I too have tested the proposed postfix release, and it fixes the DANE issue and also passed all my regression tests. :-) There is still an issue with posttls-finger attempting to connect to private/tlsmgr, which fails if it isn't run from /var/spool/postfix as root. (This was actually the symptom originally described by this bug when it was first logged by Jan. I'll raise a separate case for that, and update this case with the bug ID...) Thanks everyone for your efforts in resolving the DANE issue. Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: [SRU] after upgrade to 20.04: dane support is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 1868955] Re: [SRU] after upgrade to 20.04: dane support is not working
Hi Lucas.I'll give it a crack tomorrow and update the case with the results.Thanks, Nick. null -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: [SRU] after upgrade to 20.04: dane support is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: [SRU] after upgrade to 20.04: posttls cannot connect to private/tlsmgr
Hi guys. Sorry for my slow response. Jan what you are seeing is consistent with what I expected. i.e. The addition of the RES_TRUSTAD flag to the postfix code allows the DANE mechanism to work. During my debugging of the postfix code, I was using posttls-finger, but I never encountered the issue with the "posttls-finger: warning: connect to private/tlsmgr: No such file or directory" message at all. But of course when I'm running posttls-finger as part of my postfix installation I do see that message (BTW I'm still on the unpatched version at this moment). I'm not sure why the behaviour is different, but it does seem that these are two different problems. Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: [SRU] after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
I (by accident) discovered that glibc has introduced a new resolver option in resolv.h: #define RES_TRUSTAD 0x0400 /* Request AD bit, keep it in responses. */ I've done some testing with this, and it resolves the issue with the AD flag not being returned. So based on this I think this bug needs to be changed back to postfix, and postfix needs to be updated to include this flag? Ideally the behaviour require should be: * If RES_TRUSTAD is defined, then postfix should use that instead of RES_USE_DNSSEC and RES_USE_EDNS0. * If RES_TRUSTAD is not defined, then postfix should maintain current behaviour of using RES_USE_DNSSEC and RES_USE_EDNS0. If the above is implemented it would reduce the size of the DNS queries, because they won't include the RRSIG records that "come for free" when the DO bit is set (based on RES_USE_DNSSEC). Thanks, Nick. ** Package changed: glibc (Ubuntu) => postfix (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
I've created a C program (attached) which demonstrates the issue. It can be compiled using the following command: gcc dnsadtest.c -lresolv This command generates an executable called "a.out". If I run a.out on Ubuntu 18.04 (bionic) I get the following output: length of answer = 251 id = 10740 opcode = 0 rcode = 0 rd flag = 1 tc flag = 0 aa flag = 0 qr flag = 1 cd flag = 0 ad flag = 1 ra flag = 1 qdcount = 256 ancount = 512 nscount = 0 arcount = 256 You can see that the output includes "ad flag = 1". But if I run a.out on Ubuntu 20.04 (focal) I get the following output: length of answer = 251 id = 48769 opcode = 0 rcode = 0 rd flag = 1 tc flag = 0 aa flag = 0 qr flag = 1 cd flag = 0 ad flag = 0 ra flag = 1 qdcount = 256 ancount = 512 nscount = 0 arcount = 256 And you can see that the output includes "ad flag = 0". Based on this I believe there is a bug in the DNS resolver in Ubuntu 20.04. Unfortunately my 18.04 server is 32-bit and by 20.04 server is 64-bit, but my testing gives the following results: 18.04 32-bit = libc6:i386 2.27-3ubuntu1 = works (ad flag = 1) 20.04 64-bit = libc6:amd64 2.31-0ubuntu9 = exhibits the issue (ad flag = 0) 20.04 32-bit* = libc6-i386 2.31-0ubuntu9 = exhibits the issue (ad flag = 0) * = running a.out compiled on 32-bit machine So it looks to me like the problem was introduced in the libc6 package somewhere between version 2.28 and 2.31 (inclusive). Can anyone corroborate my findings? Thanks, Nick. ** Attachment added: "C program to demonstrate AD flag issue" https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+attachment/5380849/+files/dnsadtest.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
Sorry for the delay in providing an update... My theory about the systemd-resolved DNSSEC option proved incorrect. So taking a step back, here is what I know about the problem that I am observing (i.e. specific to my test set-up): * posttls-finger makes three DNS queries: The first query is for an MX record (which returns NODATA), then an A record (which returns a valid IP address), and finally a record (which returns NODATA). * None of these include the AD flag in the request (question) - which is different from the behaviour seen when using 'dig' - but as it turns out, you don't need to include AD in the request to get AD in the reply. So this wasn't the problem. * All three queries include the DO flag (to request RRSIG records). * Using Wireshark I can see that the DNS response coming back to the 3 queries includes the AD flag (and the DO flag, and also RRSIG/NSEC3 records as appropriate). * However in spite of this, the DNS results returned from the C functions indicate AD=0 - i.e. they are saying that AD flag isn't present in the response, even though (from the Wireshark trace) it clearly is. * Based on this, my hypothesis is that the issue is with the C functions (libresolv). So my plan now is to write a C program to test this theory, which will make a DNS query and then check the AD flag. If my theory is correct then running the same program on Ubuntu 20.04 and an older distribution should give different results. Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
Hi guys. I've made some progress with narrowing down the cause of this problem. It looks like the whole "private/tlsmgr" thing is a bit of a red herring, and the actual problem seems to be that the DNS query that is sent lacks the AD flag. I've confirmed that RES_USE_DNSSEC is included in the flags when the DNS functions are called within the code, so I'm suspecting that systemd.resolvd has something to do with it. E.g. I've just noticed that when I run "systemd-resolve --status", the output includes: DNSSEC supported: no Which looks like a pretty good reason for this behaviour. Tomorrow I'll try changing the systemd.resolvd settings to enable DNSSEC and see if that makes a difference. Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777125] Re: On boot up NetworkManager runs nm_dispatcher for only 1 of 2 tun interfaces
I can confirm that this issue hasn't happened in over 1 year. Please close? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777125 Title: On boot up NetworkManager runs nm_dispatcher for only 1 of 2 tun interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1777125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876691] Re: Login screen suspends even if disabled
*** This bug is a duplicate of bug 1874639 *** https://bugs.launchpad.net/bugs/1874639 ** This bug has been marked a duplicate of bug 1874639 desktop pcs start to suspend by default -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876691 Title: Login screen suspends even if disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1876691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
Hi Jan. Thanks for sending me that blogpost. I found it a really good read! :-) I tried downloading some open-source code one other time (can't actually remember what it was), and got horribly confused, but maybe (like you) I might feel inspired to have another crack at some stage... Nick. On 19/05/20 10:25 pm, Jan Büren wrote: > Hi Nick, > yep. My workaround was to change this to dane instead of dane-only. > > It is a tiny bit disappointing that it is still broken because I prefer to > use ubuntu as a server system instead of debian. > Reading this discussion I guess the feature is working in debian but not in > ubuntu. > > Additionally I resisted building Postfix from source to detect the > deeper bug reason but if this bug doesn't process maybe this would be an > option. > > I enjoyed the idea from this blogpost: > https://briefings.threeletter.agency/post/120317637998/fixing-postfix-a > -trip-down-a-smtp-tls-rabbit > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
I have this issue also, but my set-up involves having my submission server send all emails to an internal mail relay, which then sends to the destination SMTP server. I'm using "dane-only" for the connection from the submission server to the mail relay, meaning that it is used for all external outgoing mail. So I'm seeing the same same behaviour as described above, but the deferred message is slightly different: to=, relay=none, delay=0.13, delays=0.1/0.02/0.01/0, dsn=4.7.5, status=deferred (no TLSA records found) I can only assume that the different message is due to a difference such as not using MX look-up to send to the mail relay? But I thought I'd mention it in case it is relevant? And just to confirm, yes this problem started after I performed the dist-upgrade to Focal Fossa. FYI As a workaround I've changed to using "encrypt" instead of "dane-only". I'm happy to provide more detailed information (e.g. configuration files) if it would help? Thanks, Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811098] Re: [SRU] ceilometer writing snmp credentials to log file
This flaw has been assigned as CVE-2019-3830 https://access.redhat.com/security/cve/cve-2019-3830 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3830 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811098 Title: [SRU] ceilometer writing snmp credentials to log file To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1811098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811098] Re: [SRU] ceilometer writing snmp credentials to log file
I agree with VMT's rating of class A. Will a CVE be requested for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811098 Title: [SRU] ceilometer writing snmp credentials to log file To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1811098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777125] Re: On boot up NetworkManager runs nm_dispatcher for only 1 of 2 tun interfaces
This bug may have been fixed. In the last couple of months I've rebooted at least half a dozen times and it hasn't occurred. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777125 Title: On boot up NetworkManager runs nm_dispatcher for only 1 of 2 tun interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1777125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777125] [NEW] On boot up NetworkManager runs nm_dispatcher for only 1 of 2 tun interfaces
Public bug reported: I have two tun interfaces used with OpenVPN, called tun0 (UDP peer-to- peer VPN) and tun1 (TCP server VPN), and I have a script in /etc/network /if-up.d which I use to add routing table entries when the interface comes up. (FYI The reason for adding routes in an if-up.d script is so I can administer all the policy-based routes in one place.) When I start up OpenVPN for the tun0 interface, the if-up.d scripts run successfully for that interface. And when I start up OpenVPN for the tun1 interface, the if-up.d scripts run successfully for that interface. So I know that everything is configured correctly. BTW The two OpenVPN instances are configured as systemd services called openvpn-server@p2p.service and openvpn-server@server.service, and neither tun0 and tun1 are configured in /etc/network/interfaces. However around 50% of the time when I reboot, the if-up.d scripts are run for only one of the two interfaces (even though both interfaces had started successfully), and it seems random which one. (The other 50% of the time it works properly and runs the if-up.d scripts for both interfaces.) As far as I can tell, it is NetworkManager which is supposed to start nm-dispatcher to run the if-up.d scripts when each tun interface comes up, and it seems that if both interfaces come up at the same time, then it only runs nm-dispatcher for one of them? I've pasted below an extract from my syslog after a reboot, where nm- dispatcher was only run for tun1, not tun0: $ egrep 'NetworkManager|nm-dispatcher' /var/log/syslog Jun 15 20:49:55 maimbo NetworkManager[1015]: [1529052595.6455] NetworkManager (version 1.10.6) is starting... (for the first time) Jun 15 20:49:55 maimbo NetworkManager[1015]: [1529052595.6456] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Jun 15 20:49:55 maimbo NetworkManager[1015]: [1529052595.8380] manager[0x55bf3e4fe050]: monitoring kernel firmware directory '/lib/firmware'. Jun 15 20:49:55 maimbo NetworkManager[1015]: [1529052595.8387] monitoring ifupdown state file '/run/network/ifstate'. Jun 15 20:49:55 maimbo dbus-daemon[860]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.26' (uid=0 pid=1015 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Jun 15 20:49:58 maimbo NetworkManager[1015]: [1529052598.3561] hostname: hostname: using hostnamed Jun 15 20:49:58 maimbo dbus-daemon[860]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.26' (uid=0 pid=1015 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Jun 15 20:49:58 maimbo NetworkManager[1015]: [1529052598.3562] hostname: hostname changed from (none) to "maimbo" Jun 15 20:49:58 maimbo NetworkManager[1015]: [1529052598.3572] dns-mgr[0x55bf3e51b970]: init: dns=systemd-resolved, rc-manager=symlink, plugin=systemd-resolved Jun 15 20:49:58 maimbo NetworkManager[1015]: [1529052598.3585] manager[0x55bf3e4fe050]: rfkill: WiFi hardware radio set enabled Jun 15 20:49:58 maimbo NetworkManager[1015]: [1529052598.3585] manager[0x55bf3e4fe050]: rfkill: WWAN hardware radio set enabled Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7231] init! Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7234] interface-parser: parsing file /etc/network/interfaces Jun 15 20:49:59 maimbo nm-dispatcher: req:1 'hostname': new request (2 scripts) Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7234] interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/* Jun 15 20:49:59 maimbo nm-dispatcher: req:1 'hostname': start running ordered scripts... Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7235] interfaces file /etc/network/interfaces.d/* doesn't exist Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7236] interface-parser: finished parsing file /etc/network/interfaces Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7243] guessed connection type (enp3s3) = 802-3-ethernet Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7244] update_connection_setting_from_if_block: name:enp3s3, type:802-3-ethernet, id:Ifupdown (enp3s3), uuid: 40b6c586-e29c-6c7e-50ee-b622c62bcef9 Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7248] adding enp3s3 to connections Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7248] adding iface enp3s3 to eni_ifaces Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7249] deleting enp3s3 from connections Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7250] guessed connection type (enp3s3) = 802-3-ethernet Jun 15 20:49:59 maimbo NetworkManager[1015]: [1529052599.7250] update_connection_settin
[Bug 1633698] [NEW] ufw before6.rules adds echo-request and echo-response rules to wrong chain
Public bug reported: The default before6.rules file that is installed with the ufw package contains a copy/paste error. It is apparent that the intention is to add rules for echo-request and echo-response to the following chains: ufw6-before-input ufw6-before-output ufw6-before-forward However there is a copy/paste error and instead of adding the rules to ufw6-before-output, it adds it to ufw6-before-input a second time. The result is that the rules are absent from ufw6-before-output. The file that needs to be fixed in the package is: /usr/share/ufw/iptables/before6.rules Here is what diff -u shows if I compare the original file to the corrected version: --- /usr/share/ufw/iptables/before6.rules 2016-04-15 17:16:29.0 +1200 +++ ufw_fixed_before6.rules 2016-10-15 23:00:57.763041239 +1300 @@ -77,8 +77,8 @@ -A ufw6-before-output -p icmpv6 --icmpv6-type time-exceeded -j ACCEPT # codes 0-2 -A ufw6-before-output -p icmpv6 --icmpv6-type parameter-problem -j ACCEPT --A ufw6-before-input -p icmpv6 --icmpv6-type echo-request -j ACCEPT --A ufw6-before-input -p icmpv6 --icmpv6-type echo-reply -j ACCEPT +-A ufw6-before-output -p icmpv6 --icmpv6-type echo-request -j ACCEPT +-A ufw6-before-output -p icmpv6 --icmpv6-type echo-reply -j ACCEPT -A ufw6-before-output -p icmpv6 --icmpv6-type router-solicitation -m hl --hl-eq 255 -j ACCEPT -A ufw6-before-output -p icmpv6 --icmpv6-type neighbor-advertisement -m hl --hl-eq 255 -j ACCEPT -A ufw6-before-output -p icmpv6 --icmpv6-type neighbor-solicitation -m hl --hl-eq 255 -j ACCEPT The impact of this error is minor because the ufw.conf file sets the default outbound policy to accept: DEFAULT_OUTPUT_POLICY="ACCEPT" Of course if anyone changed the default outbound policy then the error would mean that pings made from the server to other machines would be blocked. I will attach the original and my fixed version of before6.rules to this bug report. Thanks for taking the time to look at this issue. Nick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ufw 0.35-2 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 Date: Sat Oct 15 23:09:04 2016 InstallationDate: Installed on 2016-10-14 (1 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release i386 (20161012.1) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 yakkety ** Attachment added: "Original and fixed versions of before6.rules" https://bugs.launchpad.net/bugs/1633698/+attachment/4761441/+files/ufw_original_and_fixed_before6.rules.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633698 Title: ufw before6.rules adds echo-request and echo-response rules to wrong chain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1633698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449922] Re: point-to-point interface routes marked inactive
This bug appears to be fixed now. My Quagga package version is: 0.99.24.1-2 :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449922 Title: point-to-point interface routes marked inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quagga/+bug/1449922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449922] [NEW] point-to-point interface routes marked inactive
Public bug reported: After upgrading to Ubuntu 15.04, I discovered that the network routes that were supposed to be added by zebra for my openvpn tun0 interface weren't there. On further investigation it seems that quagga is getting the wrong IP details for this point-to-point interface. FYI This openvpn interface (tun0) uses the 'p2p' topology in openvpn configuration. When I first set this up over a year ago I made some notes that included the output from the "show ip route" command (from 'telnet localhost zebra' session) which showed: S>* 192.168.10.0/24 [1/0] via 192.168.10.25, tun0 C>* 192.168.10.25/32 is directly connected, tun0 However since upgrading to Ubuntu 15.04, the equivalent lines now show: S 192.168.10.0/24 [1/0] via 192.168.10.25 inactive C>* 192.168.20.25/32 is directly connected, tun0 The key difference here is the IP address in the 'C' line. In the former case the IP address is the remote end of the tunnel, 192.168.10.25, which is correct. In the latter case, it is the IP address of the local end of the tunnel, 192.168.20.25. Consequently, the route in the 'S' is marked inactive and therefore doesn't get added to the routing table. Here are the details for the tun0 interface from ifconfig: tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:192.168.20.25 P-t-P:192.168.10.25 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:50 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:14080 (14.0 KB) BTW I also have another openvpn interface (tun1) which uses 'subnet' topology (rather than 'p2p'), and it is working fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: quagga 0.99.23.1-1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 20:47:06 2015 ExecutablePath: /usr/lib/quagga/zebra InstallationDate: Installed on 2014-05-04 (360 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) LANG=en_NZ.UTF-8 LANGUAGE=en_NZ:en SourcePackage: quagga UpgradeStatus: Upgraded to vivid on 2015-04-26 (3 days ago) mtime.conffile..etc.quagga.daemons: 2014-06-08T22:14:02.457222 ** Affects: quagga (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449922 Title: point-to-point interface routes marked inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quagga/+bug/1449922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253546] [NEW] Screensaver doesn't come on at login screen
Public bug reported: I have discovered that the screen-saver doesn't ever come on (i.e. to blank the screen) while the computer is sitting at the login screen. I have googled and found various methods of changing display settings for the login screen, such as background wallpaper, although many of these apply to older versions of Ubuntu. The most relevant thing I found was instructions for using running gconf-editor as lightdm user, and editing unity-greeter settings. However there were no unity-greeter settings that I could see to control screen-dimming. The screen-saver is an important energy-saving feature. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-greeter 13.10.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 21 21:11:43 2013 InstallationDate: Installed on 2013-05-09 (196 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity-greeter UpgradeStatus: Upgraded to saucy on 2013-10-27 (25 days ago) ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253546 Title: Screensaver doesn't come on at login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1253546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221179] Re: [background] image previews should include shell components
** Changed in: ubuntu-ux Assignee: Nick Tait (jnick-tait) => Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221179 Title: [background] image previews should include shell components To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1221179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977974] Re: Improve background colorization
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesign ** Tags removed: reviewedbydesign ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977974 Title: Improve background colorization To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/977974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925215] Re: keyboard shortcuts overlay and alt-tab show wrong background in the expo view.
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925215 Title: keyboard shortcuts overlay and alt-tab show wrong background in the expo view. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/925215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 967110] Re: Incorrect labels in System Settings-Displays panel for Launcher Placement and Sticky edges options
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967110 Title: Incorrect labels in System Settings-Displays panel for Launcher Placement and Sticky edges options To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/967110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968261] Re: Multimonitor - Only the panel that controls the focused window should draw its title
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/968261 Title: Multimonitor - Only the panel that controls the focused window should draw its title To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/968261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 799890] Re: In Unity the distinction between GVolume, GDrive and GMount is a bit confusing.
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/799890 Title: In Unity the distinction between GVolume, GDrive and GMount is a bit confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/799890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 923384] Re: HUD shows up when switching keyboard layouts with alt-shift
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/923384 Title: HUD shows up when switching keyboard layouts with alt-shift To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/923384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931406] Re: [autohide] app icons in HUD are poorly scaled
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931406 Title: [autohide] app icons in HUD are poorly scaled To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/931406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921249] Re: HUD - Using HUD often results in window losing focus
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921249 Title: HUD - Using HUD often results in window losing focus To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/921249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841902] Re: Dash - Genre filter category in the Music Lens should use a 3 column layout
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841902 Title: Dash - Genre filter category in the Music Lens should use a 3 column layout To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/841902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973063] Re: Starting dash or hud with mouse over launcher desaturates all icons
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973063 Title: Starting dash or hud with mouse over launcher desaturates all icons To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/973063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932143] Re: Update 'desktop' menu so it is fully relevant to desktop functionality
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932143 Title: Update 'desktop' menu so it is fully relevant to desktop functionality To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/932143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906235] Re: Dash- More fixes to layout and alignments
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906235 Title: Dash- More fixes to layout and alignments To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/906235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929183] Re: The search box should not have the glow
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929183 Title: The search box should not have the glow To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/929183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913717] Re: The search box is too opaque and dark
** Tags removed: udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913717 Title: The search box is too opaque and dark To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/913717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 938620] Re: Launcher - Properly colorize icons
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/938620 Title: Launcher - Properly colorize icons To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/938620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926213] Re: Overlay should refer to "Menu Bar" not "Top Bar"
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926213 Title: Overlay should refer to "Menu Bar" not "Top Bar" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/926213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765819] Re: Launcher - Make Launcher left of screen reveal more responsive and less prone to false positives
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765819 Title: Launcher - Make Launcher left of screen reveal more responsive and less prone to false positives To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/765819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861250] Re: alt-tab - quick alt + tab (before the switcher shows) not consistent
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861250 Title: alt-tab - quick alt + tab (before the switcher shows) not consistent To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/861250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 967136] Re: In the Display Settings panel, when changing the 'Launcher placement' option from the drop-down list, the display arrangement widget does not immediately update to reflect the change
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967136 Title: In the Display Settings panel, when changing the 'Launcher placement' option from the drop-down list, the display arrangement widget does not immediately update to reflect the change To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/967136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973181] Re: Dash - System commands presence confuse the definition of App
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973181 Title: Dash - System commands presence confuse the definition of App To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/973181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871900] Re: Dash - When multiple results have equal string match relevancy ranking, those with equal ranking should be then sorted by frequency of use.
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871900 Title: Dash - When multiple results have equal string match relevancy ranking, those with equal ranking should be then sorted by frequency of use. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/871900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 934061] Re: HUD doesn't give the focus back to the active application after dash/hud use
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/934061 Title: HUD doesn't give the focus back to the active application after dash/hud use To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/934061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 961285] Re: [5.8 pre staging] "sticky edge" option does nothing visible
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/961285 Title: [5.8 pre staging] "sticky edge" option does nothing visible To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/961285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869907] Re: Window Management - Unmaximizing a window doesn't return to the initial size/position.
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869907 Title: Window Management - Unmaximizing a window doesn't return to the initial size/position. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/869907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 927952] Re: When I press the Print Screen button, it will not appear in "Save Screenshot" window.
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927952 Title: When I press the Print Screen button, it will not appear in "Save Screenshot" window. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/927952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841750] Re: Dash - horizontal divider line in between categories incorrectly drawn
** Tags removed: udo udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841750 Title: Dash - horizontal divider line in between categories incorrectly drawn To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/841750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 761851] Re: Software Centre - automatically add app icon to launcher
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/761851 Title: Software Centre - automatically add app icon to launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/761851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869900] Re: multimonitor , window management - windows should not open off display
** Tags removed: udo udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869900 Title: multimonitor , window management - windows should not open off display To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/869900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 941066] Re: Dash is totally broken when disabling the blur effect
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941066 Title: Dash is totally broken when disabling the blur effect To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/941066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838232] Re: Alt-tab - Reduce the spread delay for all items other than the initial item the select lands on after alt-tab opens
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838232 Title: Alt-tab - Reduce the spread delay for all items other than the initial item the select lands on after alt-tab opens To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/838232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925021] Re: Launcher - Inserting items into launcher makes unnecessary animations on other monitors
** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925021 Title: Launcher - Inserting items into launcher makes unnecessary animations on other monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/925021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946104] Re: multimonitor: Please give me a way to turn off sticky monitor edges
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946104 Title: multimonitor: Please give me a way to turn off sticky monitor edges To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/946104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932906] Re: HUD loses keypresses for the first second after opening
** Tags removed: udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932906 Title: HUD loses keypresses for the first second after opening To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/932906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919139] Re: window management, multi-monitor - In multi-monitor environment, windows should spread on the monitor in which they reside
** Tags removed: udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919139 Title: window management, multi-monitor - In multi-monitor environment, windows should spread on the monitor in which they reside To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/919139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928805] Re: Launcher, Window Management - Launcher reveal should not be triggered when dragging a window
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/928805 Title: Launcher, Window Management - Launcher reveal should not be triggered when dragging a window To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/928805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924884] Re: Dash - Different states of rating stars, and dimensions
** Tags removed: udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924884 Title: Dash - Different states of rating stars, and dimensions To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/924884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950136] Re: multimonitor, launcher: Provide an option to display either a single launcher or a launcher on each display in a multi-monitor environment
** Tags removed: udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950136 Title: multimonitor, launcher: Provide an option to display either a single launcher or a launcher on each display in a multi-monitor environment To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/950136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844044] Re: Unity Greeter - Add Network Login option
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844044 Title: Unity Greeter - Add Network Login option To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/844044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921305] Re: HUD is over gtk-menu
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921305 Title: HUD is over gtk-menu To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/921305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 967121] Re: Misleading placement of 'Launcher placement' and 'Sticky edges' options in the System Settings-Displays panel
** Tags removed: udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967121 Title: Misleading placement of 'Launcher placement' and 'Sticky edges' options in the System Settings-Displays panel To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/967121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 967027] Re: Menubar representations should not be shown in the arrangement widget of the Displays panel
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967027 Title: Menubar representations should not be shown in the arrangement widget of the Displays panel To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/967027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950404] Re: Launcher Switcher (Super+Tab) selection could be changed by arrow keys too
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950404 Title: Launcher Switcher (Super+Tab) selection could be changed by arrow keys too To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/950404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 834878] Re: Unity greeter password field uses old-fashioned asterisks
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/834878 Title: Unity greeter password field uses old-fashioned asterisks To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/834878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 937193] Re: Dash - lens bar clickable area needs to be expanded
** Tags removed: udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937193 Title: Dash - lens bar clickable area needs to be expanded To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/937193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850984] Re: Dash - Missing category separator line in dash
** Tags removed: udp ** Tags added: reviewedbydesignp ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850984 Title: Dash - Missing category separator line in dash To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/850984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 801784] Re: Gnome3 Control Centre Launcher icon does not correctly represent which panel is currently open
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/801784 Title: Gnome3 Control Centre Launcher icon does not correctly represent which panel is currently open To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/801784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 757650] Re: Unable to select a maximised app by clicking on left edge of the screen
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/757650 Title: Unable to select a maximised app by clicking on left edge of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/757650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 720716] Re: Please add unity Quicklist support
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp udt ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/720716 Title: Please add unity Quicklist support To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/720716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865239] Re: Background colorization should use a different heuristic
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udo udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865239 Title: Background colorization should use a different heuristic To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/865239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932164] Re: Unity Greeter - Replace 'cog' icon in the login box with a icon that represents the selected session
** Changed in: ayatana-design Status: Fix Committed => Fix Released ** Tags removed: udp ** Tags added: reviewedbydesignp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932164 Title: Unity Greeter - Replace 'cog' icon in the login box with a icon that represents the selected session To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/932164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 723861] Re: Right clicking on the desktop still displays the “Create Launcher...” option.
** Tags removed: udo udp udt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/723861 Title: Right clicking on the desktop still displays the “Create Launcher...” option. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/723861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 874380] Re: Launcher - the "Keep in Launcher" quicklist option should change from the current checkbox option to a two state toggle
** Tags removed: udo udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874380 Title: Launcher - the "Keep in Launcher" quicklist option should change from the current checkbox option to a two state toggle To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/874380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891818] Re: Dash - dash is not closed with alt+f4
** Tags removed: udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891818 Title: Dash - dash is not closed with alt+f4 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/891818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966424] Re: Dash - Search box text is clipped
** Tags removed: udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966424 Title: Dash - Search box text is clipped To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/966424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900400] Re: Application title on quicklist should be bold (or more visible)
** Tags removed: udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/900400 Title: Application title on quicklist should be bold (or more visible) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/900400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978785] Re: Dash - reduce frosty effect
** Tags removed: udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/978785 Title: Dash - reduce frosty effect To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/978785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711199] Re: [UIFe] Dash - No message displayed when no results are returned in the Dash
** Tags removed: udo udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711199 Title: [UIFe] Dash - No message displayed when no results are returned in the Dash To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/711199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841847] Re: Dash - unable to select multiple search filters within the same filter category simultaneously
** Tags removed: udo udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841847 Title: Dash - unable to select multiple search filters within the same filter category simultaneously To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/841847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841870] Re: Dash - A expand/collapse arrow is missing from all the filter category headers
** Tags removed: udo udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841870 Title: Dash - A expand/collapse arrow is missing from all the filter category headers To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/841870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844033] Re: Dash - Keyboard navigation for search filters is broken
** Tags removed: udo udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844033 Title: Dash - Keyboard navigation for search filters is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/844033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844055] Re: Unity Greeter - The word "password" should be inside the password entry box, not above it
** Tags removed: udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844055 Title: Unity Greeter - The word "password" should be inside the password entry box, not above it To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/844055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849175] Re: Dash - cursor should change when pointer is over the search field
** Tags removed: udo udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/849175 Title: Dash - cursor should change when pointer is over the search field To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/849175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 863405] Re: Dash - After scrolling to the bottom of the Dash using the cursor keys, navigating back upwards is broken
** Tags removed: udo udp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/863405 Title: Dash - After scrolling to the bottom of the Dash using the cursor keys, navigating back upwards is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/863405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
