Question mark within the Wi-Fi icon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Question mark within the Wi-Fi icon after connecting to the internet.
It should be noted that there is no problem with connecting to the Internet, and I have full Internet access and there is only a question mark within the Wi-Fi icon.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSign
Uname: Linux 5.0.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperVersion: 1.403
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 14 10:48:29 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:194d]
Subsystem: ASUSTeK Computer Inc. GK208BM [GeForce 920M] [1043:232a]
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
MachineType: ASUSTeK COMPUTER INC. TP300LJ
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=C.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: TP300LJ.206
dmi.board.
dmi.board.name: TP300LJ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: TP
dmi.product.name: TP300LJ
dmi.product.sku: ASUS-NotebookSKU
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
The problem with the battery icon was possibly bug 1823175 (now fixed).