From chernousov at help-me-24.com Mon Apr 10 04:36:02 2017 From: chernousov at help-me-24.com (Anton Chernousov) Date: Mon, 10 Apr 2017 11:36:02 +0700 Subject: Bug in Dolphin with create folder menu option Message-ID: Hi! In the localized version of Ubuntu 16.04.2 LTS located strange bug. Dolphin in create folder mode show two options "Create folder" and translated create folder "Создать папку". Screen-shot link: https://files.help-me-24.com/chernousov/blog/images/kubuntu-bugs/create-folder-dolphin-bug.png English version menu item on selection crashed Dolphin, but localized version work fine. How can i fix this? --------------------------------- With best regards, Chernousov Anton (http://help-me-24.com) -------------- next part -------------- A non-text attachment was scrubbed... Name: create-folder-dolphin-bug.png Type: image/png Size: 42047 bytes Desc: not available URL: From cbaptista at opensuse.us Tue Apr 18 14:39:56 2017 From: cbaptista at opensuse.us (Carlos Baptista) Date: Tue, 18 Apr 2017 15:39:56 +0100 Subject: systemd-resolved problem Message-ID: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> Hi, After the upgrade 17.04, the resolver stop using the dns servers configured by DHCP. I have to use our network dns servers. Does anybody know how to configure systemd-resolved ? #systemd-resolve --status Global DNS Domain: mydomain.local DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (anboxbr0) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Link 3 (wlo1) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Link 2 (enp0s25) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes DNS Servers: 192.168.1.5 192.168.2.5 192.168.2.4 8.8.8.8 DNS Domain: mydomain.local #host server01 Host server01 not found: 2(SERVFAIL) #host server01.mydomain.local Host server01.mydomain.local not found: 3(NXDOMAIN) #host server01.mydomain.local 192.168.1.5 Using domain server: Name: 192.168.1.5 Address: 192.168.1.5#53 Aliases: server01.mydomain.local has address 192.168.1.62 Thanks Carlos Baptista From phil_lor at bigpond.com Thu Apr 20 01:43:53 2017 From: phil_lor at bigpond.com (Phil) Date: Thu, 20 Apr 2017 11:43:53 +1000 Subject: Bounced off list Message-ID: <20170420114353.4c48f505@raspberrypi> I'm not receiving mail from this list due to my ISP bouncing my mail again. I don't remember who, at Kubuntu, I contacted previously to have this problem resolved. -- Regards, Phil From a.mani.cms at gmail.com Thu Apr 20 06:24:29 2017 From: a.mani.cms at gmail.com (A. Mani) Date: Thu, 20 Apr 2017 11:54:29 +0530 Subject: Upgrade issue Message-ID: do-release-upgrade is not finding the latest version I have libre kernel installed in 16.10. Can that be a reason? Thanks and Best A Mani Prof(Miss) A Mani CU, ASL, AMS, ISRS, CLC, CMS, IEEE HomePage: http://www.logicamani.in Blog: http://logicamani.blogspot.in/ sip:girlprofessor at ekiga.net From valorie.zimmerman at gmail.com Thu Apr 20 08:15:38 2017 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Thu, 20 Apr 2017 01:15:38 -0700 Subject: Bounced off list In-Reply-To: <20170420114353.4c48f505@raspberrypi> References: <20170420114353.4c48f505@raspberrypi> Message-ID: On Wed, Apr 19, 2017 at 6:43 PM, Phil wrote: > I'm not receiving mail from this list due to my ISP bouncing my mail again. I don't remember who, at Kubuntu, I contacted previously to have this problem resolved. > > -- > Regards, > Phil Phil, you have not "bounced off" because you successfully posted. Unfortunately, your post is off-topic. To put it back on topic -- how are you liking 17.04? Valorie PS: you can always check the archives which is linked to on the list info page [1] to see what you missed. 1. https://lists.ubuntu.com/mailman/listinfo/kubuntu-users -- http://about.me/valoriez From bmarsh at bmarsh.com Thu Apr 20 17:18:16 2017 From: bmarsh at bmarsh.com (Bruce Marshall) Date: Thu, 20 Apr 2017 13:18:16 -0400 Subject: systemd-resolved problem In-Reply-To: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> References: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> Message-ID: <2801dedc-ec74-07be-56e0-c45c85c3ca20@bmarsh.com> On 04/18/2017 10:39 AM, Carlos Baptista wrote: > Hi, > > After the upgrade 17.04, the resolver stop using the dns servers > configured by DHCP. I have to use our network dns servers. > > Does anybody know how to configure systemd-resolved ? > > > #systemd-resolve --status > Global > DNS Domain: mydomain.local > DNSSEC NTA: 10.in-addr.arpa > 16.172.in-addr.arpa > 168.192.in-addr.arpa > 17.172.in-addr.arpa > 18.172.in-addr.arpa > 19.172.in-addr.arpa > 20.172.in-addr.arpa > 21.172.in-addr.arpa > 22.172.in-addr.arpa > 23.172.in-addr.arpa > 24.172.in-addr.arpa > 25.172.in-addr.arpa > 26.172.in-addr.arpa > 27.172.in-addr.arpa > 28.172.in-addr.arpa > 29.172.in-addr.arpa > 30.172.in-addr.arpa > 31.172.in-addr.arpa > corp > d.f.ip6.arpa > home > internal > intranet > lan > local > private > test > > Link 4 (anboxbr0) > Current Scopes: LLMNR/IPv4 LLMNR/IPv6 > LLMNR setting: yes > MulticastDNS setting: no > DNSSEC setting: allow-downgrade > DNSSEC supported: yes > > Link 3 (wlo1) > Current Scopes: none > LLMNR setting: yes > MulticastDNS setting: no > DNSSEC setting: allow-downgrade > DNSSEC supported: yes > > Link 2 (enp0s25) > Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 > LLMNR setting: yes > MulticastDNS setting: no > DNSSEC setting: allow-downgrade > DNSSEC supported: yes > DNS Servers: 192.168.1.5 > 192.168.2.5 > 192.168.2.4 > 8.8.8.8 > DNS Domain: mydomain.local > > > #host server01 > Host server01 not found: 2(SERVFAIL) > > #host server01.mydomain.local > Host server01.mydomain.local not found: 3(NXDOMAIN) > > #host server01.mydomain.local 192.168.1.5 > Using domain server: > Name: 192.168.1.5 > Address: 192.168.1.5#53 > Aliases: > > server01.mydomain.local has address 192.168.1.62 > > > Thanks > > Carlos Baptista > > > > I have this problem too,... and have had it prior to 17.04. Tried various configurations of systemd-resolved but the only way around the problem seems to be a cron job: */10 * * * * /usr/sbin/service systemd-resolved restart The reason it has to be a cron job is that if you run the command one time, problems again show up within about 10 minutes or less/more. From bm_witness at yahoo.com Thu Apr 20 22:13:25 2017 From: bm_witness at yahoo.com (BRM) Date: Thu, 20 Apr 2017 22:13:25 +0000 (UTC) Subject: systemd-resolved problem In-Reply-To: <2801dedc-ec74-07be-56e0-c45c85c3ca20@bmarsh.com> References: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> <2801dedc-ec74-07be-56e0-c45c85c3ca20@bmarsh.com> Message-ID: <422149509.5378838.1492726405872@mail.yahoo.com> Curious: is this the bug you're coming across - https://github.com/systemd/systemd/issues/5745 Ben On Thursday, April 20, 2017 1:19 PM, Bruce Marshall wrote: On 04/18/2017 10:39 AM, Carlos Baptista wrote: > Hi, > > After the upgrade 17.04, the resolver stop using the dns servers > configured by DHCP. I have to use our network dns servers. > > Does anybody know how to configure systemd-resolved ? > > > #systemd-resolve --status > Global >          DNS Domain: mydomain.local >          DNSSEC NTA: 10.in-addr.arpa > 16.172.in-addr.arpa > 168.192.in-addr.arpa > 17.172.in-addr.arpa > 18.172.in-addr.arpa > 19.172.in-addr.arpa > 20.172.in-addr.arpa > 21.172.in-addr.arpa > 22.172.in-addr.arpa > 23.172.in-addr.arpa > 24.172.in-addr.arpa > 25.172.in-addr.arpa > 26.172.in-addr.arpa > 27.172.in-addr.arpa > 28.172.in-addr.arpa > 29.172.in-addr.arpa > 30.172.in-addr.arpa > 31.172.in-addr.arpa > corp > d.f.ip6.arpa >                      home >                      internal >                      intranet >                      lan >                      local >                      private >                      test > > Link 4 (anboxbr0) >      Current Scopes: LLMNR/IPv4 LLMNR/IPv6 >        LLMNR setting: yes > MulticastDNS setting: no >      DNSSEC setting: allow-downgrade >    DNSSEC supported: yes > > Link 3 (wlo1) >      Current Scopes: none >        LLMNR setting: yes > MulticastDNS setting: no >      DNSSEC setting: allow-downgrade >    DNSSEC supported: yes > > Link 2 (enp0s25) >      Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 >        LLMNR setting: yes > MulticastDNS setting: no >      DNSSEC setting: allow-downgrade >    DNSSEC supported: yes >          DNS Servers: 192.168.1.5 >                      192.168.2.5 >                      192.168.2.4 >                      8.8.8.8 >          DNS Domain: mydomain.local > > > #host server01 > Host server01 not found: 2(SERVFAIL) > > #host server01.mydomain.local > Host server01.mydomain.local not found: 3(NXDOMAIN) > > #host server01.mydomain.local 192.168.1.5 > Using domain server: > Name: 192.168.1.5 > Address: 192.168.1.5#53 > Aliases: > > server01.mydomain.local has address 192.168.1.62 > > > Thanks > > Carlos Baptista > > > > I have this problem too,...  and have had it prior to 17.04. Tried various configurations of systemd-resolved but the only way around the problem seems to be a cron job: */10 * * * *  /usr/sbin/service systemd-resolved restart The reason it has to be a cron job is that if you run the command one time,  problems again show up within about 10 minutes or less/more. -- kubuntu-users mailing list kubuntu-users at lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From valorie.zimmerman at gmail.com Fri Apr 21 04:29:04 2017 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Thu, 20 Apr 2017 21:29:04 -0700 Subject: KDE PIM update for Zesty available for testers Message-ID: Hi folks, Since we missed by a whisker getting updated PIM (kontact, kmail, akregator, kgpg etc..) into Zesty for release day, and we believe it is important that our users have access to this significant update, packages are now available for testers in the Kubuntu backports landing ppa. Read the details on the website: http://kubuntu.org/news/kde-pim-update-for-zesty-available-for-testers/ I've posted this news on Kubuntu Forums, and Twitter (my own account). Feel free to spread the word! Valorie -- http://about.me/valoriez From mrvanes at gmail.com Fri Apr 21 07:44:56 2017 From: mrvanes at gmail.com (Martin van Es) Date: Fri, 21 Apr 2017 09:44:56 +0200 Subject: KDE PIM update for Zesty available for testers In-Reply-To: References: Message-ID: Hi, I've tried the upgrade but fail to understand the dependancy circle I'm encountering. Disclaimer:I'm not a packaging expert! aptitude suggests to remove 7 packages, of which knotes is one. This is because knotes has both version 16.04.3 and 16.12.3 of kdepim-doc in the breaks and replaces dependancies. Like I said, I'm not an expert, but it seems strange for knotes 16.12.3 to have a break dependancy on kdepim-doc 16.12.3? A little more research reveals that kdepim-doc 16.12.3 is a transitional package and can be removed. So that would explain the problems, but fact is, that is not the suggested solution? In some sort of same way kdepim-runtime breaks kdepimkio-plugins 16.04.3 but here the solution isn't so obvious other than removing kdepimkio-plugins. Another circle: libkf5messagecomposer5 depends on kf5-messagelib-data and resolving this leads to a circle, unless I remove libkf5messagecomposer5 completely. The same holds for libkf5messagecore5, libkf5messagelist5, libkfmessageviewer5 and libkf5mailcommon5. They are all 16.04.3 versions so I assume it's safe to remove them? I've canceled the upgrade for now. Best regards, Martin On Fri, Apr 21, 2017 at 6:29 AM, Valorie Zimmerman wrote: > Hi folks, > > Since we missed by a whisker getting updated PIM (kontact, kmail, > akregator, kgpg etc..) into Zesty for release day, and we believe it > is important that our users have access to this significant update, > packages are now available for testers in the Kubuntu backports > landing ppa. Read the details on the website: > > http://kubuntu.org/news/kde-pim-update-for-zesty-available-for-testers/ > > I've posted this news on Kubuntu Forums, and Twitter (my own account). > Feel free to spread the word! > > Valorie > > -- > http://about.me/valoriez > > -- > kubuntu-devel mailing list > kubuntu-devel at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel -- If 'but' was any useful, it would be a logic operator From cbaptista at opensuse.us Fri Apr 21 13:36:06 2017 From: cbaptista at opensuse.us (Carlos Baptista) Date: Fri, 21 Apr 2017 14:36:06 +0100 Subject: systemd-resolved problem In-Reply-To: <2801dedc-ec74-07be-56e0-c45c85c3ca20@bmarsh.com> References: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> <2801dedc-ec74-07be-56e0-c45c85c3ca20@bmarsh.com> Message-ID: Hi, well, I have a different workaround. I replace the resolv.conf at network connect. But I would prefer to solve the systemd issue... Carlos On 20-04-2017 18:18, Bruce Marshall wrote: > On 04/18/2017 10:39 AM, Carlos Baptista wrote: >> Hi, >> >> After the upgrade 17.04, the resolver stop using the dns servers >> configured by DHCP. I have to use our network dns servers. >> >> Does anybody know how to configure systemd-resolved ? >> >> >> #systemd-resolve --status >> Global >> DNS Domain: mydomain.local >> DNSSEC NTA: 10.in-addr.arpa >> 16.172.in-addr.arpa >> 168.192.in-addr.arpa >> 17.172.in-addr.arpa >> 18.172.in-addr.arpa >> 19.172.in-addr.arpa >> 20.172.in-addr.arpa >> 21.172.in-addr.arpa >> 22.172.in-addr.arpa >> 23.172.in-addr.arpa >> 24.172.in-addr.arpa >> 25.172.in-addr.arpa >> 26.172.in-addr.arpa >> 27.172.in-addr.arpa >> 28.172.in-addr.arpa >> 29.172.in-addr.arpa >> 30.172.in-addr.arpa >> 31.172.in-addr.arpa >> corp >> d.f.ip6.arpa >> home >> internal >> intranet >> lan >> local >> private >> test >> >> Link 4 (anboxbr0) >> Current Scopes: LLMNR/IPv4 LLMNR/IPv6 >> LLMNR setting: yes >> MulticastDNS setting: no >> DNSSEC setting: allow-downgrade >> DNSSEC supported: yes >> >> Link 3 (wlo1) >> Current Scopes: none >> LLMNR setting: yes >> MulticastDNS setting: no >> DNSSEC setting: allow-downgrade >> DNSSEC supported: yes >> >> Link 2 (enp0s25) >> Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 >> LLMNR setting: yes >> MulticastDNS setting: no >> DNSSEC setting: allow-downgrade >> DNSSEC supported: yes >> DNS Servers: 192.168.1.5 >> 192.168.2.5 >> 192.168.2.4 >> 8.8.8.8 >> DNS Domain: mydomain.local >> >> >> #host server01 >> Host server01 not found: 2(SERVFAIL) >> >> #host server01.mydomain.local >> Host server01.mydomain.local not found: 3(NXDOMAIN) >> >> #host server01.mydomain.local 192.168.1.5 >> Using domain server: >> Name: 192.168.1.5 >> Address: 192.168.1.5#53 >> Aliases: >> >> server01.mydomain.local has address 192.168.1.62 >> >> >> Thanks >> >> Carlos Baptista >> >> >> >> > I have this problem too,... and have had it prior to 17.04. Tried > various configurations of systemd-resolved but the only way around the > problem seems to be a cron job: > > > */10 * * * * /usr/sbin/service systemd-resolved restart > > > The reason it has to be a cron job is that if you run the command one > time, problems again show up within about 10 minutes or less/more. > > > > > From a.mani.cms at gmail.com Fri Apr 21 13:45:09 2017 From: a.mani.cms at gmail.com (A. Mani) Date: Fri, 21 Apr 2017 19:15:09 +0530 Subject: Upgrade issue In-Reply-To: References: Message-ID: On Thu, Apr 20, 2017 at 11:54 AM, A. Mani wrote: > do-release-upgrade is not finding the latest version > I have libre kernel installed in 16.10. Can that be a reason? it was due to Prompt=lts fixed Best A Mani Prof(Miss) A Mani CU, ASL, AMS, ISRS, CLC, CMS, IEEE HomePage: http://www.logicamani.in Blog: http://logicamani.blogspot.in/ sip:girlprofessor at ekiga.net From luca at ventoso.org Fri Apr 21 17:25:50 2017 From: luca at ventoso.org (Luca Olivetti) Date: Fri, 21 Apr 2017 19:25:50 +0200 Subject: systemd-resolved problem In-Reply-To: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> References: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> Message-ID: <20d2001f-4114-c2d2-d441-7e2c215d354e@ventoso.org> El 18/04/17 a les 16:39, Carlos Baptista ha escrit: > Hi, > > After the upgrade 17.04, the resolver stop using the dns servers > configured by DHCP. I have to use our network dns servers. > > Does anybody know how to configure systemd-resolved ? See here if you want to disable it and use a working resolver: https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu Bye -- Luca From bmarsh at bmarsh.com Fri Apr 21 18:51:33 2017 From: bmarsh at bmarsh.com (Bmarsh) Date: Fri, 21 Apr 2017 14:51:33 -0400 Subject: systemd-resolved problem In-Reply-To: <20d2001f-4114-c2d2-d441-7e2c215d354e@ventoso.org> References: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> <20d2001f-4114-c2d2-d441-7e2c215d354e@ventoso.org> Message-ID: I just ran an update for 17.04 and they updated most of the system-resolved items. Hope it got fixed. From: Luca Olivetti To: kubuntu-users at lists.ubuntu.com Subject: Re: systemd-resolved problem Date: 4/21/17, 1:25 PM El 18/04/17 a les 16:39, Carlos Baptista ha escrit: > Hi, > > After the upgrade 17.04, the resolver stop using the dns servers > configured by DHCP. I have to use our network dns servers. > > Does anybody know how to configure systemd-resolved ? See here if you want to disable it and use a working resolver: https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu Bye -- Luca -- kubuntu-users mailing list kubuntu-users at lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmarsh at bmarsh.com Fri Apr 21 20:08:35 2017 From: bmarsh at bmarsh.com (Bruce Marshall) Date: Fri, 21 Apr 2017 16:08:35 -0400 Subject: systemd-resolved problem In-Reply-To: References: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> <20d2001f-4114-c2d2-d441-7e2c215d354e@ventoso.org> Message-ID: <126b4773-4c25-caad-4128-318bc6c437f8@bmarsh.com> On 04/21/2017 02:51 PM, Bmarsh wrote: > I just ran an update for 17.04 and they updated most of the > system-resolved items. > > Hope it got fixed. > No such luck..... It did NOT solve the problem. > >> *From: * Luca Olivetti > >> *To: * kubuntu-users at lists.ubuntu.com >> >> *Subject: * Re: systemd-resolved problem >> *Date: * 4/21/17, 1:25 PM >> >> >> >> El 18/04/17 a les 16:39, Carlos Baptista ha escrit: >> > Hi, >> > >> > After the upgrade 17.04, the resolver stop using the dns servers >> > configured by DHCP. I have to use our network dns servers. >> > >> > Does anybody know how to configure systemd-resolved ? >> >> See here if you want to disable it and use a working resolver: >> >> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu >> >> >> >> Bye >> -- >> Luca >> >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users >> > > -- "Always remember to pillage BEFORE you burn." -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil_lor at bigpond.com Fri Apr 21 23:16:18 2017 From: phil_lor at bigpond.com (Phil) Date: Sat, 22 Apr 2017 09:16:18 +1000 Subject: Bounced off list In-Reply-To: References: <20170420114353.4c48f505@raspberrypi> Message-ID: <20170422091618.4dd4f8b2@raspberrypi> On Thu, 20 Apr 2017 01:15:38 -0700 Valorie Zimmerman wrote: > Phil, you have not "bounced off" because you successfully posted. > Unfortunately, your post is off-topic. To put it back on topic -- how > are you liking 17.04? Thank you for your reply Valorie, The last message that I received from the list was on the 17/02 and it was from you announcing that 16.04.2 update was available. Since I'm on the kubuntu-users-bounces list then I assumed that I was now off the list. I'm also on the users-bounces list with several other mail list but I'm still receiving mail from all except one. This has occurred since my ISP changed over to IMAP mail. Regarding 17.04. There was a bug in Discover in version 16.10 that prevented Discover from performing updates. That bug has carried over into 17.04, at least in my installation. The notifier show that there are updates yet Discover shows that my system is up to date. Sudo apt-get updates shows that this is not the case. Other than that problem I do like Kubuntu 17.04. -- Regards, Phil From paul at lemmons.name Sat Apr 22 17:37:12 2017 From: paul at lemmons.name (Paul Lemmons) Date: Sat, 22 Apr 2017 17:37:12 +0000 Subject: systemd-resolved problem In-Reply-To: <126b4773-4c25-caad-4128-318bc6c437f8@bmarsh.com> References: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> <20d2001f-4114-c2d2-d441-7e2c215d354e@ventoso.org> <126b4773-4c25-caad-4128-318bc6c437f8@bmarsh.com> Message-ID: It did not fix it for me. On Fri, Apr 21, 2017 at 1:08 PM Bruce Marshall wrote: > On 04/21/2017 02:51 PM, Bmarsh wrote: > > I just ran an update for 17.04 and they updated most of the > system-resolved items. > > Hope it got fixed. > > > No such luck..... It did NOT solve the problem. > > > > > > > > > *From: * Luca Olivetti > *To: * kubuntu-users at lists.ubuntu.com > *Subject: * Re: systemd-resolved problem > *Date: * 4/21/17, 1:25 PM > > El 18/04/17 a les 16:39, Carlos Baptista ha escrit: > > Hi, > > > > After the upgrade 17.04, the resolver stop using the dns servers > > configured by DHCP. I have to use our network dns servers. > > > > Does anybody know how to configure systemd-resolved ? > > See here if you want to disable it and use a working resolver: > > > https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu > > > Bye > -- > Luca > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > > > > > > -- > "Always remember to pillage BEFORE you burn." > > -- > kubuntu-users mailing list > kubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul at lemmons.name Sat Apr 22 17:38:09 2017 From: paul at lemmons.name (Paul Lemmons) Date: Sat, 22 Apr 2017 17:38:09 +0000 Subject: systemd-resolved problem In-Reply-To: References: <4a6f0006-cc8e-3252-c0f7-465ba10635a5@opensuse.us> <20d2001f-4114-c2d2-d441-7e2c215d354e@ventoso.org> <126b4773-4c25-caad-4128-318bc6c437f8@bmarsh.com> Message-ID: Does anybody know, is there a problem open on this anywhere? On Sat, Apr 22, 2017 at 10:37 AM Paul Lemmons wrote: > It did not fix it for me. > > > On Fri, Apr 21, 2017 at 1:08 PM Bruce Marshall wrote: > >> On 04/21/2017 02:51 PM, Bmarsh wrote: >> >> I just ran an update for 17.04 and they updated most of the >> system-resolved items. >> >> Hope it got fixed. >> >> >> No such luck..... It did NOT solve the problem. >> >> >> >> >> >> >> >> >> *From: * Luca Olivetti >> *To: * kubuntu-users at lists.ubuntu.com >> *Subject: * Re: systemd-resolved problem >> *Date: * 4/21/17, 1:25 PM >> >> El 18/04/17 a les 16:39, Carlos Baptista ha escrit: >> > Hi, >> > >> > After the upgrade 17.04, the resolver stop using the dns servers >> > configured by DHCP. I have to use our network dns servers. >> > >> > Does anybody know how to configure systemd-resolved ? >> >> See here if you want to disable it and use a working resolver: >> >> >> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu >> >> >> Bye >> -- >> Luca >> >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users >> >> >> >> >> >> -- >> "Always remember to pillage BEFORE you burn." >> >> -- >> kubuntu-users mailing list >> kubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From valorie.zimmerman at gmail.com Thu Apr 27 07:16:37 2017 From: valorie.zimmerman at gmail.com (Valorie Zimmerman) Date: Thu, 27 Apr 2017 00:16:37 -0700 Subject: Kubuntu Release Manager / Kubuntu Promotion team Message-ID: Hi folks, now that Artful Aardvark 17.10 archive is now open, and our developers are preparing packages for testing and upload, we're heading towards Alpha 1 which is scheduled for June 29. So no hurry, but why not get things set up now? I helped Walter (wxl) who functioned as our RM last cycle, and it wasn't *hard* -- but there were lots of steps. I think a small team would do this job better than one person, so I'd like people to look at the job and step up for this cycle. It would be great is someone who likes Facebook, can be active there, for instance. Same with Kubuntuforums, Twitter, Reddit, G+. In fact, this call might be spread to those places too! By the way, Walter has promised to help us out if we need it. I was thinking of a separate IRC channel and/or a Telegram group, but we've been using #kubuntu-council, and Kubuntu Council Telegram group which are bridged, and it's working well. I think that members of the Council who aren't packaging will want to help out in this way anyway. The IRC channel is public, and I'll add anyone to the T-group who wants that. If that channel gets too busy or the rest of the KC wants it separate, we can do that too. I have a wiki page on Phabricator about the RM work: https://phabricator.kde.org/w/kubuntu/release-management/. Walter made a page for us on the KDE wiki: https://community.kde.org/Kubuntu/ReleaseManagement . And today Walter shared an older wiki page that they have used to keep track of who is doing what in Lubuntu: https://wiki.ubuntu.com/Lubuntu/Developers/PrePostReleaseTODO To get organized we could do a similar page on one of the wikis, LP, or instead -- anybody have any ideas? Step up folks, and let's get set up. Valorie PS: Supposedly UOS is next week, but http://summit.ubuntu.com/ is still empty. I think the big changes that Mark Shuttleworth announced have thrown people into a bit of a loop. When it is scheduled, maybe we could have a session and do this planning in real-time? -- http://about.me/valoriez