[Bug 1849891] Re: Can not establish WIFI connection with Intel Wireless 7265 [8086:095a] subsystem id [8086:5110] after upgrade to Ubuntu 19.10

2019-11-05 Thread Markus Straub
Update: In my case WIFI works again after disabling 802.11n. I added the
option 11n_disable=1 to /etc/modprobe.d/iwlwifi.conf - now it looks like
this:

# /etc/modprobe.d/iwlwifi.conf
# iwlwifi will dyamically load either iwldvm or iwlmvm depending on the
# microcode file installed on the system.  When removing iwlwifi, first
# remove the iwl?vm module and then iwlwifi.
remove iwlwifi \
(/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \
&& /sbin/modprobe -r mac8021
options iwlwifi 11n_disable=1

See also
https://wiki.archlinux.org/index.php/Network_configuration/Wireless#iwlwifi
(the iwlwifi parameters apply to Ubuntu too and Arch has great
documentation )

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849891

Title:
  Can not establish WIFI connection with Intel Wireless 7265 [8086:095a]
  subsystem id [8086:5110] after upgrade to Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1849891/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849891] Re: Can not establish WIFI connection with Intel Wireless 7265 [8086:095a] subsystem id [8086:5110] after upgrade to Ubuntu 19.10

2019-11-01 Thread Markus Straub
Thank you for your suggestions, You-Sheng Yang.

Which kernel/firmware version worked?
-> the default Ubuntu 19.04 kernel and firmware. I never installed a kernel or 
firmware from external sources and all minor updates that were available worked 
just fine. What also worked: all other versions of Ubuntu I used on my laptop, 
at least 18.04 and 18.10 too, most probably I also used 16.04 (not sure).

Which kernel/firmware does not work?
-> The versions at the release of Ubuntu 19.10 (on the .iso images) and also 
the latest update (5.3.0-19-generic).

An important detail could be, that when I boot Ubuntu 19.10 with the old
kernel still installed from 19.04 the same behavior can be seen.

$ uname -a
Linux whakaari 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

$ dmesg | grep "iwlwifi\|wlp3s0"
[4.442485] iwlwifi :03:00.0: Found debug destination: EXTERNAL_DRAM
[4.442487] iwlwifi :03:00.0: Found debug configuration: 0
[4.442790] iwlwifi :03:00.0: loaded firmware version 29.1654887522.0 
op_mode iwlmvm
[4.495202] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 
7265, REV=0x210
[4.509093] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
[4.509828] iwlwifi :03:00.0: Allocated 0x0040 bytes for firmware 
monitor.
[4.520392] iwlwifi :03:00.0: base HW address: 5c:e0:c5:63:e2:a5
[4.838622] iwlwifi :03:00.0 wlp3s0: renamed from wlan0
[6.741168] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
[6.826404] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
[6.829668] iwlwifi :03:00.0: FW already configured (0) - re-configuring
[   65.133013] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[   65.139402] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[   65.159113] wlp3s0: authenticated
[   65.166457] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[   65.274544] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[   65.378575] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[   65.482488] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out
[   66.523712] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[   66.530411] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[   66.634538] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 2/3)
[   66.644178] wlp3s0: authenticated
[   66.646503] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[   66.750461] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[   66.854575] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[   66.958583] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out
[   68.401500] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[   68.406079] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[   68.510545] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 2/3)
[   68.520607] wlp3s0: authenticated
[   68.522474] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[   68.626486] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[   68.730468] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[   68.834507] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out
[   72.949579] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[   72.954141] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[   72.965169] wlp3s0: authenticated
[   72.966514] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[   73.070456] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[   73.174478] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[   73.278529] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out
[   83.224244] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[   83.229198] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[   83.240334] wlp3s0: authenticated
[   83.242503] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[   83.346574] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[   83.450513] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[   83.554484] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849891

Title:
  Can not establish WIFI connection with Intel Wireless 7265 [8086:095a]
  subsystem id [8086:5110] after upgrade to Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1849891/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849891] Re: Can not establish WIFI connection with Intel Wireless 7265 [8086:095a] subsystem id [8086:5110] after upgrade to Ubuntu 19.10

2019-11-01 Thread Markus Straub
Results from your third suggestion (unfortunately no success):

$ sudo add-apt-repository ppa:canonical-hwe-team/backport-iwlwifi
$ sudo apt install backport-iwlwifi-dkms

Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  backport-iwlwifi-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1.551 kB of archives.
After this operation, 9.942 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/canonical-hwe-team/backport-iwlwifi/ubuntu 
eoan/main amd64 backport-iwlwifi-dkms all 8042-0ubuntu1 [1.551 kB]
Fetched 1.551 kB in 2s (849 kB/s)  
Selecting previously unselected package backport-iwlwifi-dkms.
(Reading database ... 320149 files and directories currently installed.)
Preparing to unpack .../backport-iwlwifi-dkms_8042-0ubuntu1_all.deb ...
Unpacking backport-iwlwifi-dkms (8042-0ubuntu1) ...
Setting up backport-iwlwifi-dkms (8042-0ubuntu1) ...
Loading new backport-iwlwifi-8042 DKMS files...
Building for 5.3.0-19-generic
Building initial module for 5.3.0-19-generic
Done.

compat.ko:
Running module version sanity check.
modinfo: ERROR: missing module or filename.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

iwlwifi.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

iwlxvt.ko:
Running module version sanity check.
modinfo: ERROR: missing module or filename.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

iwlmvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

mac80211.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

cfg80211.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

depmod...

DKMS: install completed.


$ uname -a
Linux whakaari 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

Then I rebooted and tried to connect to the WIFI

$ dmesg | grep "iwlwifi\|wlp3s0"
[4.247626] Loading modules backported from iwlwifi
[4.247627] iwlwifi-stack-public:master:8042:654c426c
[4.362032] iwlwifi :03:00.0: Direct firmware load for iwl-dbg-cfg.ini 
failed with error -2
[4.367098] iwlwifi :03:00.0: Found debug destination: EXTERNAL_DRAM
[4.367108] iwlwifi :03:00.0: Found debug configuration: 0
[4.367369] iwlwifi :03:00.0: loaded firmware version 29.62a39462.0 
op_mode iwlmvm
[4.389809] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 
7265, REV=0x210
[4.403033] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
[4.403770] iwlwifi :03:00.0: Allocated 0x0040 bytes for firmware 
monitor.
[4.412431] iwlwifi :03:00.0: base HW address: 5c:e0:c5:63:e2:a5
[4.778388] iwlwifi :03:00.0 wlp3s0: renamed from wlan0
[6.808565] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
[6.886587] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
[6.889305] iwlwifi :03:00.0: FW already configured (0) - re-configuring
[   52.385983] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[   52.391168] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[   52.507214] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 2/3)
[   52.612962] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 3/3)
[   52.622972] wlp3s0: authenticated
[   52.627184] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[   52.731156] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[   52.835165] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[   52.939161] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out
[   53.982692] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[   53.987699] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[   54.091208] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 2/3)
[   54.101544] wlp3s0: authenticated
[   54.103138] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[   54.207274] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[   54.311270] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[   54.415246] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out
[   55.861407] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[   55.866987] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[   55.975216] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 2/3)
[   55.986647] wlp3s0: 

[Bug 1849891] [NEW] Can not establish WIFI connection with Intel Wireless 7265 after upgrade to Ubuntu 19.10

2019-10-25 Thread Markus Straub
Public bug reported:

- WIFI is active, and I can see available networks, e.g. with iwlist wlp3s0 scan
- However, connecting to a network (with the GUI) fails: after entering 
credentials (for a password protrected WPA2 network) it tries to connect for a 
few seconds but then asks for a passphrase again .. and again ..
- Also the problem is not the GUI, the exact same behavior is shown by nmtui

Checking the output of NetworkManager in /var/log/syslog we can see that
the association is the one that fails:

sudo cat /var/log/syslog  | grep "(wlp3s0)" | sed 's/.*device //'

device (wlp3s0): Activation: starting connection 'MY_WIFI' 
(c5c790fb-86a8-4905-97b0-75170f5e985c)
device (wlp3s0): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) access point 'MY_WIFI' has security, but 
secrets are required.
device (wlp3s0): state change: config -> need-auth (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): state change: need-auth -> prepare (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) connection 'MY_WIFI' has security, and 
secrets exist.  No new secrets needed.
device (wlp3s0): supplicant interface state: ready -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): Activation: (wifi) association took too long
device (wlp3s0): state change: config -> need-auth (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) asking for new secrets
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): no secrets: User canceled the secrets request.
device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets', 
sys-iface-state: 'managed')
device (wlp3s0): Activation: failed for connection 'MY_WIFI'
device (wlp3s0): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')

This is what the log looked like before the update with Ubuntu MATE
19.04

device (wlp3s0): Activation: starting connection 'MY_WLAN' 
(b3dffdda-2b7b-467d-a1f5-2b3077d26eb3)
device (wlp3s0): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) access point 'MY_WLAN' has security, but 
secrets are required.
device (wlp3s0): state change: config -> need-auth (reason 'none', 
sys-iface-state: 'managed') 
device (wlp3s0): state change: need-auth -> prepare (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) connection 'MY_WLAN' has security, and 
secrets exist.  No new secrets needed. 
device (wlp3s0): supplicant interface state: ready -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> associated
device (wlp3s0): supplicant interface state: associated -> 4-way handshake
device (wlp3s0): supplicant interface state: 4-way handshake -> completed
device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. 
Connected to wireless network "MY_WLAN"
device (wlp3s0): state change: config -> ip-config (reason 'none', 
sys-iface-state: 'managed') 
dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
dhcp4 (wlp3s0): dhclient started with 

[Bug 1499530] Re: Dolphin context menu is missing "Compress"/"Extract" entries

2015-11-02 Thread Markus Straub
As posted on http://www.linuxgnut.com/dolphin-extract-menus-missing-in-
kubuntu-1510 this is a practical fix for the problem:

sudo ln -s /usr/share/kde4/servicetypes/konqpopupmenuplugin.desktop
/usr/share/kservicetypes5/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499530

Title:
  Dolphin context menu is missing "Compress"/"Extract" entries

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1499530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 174532] Re: Desktop displays root directory (/) after upgrade from Gutsy to Hardy

2008-03-13 Thread Markus Straub
Daniel, I can't exactly remember the contents of ~/.config/user-
dirs.dirs, but I tried to correct the information there and it had no
influence. xdg-user-dirs was not installed by default. it rewrote user-
dirs.dirs to this:

XDG_DESKTOP_DIR=$HOME/Desktop
XDG_DOWNLOAD_DIR=$HOME/Desktop
XDG_TEMPLATES_DIR=$HOME/Templates
XDG_PUBLICSHARE_DIR=$HOME/Public
XDG_DOCUMENTS_DIR=$HOME/Documents
XDG_MUSIC_DIR=$HOME/Music
XDG_PICTURES_DIR=$HOME/Pictures
XDG_VIDEOS_DIR=$HOME/Videos

Maybe the tool also changes data in other places?

-- 
Desktop displays root directory (/) after upgrade from Gutsy to Hardy
https://bugs.launchpad.net/bugs/174532
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kubuntu-default-settings in ubuntu.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 174532] Re: Desktop displays root directory (/) after upgrade from Gutsy to Hardy

2008-02-28 Thread Markus Straub
The same thing happened to me after I upgraded KDE to 3.5.9 while still using 
Kubuntu 7.10
(deb http://ppa.launchpad.net/kubuntu-kde-3.5.9/ubuntu gutsy main)

The above solution doesn't seem to work for me though:
If I use System Settings  About Me  Paths to update the path, it is written 
into ~/.config/user-dirs.dirs correctly. After restarting KDE the path is still 
present in user-dirs.dirs, but kde-config --userpath desktop reveals that my 
Desktop still points to /. Also of course my Desktop shows me icons for my 
root-directory.

My next approach, namely to put the line Desktop=$HOME/Desktop into
the [Paths]-section of ~/.kde/share/config/kdeglobals doesn't solve the
problem either.

-- 
Desktop displays root directory (/) after upgrade from Gutsy to Hardy
https://bugs.launchpad.net/bugs/174532
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kubuntu-default-settings in ubuntu.

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 174532] Re: Desktop displays root directory (/) after upgrade from Gutsy to Hardy

2008-02-28 Thread Markus Straub
Further research finally led to a solution:
(found on: http://ubuntuforums.org/showthread.php?t=609005page=2)

I deleted the XDG_DESKTOP_DIR-line from ~/.config/user-dirs.dirs,
installed xdg-user-dirs, ran xdg-user-dirs-update, logged out and in
again and everything was nice and dandy - again. My Desktop is no longer
/ but ~/Desktop.

-- 
Desktop displays root directory (/) after upgrade from Gutsy to Hardy
https://bugs.launchpad.net/bugs/174532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs