[Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Ok, I figured out kernel compiling. And many git bisects later, I think I found the commit causing the issue. It's commit 4eb4bb735a536d922fc92de347b90ea290067c71 that causes my WiFi to become unstable. If I go one commit earlier (ef8f38d37265d79607e1fc132e28fadec8f51056) it all works perfectly, using that right now. The commit causing breakage is a pretty short patch, but I don't really understand what it does: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-next&id=4eb4bb735a536d922fc92de347b90ea290067c71 I hope this helps at least! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Version 5.15.0-23-generic still works great for me, no dropping WiFi at all. Version 5.15.0-25-generic is where the troubles started. Version 5.15.0-27 from the updates this morning has the same issues. For completeness sake, my output of lspci for the wireless card: 0d:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) I did a bit more digging and pulled the source from git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy and did a diff between -23 and -25 and search for anything related to ath drivers, but I didn't see much there. The only thing I did find related to wifi is about iwlwifi. There had been changes made to that code, specifically this from -24: - iwlwifi: don't advertise TWT support I did figure out how to compile Ubuntu kernels from Git so I'll try playing with that but I'm not terribly good at it yet. Have to figure out how to not overwrite my current -23 kernel with the .deb it makes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Oh, you are right. I booted into the 5.15.0-23-generic kernel and the WiFi instability went away. I've been using it for a few hours now and I would have seen the issue by now. I checked the logs and the update to 5.15.0-25-generic was installed on 6 April, 2022 which correlates roughly when I started having issues. I suppose this means I filed this bug against the wrong package. Should I do something about that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1968391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Minor update: when the WiFi is being flaky, I often get see 100% CPU usage for ksoftirqd, but not always. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1968391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968391] [NEW] Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Public bug reported: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy wpasupplicant wpasupplicant: Geïnstalleerd: 2:2.10-6 Kandidaat: 2:2.10-6 Versietabel: *** 2:2.10-6 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 8 21:28:12 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-12 (27 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS To manage notifications about this bug go to: htt
[Bug 1964936] [NEW] Events on Nextcloud do not show up in calendar
Public bug reported: I set up KOrganizer to use my Nextcloud server for calendar (and contacts). Nextcloud is installed in a subdirectory of my domain (not sure if that matters, but sometimes it does). I can see the events in the Akonadi Console browser, but they do not show up in KOrganizer. In KOrganizer, the checkbox is checked, so it should display. Additionally, if I click on the eye icon to open just that calendar, I still don't see the events. I can accept calendar invites in KMail and they do show up in Nextcloud, so it seems to be specifically KOrganizer that is not showing anything. This is on Kubuntu Jammy 22.04 with the latest updates as of March 15. KOrganizer version: 4:21.12.3-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: korganizer 4:21.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Mar 15 07:32:43 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-12 (2 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) SourcePackage: korganizer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: korganizer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964936 Title: Events on Nextcloud do not show up in calendar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/korganizer/+bug/1964936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770742] Re: Cannot find -lGL
Oh, sorry. I'm really late to reply to this. Yeah, I do have the proprietary nVidia drivers installed. Those drivers came from the default Ubuntu repositories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770742 Title: Cannot find -lGL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1770742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770742] [NEW] Cannot find -lGL
Public bug reported:
I was trying to compile a OpenGL program, but it fails to compile. I
suppose the package this bug is in is really libglvnd-dev, but I could
not find that in Launchpad.
Anyway, the linking error is:
/usr/bin/x86_64-linux-gnu-ld: cannot find -lGL
collect2: error: ld returned 1 exit status
This seems to be because the symlink libGL.so is missing. If I go to
/usr/lib/x86_64-linux-gnu and type:
sudo ln -s libGL.so.1 libGL.so
then compiling works.
Here is a (nonsensical) test program:
#include
int main(int argc, char *argv[])
{
glEnable(GL_DEPTH_TEST);
return 0;
}
which I compile with:
gcc testgl.c -lGL
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1 1.0.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Fri May 11 15:48:17 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-04-29 (12 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: libglvnd
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: libglvnd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770742
Title:
Cannot find -lGL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1770742/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769461] Re: Crash on heaptrack analysis
Yes, sorry about that. I got confused due to the lack of a kdevelop-dbg package in Kubuntu 18.04. But I figured it out. See attached backtrace. ** Attachment added: "kdevelop-20180509-142408.kcrash.txt" https://bugs.launchpad.net/ubuntu/+source/kdevelop/+bug/1769461/+attachment/5136860/+files/kdevelop-20180509-142408.kcrash.txt -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdevelop in Ubuntu. https://bugs.launchpad.net/bugs/1769461 Title: Crash on heaptrack analysis To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdevelop/+bug/1769461/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1769461] [NEW] Crash on heaptrack analysis
Public bug reported: KDevelop crashes when selecting Run -> Run Heaptrack Analysis even though heaptrack and heaptrack-gui are installed. To reproduce: 1. Create new Terminal project with default template. 2. Compile code and observe that it works. 3. From the menu select Run -> Run Heaptrack Analysis 4. KDevelop crashes due to segmentation fault Output from running kdevelop from the terminal: QWidget::insertAction: Attempt to insert null action QWidget::insertAction: Attempt to insert null action KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kdevelop path = /usr/bin pid = 11158 KCrash: Arguments: /usr/bin/kdevelop KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 24 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... Unable to start Dr. Konqi Re-raising signal for core dump handling. [1]+ Segmentatiefout (geheugendump gemaakt) kdevelop ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kdevelop 4:5.2.1-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun May 6 10:09:24 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-29 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: kdevelop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kdevelop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769461 Title: Crash on heaptrack analysis To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdevelop/+bug/1769461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755812] [NEW] Next button not visible during install in VirtualBox
Public bug reported: I downloaded the Kubuntu 18.04-beta1 iso and did an install in VirtualBox 5.0.40_Ubuntu r115130. During the install the screen was too small to show the Next button. Resizing the virtualbox window had no effect. Workaround is to use the Tab button and guess when the Next button is selected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 14 09:26:20 2018 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity InstallationDate: Installed on 2018-03-14 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) JournalErrors: -- Logs begin at Wed 2018-03-14 09:17:25 EDT, end at Wed 2018-03-14 09:24:41 EDT. -- Mar 14 09:17:25 hostname kernel: piix4_smbus :00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr Mar 14 09:19:18 hostname spice-vdagent[1149]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Mar 14 09:19:36 hostname pulseaudio[1074]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755812 Title: Next button not visible during install in VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740687] [NEW] Dokuwiki 20160626.a is incompatible with php7.1
Public bug reported: I am using Ubuntu 17.10. Currently that comes with PHP7.1. However, DokuWiki only became compatible with PHP7.1 since version 2017-02-19e “Frusterick Manners”. Currently Ubuntu 17.10 only ships with Release 2016-06-26a “Elenor of Tsort”. Using the old version results in DokuWiki producing PHP Fatal Errors in the CSS.php part. Thus all pages are malformed. ** Affects: dokuwiki (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/1740687 Title: Dokuwiki 20160626.a is incompatible with php7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dokuwiki/+bug/1740687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573277] [NEW] Fresh install of Kubuntu 16.04 breaks when using Dutch language
Public bug reported: The kde-l10n-nl package conflicts with plasma-desktop and plasma-desktop-data. Unfortunately, on a fresh install of Kubuntu 16.04 from the iso, this package is automatically installed and thus plasma-desktop and plasma-desktop-data are uninstalled. This results in an error after logging in for the first time, saying that the necessary packages are missing. Weirdly enough, packages such as kde-l10n-de do not have this problem. So to reproduce (in Virtualbox): 1. Create new virtual machine 2. Install Kubuntu 16.04 from ISO 3. Choose "Nederlands" (Dutch) as the language. 4. Finish installation and restart. 5. Log in for the first time and observe the error. Workaround is to use Alt+F2 to open krunner, and start a terminal session from there. Then install plasma-desktop and plasma-desktop-data again with apt and reboot. Now everything works fine again. Additional info: jarno@kubuntu1604:~$ LANG=en apt-cache policy kde-l10n-nl plasma-desktop plasma-desktop-data kde-l10n-nl: Installed: (none) Candidate: 4:15.08.2-0ubuntu1 Version table: 4:15.08.2-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe i386 Packages plasma-desktop: Installed: 4:5.5.5-0ubuntu1 Candidate: 4:5.5.5-0ubuntu1 Version table: *** 4:5.5.5-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status plasma-desktop-data: Installed: 4:5.5.5-0ubuntu1 Candidate: 4:5.5.5-0ubuntu1 Version table: *** 4:5.5.5-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 21 18:14:15 2016 InstallationDate: Installed on 2016-04-21 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu performance xenial ** Description changed: The kde-l10n-nl package conflicts with plasma-desktop and plasma-desktop-data. Unfortunately, on a fresh install of Kubuntu 16.04 from the iso, this package is automatically installed and thus plasma-desktop and plasma-desktop-data are uninstalled. This results in an error after logging in for the first time, saying that the necessary packages are missing. Weirdly enough, packages such as kde-l10n-de do not have this problem. So to reproduce (in Virtualbox): 1. Create new virtual machine 2. Install Kubuntu 16.04 from ISO 3. Choose "Nederlands" (Dutch) as the language. 4. Finish installation and restart. 5. Log in for the first time and observe the error. Workaround is to use Alt+F2 to open krunner, and start a terminal - session from there. The install plasma-desktop and plasma-desktop-data + session from there. Then install plasma-desktop and plasma-desktop-data again with apt and reboot. Now everything works fine again. Additional info: - jarno@kubuntu1604:~$ LANG=en apt-cache policy kde-l10n-nl plasma-desktop plasma-desktop-data + jarno@kubuntu1604:~$ LANG=en apt-cache policy kde-l10n-nl plasma-desktop plasma-desktop-data kde-l10n-nl: - Installed: (none) - Candidate: 4:15.08.2-0ubuntu1 - Version table: - 4:15.08.2-0ubuntu1 500 - 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages - 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe i386 Packages + Installed: (none) + Candidate: 4:15.08.2-0ubuntu1 + Version table: + 4:15.08.2-0ubuntu1 500 + 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages + 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe i386 Packages plasma-desktop: - Installed: 4:5.5.5-0ubuntu1 - Candidate: 4:5.5.5-0ubuntu1 - Version table: - *** 4:5.5.5-0ubuntu1 500 - 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 4:5.5.5-0ubuntu1 + Candidate: 4:5.5.5-0ubuntu1 + Version table: + *** 4:5.5.5-0ubuntu1 500 + 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages + 100 /var/lib/dpkg/status plasma-desktop-data: - Installed: 4:5.5.5-0ubuntu1 - Candidate: 4:5.5.5-0ubuntu1 - Version table: - *** 4:5.5.5-0ubuntu1 500 - 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages - 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe i386 Packages - 100 /var/lib/dp
