[Desktop-packages] [Bug 1827958] Re: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system
Any solution for that bug ? I'm on Manjaro and I've this bug too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1827958 Title: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system Status in alsa-driver package in Ubuntu: New Bug description: The inbuilt microphone has never worked on the version of ubuntu on this computer. The hardware works completely fine on other operating systems (Windows). Distribution: Ubuntu 18.04.2 LTS alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:54:58 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 0 3 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1273 F pulseaudio lune 1908 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860243] Re: wifi not detected. nm-applet error when trying to run
In terminal sudo apt update && sudo apt install firmware-b43-installer Reboot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1860243 Title: wifi not detected. nm-applet error when trying to run Status in network-manager-applet package in Ubuntu: New Bug description: There is a problem with this kernel I have reported this problem to Debian as well. The kernel is not able to load the firmware for the wifi hardware so the network managers are not detecting wifi at all. I tryed to run the nm-applet and got the following error: (nm-applet:30837): Gtk-WARNING **: 18:26:47.538: Can't set a parent on widget which has a parent The correct firmware files for my system are installed and in the correct place.When I run a dmesg command it gives the following error: 9.453407] b43-phy0: Broadcom 4312 WLAN found (core revision 15) [9.496761] b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1 [9.496777] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2062, Revision 2, Version 0 [9.512936] b43 ssb0:0: Direct firmware load for b43/ucode15.fw failed with error -2 [9.512976] b43 ssb0:0: Direct firmware load for b43/ucode15.fw failed with error -2 [9.513063] b43 ssb0:0: Direct firmware load for b43-open/ucode15.fw failed with error -2 [9.513100] b43 ssb0:0: Direct firmware load for b43-open/ucode15.fw failed with error -2 [9.513104] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found [9.513108] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found [9.513111] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website. [9.513200] Broadcom 43xx driver loaded [ Features: PNL ] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager-gnome 1.8.22-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Jan 18 18:43:15 2020 InstallationDate: Installed on 2020-01-18 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) IpRoute: default via 192.168.1.1 dev enp9s0 proto dhcp metric 100 192.168.1.0/24 dev enp9s0 proto kernel scope link src 192.168.1.16 metric 100 IwConfig: enp9s0no wireless extensions. lono wireless extensions. RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 2951c15c-9995-3f31-915c-79716865ac23 ethernet 1579390965 Sat 18 Jan 2020 06:42:45 PM EST yes -999 no/org/freedesktop/NetworkManager/Settings/1 yes enp9s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp9s0 ethernet connected full full /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 2951c15c-9995-3f31-915c-79716865ac23 /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1860243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960817] Re: Network Manager sets powersave on by default, thus making many WiFi connections unreliable
Please revert https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1557026 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1960817 Title: Network Manager sets powersave on by default, thus making many WiFi connections unreliable Status in network-manager package in Ubuntu: Confirmed Bug description: As the headline says. On the support fora that I frequent, many people report unstable and unreliable WiFi connections because of this. In those cases, when power management for the WiFi chipset is turned off, the connection immediately improves a lot. Therefore the default for WiFi power management should be "off", non "on". Workaround for those who don't want to wait for the fix: sudo sed -i 's/3/2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf Reboot. When there's no such .conf file yet: sudo touch /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf echo "[connection]" | sudo tee /etc/NetworkManager/conf.d/default- wifi-powersave-off.conf echo "wifi.powersave = 2" | sudo tee -a /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf Reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1960817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960817] Re: Network Manager sets powersave on by default, thus making many WiFi connections unreliable
The actual git commit is https://git.launchpad.net/network- manager/commit/?id=b07d891427e6698838feb42e03ac668893125775 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1960817 Title: Network Manager sets powersave on by default, thus making many WiFi connections unreliable Status in network-manager package in Ubuntu: Confirmed Bug description: As the headline says. On the support fora that I frequent, many people report unstable and unreliable WiFi connections because of this. In those cases, when power management for the WiFi chipset is turned off, the connection immediately improves a lot. Therefore the default for WiFi power management should be "off", non "on". Workaround for those who don't want to wait for the fix: sudo sed -i 's/3/2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf Reboot. When there's no such .conf file yet: sudo touch /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf echo "[connection]" | sudo tee /etc/NetworkManager/conf.d/default- wifi-powersave-off.conf echo "wifi.powersave = 2" | sudo tee -a /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf Reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1960817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
What is the result from terminal for cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval wpa_su
[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
Chelmite, change it to 2 and see if it works better sudo sed -i 's/3/2/' /etc/NetworkManager/conf.d/* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval wp
[Desktop-packages] [Bug 1915491] Re: Wifi adapter installed but can't be found in Settings
What results do you get from this command in terminal before and after the issue iwconfig -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1915491 Title: Wifi adapter installed but can't be found in Settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: # Summary: > ## Wifi Adpter Not found ## Steps to Reproduce: - I don't know ## Expected Results: Wifi should always be available ## Problem Description: Sometimes when startup my pc there is no wifi icon on the top right corner menu. When checking the wifi settings on the settings window it shows that the wifi adapter not found. But after restarting the pc, everything back to normal again. This is happening too frequently now. * * * Screenshot: https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 11:13:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E7470 [1028:06dc] InstallationDate: Installed on 2021-01-06 (36 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E7470 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 047I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915491] Re: Wifi adapter installed but can't be found in Settings
Power management might be crashing the driver, in terminal sudo sed -i 's/3/2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf systemctl restart network-manager.service See if it happens again -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1915491 Title: Wifi adapter installed but can't be found in Settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: # Summary: > ## Wifi Adpter Not found ## Steps to Reproduce: - I don't know ## Expected Results: Wifi should always be available ## Problem Description: Sometimes when startup my pc there is no wifi icon on the top right corner menu. When checking the wifi settings on the settings window it shows that the wifi adapter not found. But after restarting the pc, everything back to normal again. This is happening too frequently now. * * * Screenshot: https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 11:13:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E7470 [1028:06dc] InstallationDate: Installed on 2021-01-06 (36 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E7470 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 047I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1940543] Re: Show Hidden Files does not persist and even resets during the same session
Thanks for clearing that up Paul. I will provide whatever data I can once someone can check on this ticket. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1940543 Title: Show Hidden Files does not persist and even resets during the same session Status in nautilus package in Ubuntu: New Bug description: Since 20.04 has been released, the option "Show Hidden Files" has never lasted long. It never persists over a reboot and even during the same session, it will just hide the files after some random (it seems random) interval. This happens for me on 3 different computers, all different builds. This happens on a vanilla install too. I have never been able to make "Show Hidden Files" last longer than an hourish, and never over a reboot. I work a lot in hidden files, this is mostly just frustrating to me since it happens randomly and when I am moving around a project, I have to keep toggling "Show Hidden Files" to get work done. I did have to reinstall `gnome-control-center` after a fresh install and updating Ubuntu 20.04 the latest version, I am not sure if that could help identify the issue but I have always had this issue on 20.04 so I am doubtful. I did this running: ``` sudo apt install --reinstall gnome-control-center ``` I had to reinstall this since Settings was no longer available after the system was updated (fresh install with `sudo apt update && sudo apt upgrade` is what broken it for me to have to reinstall it. I even tried using: ``` gsettings set org.gtk.Settings.FileChooser show-hidden true ``` but the issue still happens. Also, not sure why nautilus is installed, I thought 20.04 was gnome? Again, this is a fresh install (15 days old) ``` $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` ``` $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ``` ``` apt-cache policy gnome gnome: Installed: (none) Candidate: 1:3.30+2 Version table: 1:3.30+2 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:46:31 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1280, 1393)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-08-03 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1940543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575179] Re: Wifi not detected on Pavilion X360 fresh install
For some reason the acer_wmi module loads and causes the wireless to be blocked on HP computers Blacklisting the acer_wmi module and rebooting should fix the issue echo "blacklist acer_wmi" | sudo tee /etc/modprobe.d/blacklist.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-nettool in Ubuntu. https://bugs.launchpad.net/bugs/1575179 Title: Wifi not detected on Pavilion X360 fresh install Status in gnome-nettool package in Ubuntu: New Bug description: I did a fresh install on a HP Pavilion X300 model11-k001ns The main problem is that I can connect to the Wifi, it appears as disabled in the Network Manager and when I enable it, it doesn't show any SSID I think it detects two wireless devices ~$ lsmod |grep _wmi hp_wmi16384 0 acer_wmi 20480 0~$ sparse_keymap 16384 2 acer_wmi,hp_wmi wmi 20480 2 acer_wmi,hp_wmi video40960 2 i915,acer_wmi ~$ uname -a Linux ubuntuHP 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ~$ sudo rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: acer-wireless: Wireless LAN Soft blocked: yes Hard blocked: no ~$ sudo rfkill unblock wifi ~$ sudo rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: acer-wireless: Wireless LAN Soft blocked: yes Hard blocked: no ~$ lspci -nnk | grep 0280 -A2 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c] Kernel driver in use: rtl8723be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/1575179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576215] Re: Network Manager regularly thinks my wifi is a wired device
It seems two similar bugs have been reported to gnome https://bugzilla.gnome.org/show_bug.cgi?id=765839 https://bugzilla.gnome.org/show_bug.cgi?id=764803 And the fix seems to be http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd4d8b24da29abfc786ce0b3030c74559b93d034 ** Bug watch added: GNOME Bug Tracker #765839 https://bugzilla.gnome.org/show_bug.cgi?id=765839 ** Bug watch added: GNOME Bug Tracker #764803 https://bugzilla.gnome.org/show_bug.cgi?id=764803 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576215 Title: Network Manager regularly thinks my wifi is a wired device Status in network-manager package in Ubuntu: New Bug description: When I boot up my network doesn't automatically connect. I instead see when I click the network manager applet that it's got no Wifi devices listed. It thinks my wireless card is an ethernet device. This isn't true and I have no ethernet devices in my system. When this situation happens if I issue /etc/init.d/network-manager restart it comes back up thinking it's a wireless device and happily associates with my saved SSID. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 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: Unity Date: Thu Apr 28 09:03:13 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160406-0 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-13 (14 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160406-07:32 IpRoute: NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp58s0 ethernet connecting (getting IP configuration) /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 1c8c4cab-09d7-4a42-bfc4-aed14caf6a46 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458933] [NEW] No volume control on screen lock - Volume goes to 100%
Public bug reported: Xubuntu 14.04.2, LightDM, Macbook 4,1, using ubuntu-stable using $ dm-tool lock, the keyboard volume controls do not work until I have logged in. I expect it to at least maintain the volume level it was at, and respond to being muted, but it does none of these things. This is a problem because if I forget to turn off music, then take my laptop somewhere, I have to login before I can mute the massive blast of music coming out of my speakers. On the lock screen, even if the volume was previously muted, it gets put to 100%. Searching google and posting this problem on /r/linux4noobs, /r/linuxquestions, and /r/archlinux have yielded no answers. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1458933 Title: No volume control on screen lock - Volume goes to 100% Status in lightdm package in Ubuntu: New Bug description: Xubuntu 14.04.2, LightDM, Macbook 4,1, using ubuntu-stable using $ dm-tool lock, the keyboard volume controls do not work until I have logged in. I expect it to at least maintain the volume level it was at, and respond to being muted, but it does none of these things. This is a problem because if I forget to turn off music, then take my laptop somewhere, I have to login before I can mute the massive blast of music coming out of my speakers. On the lock screen, even if the volume was previously muted, it gets put to 100%. Searching google and posting this problem on /r/linux4noobs, /r/linuxquestions, and /r/archlinux have yielded no answers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1458933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575179] Re: Wifi not detected on Pavilion X360 fresh install
Nemo_bis I don't think it is a duplicate of either of those bugs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-nettool in Ubuntu. https://bugs.launchpad.net/bugs/1575179 Title: Wifi not detected on Pavilion X360 fresh install Status in gnome-nettool package in Ubuntu: New Bug description: I did a fresh install on a HP Pavilion X300 model11-k001ns The main problem is that I can connect to the Wifi, it appears as disabled in the Network Manager and when I enable it, it doesn't show any SSID I think it detects two wireless devices ~$ lsmod |grep _wmi hp_wmi16384 0 acer_wmi 20480 0~$ sparse_keymap 16384 2 acer_wmi,hp_wmi wmi 20480 2 acer_wmi,hp_wmi video40960 2 i915,acer_wmi ~$ uname -a Linux ubuntuHP 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ~$ sudo rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: acer-wireless: Wireless LAN Soft blocked: yes Hard blocked: no ~$ sudo rfkill unblock wifi ~$ sudo rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: acer-wireless: Wireless LAN Soft blocked: yes Hard blocked: no ~$ lspci -nnk | grep 0280 -A2 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c] Kernel driver in use: rtl8723be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/1575179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1396361] Re: Double Mouse Cursor
*** This bug is a duplicate of bug 1390625 *** https://bugs.launchpad.net/bugs/1390625 This bug still persists. I am on Lubuntu 3.16.0-62-generic #83~14.04.1-Ubuntu x86_64 x86_64 x86_64 GNU/Linux. Dragging icon from Firefox 45.0 causes mouse pointer duplication and more. Please see attached picture. Has any progress been made on this bug. Thanks for your assistance in advance. ** Attachment added: "IMG_20160315_110814983.jpg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4600046/+files/IMG_20160315_110814983.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1396361 Title: Double Mouse Cursor Status in xorg package in Ubuntu: Incomplete Bug description: When dragging with the mouse cursor often it creates a double cursor side by side about 10 cm apart on the screen. Only one cursor works. Using print screen does not show the cursor in the resulting image. Rebooting corrects the problem. This is similar to the double mouse cursor reported as a result of flash in a browser, however the current problem will occur without the browser open. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE Date: Tue Nov 25 15:58:51 2014 InstallationDate: Installed on 2014-10-24 (32 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480358] [NEW] There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible.
Public bug reported: There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible. Kubuntu 15.10 x64 Alpha 2 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Description changed: There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible. + + Kubuntu 15.10 x64 Alpha 2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1480358 Title: There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible. Status in libreoffice package in Ubuntu: New Bug description: There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible. Kubuntu 15.10 x64 Alpha 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1480358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480358] Re: LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible.
** Summary changed: - There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible. + LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1480358 Title: LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible. Status in libreoffice package in Ubuntu: New Bug description: There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible. Kubuntu 15.10 x64 Alpha 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1480358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480358] Re: LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible and the Check Box are weird (screenshots)
** Summary changed: - LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible. + LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible and the Check Box are weird (screenshots) ** Attachment added: "LibreOffice-KDE GUI - Hover.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1480358/+attachment/4438439/+files/LibreOffice-KDE%20GUI%20-%20Hover.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1480358 Title: LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible and the Check Box are weird (screenshots) Status in libreoffice package in Ubuntu: New Bug description: There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible. Kubuntu 15.10 x64 Alpha 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1480358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480358] Re: LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible and the Check Box are weird (screenshots)
** Attachment added: "LibreOffice-KDE GUI - Box.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1480358/+attachment/4438440/+files/LibreOffice-KDE%20GUI%20-%20Box.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1480358 Title: LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible and the Check Box are weird (screenshots) Status in libreoffice package in Ubuntu: New Bug description: There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible. Kubuntu 15.10 x64 Alpha 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1480358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480358] Re: LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible and the Check Box are weird (screenshots)
** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1480358 Title: LibreOffice-KDE GUI: When you mouse hover in menu there is no hovering visible and the Check Box are weird (screenshots) Status in libreoffice package in Ubuntu: Confirmed Bug description: There is a bug on LibreOffice-KDE GUI. When you mouse hover in menu there is no hovering visible. Kubuntu 15.10 x64 Alpha 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1480358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1562822] Re: Bluetooth Browse Files... not working
You are likely missing a couple packages sudo apt-get install obexfs obexftp Then connect to the device and see if send files works To receive files over bluetooth you will need to enable the option in Personal File Sharing, search dash for the program -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1562822 Title: Bluetooth Browse Files... not working Status in unity-control-center package in Ubuntu: New Bug description: Mobile phone: LG L40 Android 4.4.2 1. Connecting to Phone is successful shown. 2. Click on Button "Browse Files... " nothing happen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 28 13:31:39 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-02-04 (52 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1562822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569638] [NEW] Terminal hieght shrinking when it losses focus
Public bug reported: When losing focus, a tabbed terminal will shrink by one line. A normal (non-tabbed) terminal doesn't have this issue. Video demonstarting this behavior: https://gfycat.com/DearestWealthyBordercollie ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1569638 Title: Terminal hieght shrinking when it losses focus Status in gnome-terminal package in Ubuntu: New Bug description: When losing focus, a tabbed terminal will shrink by one line. A normal (non-tabbed) terminal doesn't have this issue. Video demonstarting this behavior: https://gfycat.com/DearestWealthyBordercollie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1569638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451276] Re: No mouse over highlight in libreoffice menus in Kubuntu 15.04
That need to be fixed for Kubuntu 16.04 or simply ship libreoffice-gtk instead... ** Tags removed: vivid ** Tags added: xenial ** Summary changed: - No mouse over highlight in libreoffice menus in Kubuntu 15.04 + No mouse over highlight in libreoffice menus in Kubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1451276 Title: No mouse over highlight in libreoffice menus in Kubuntu Status in libreoffice package in Ubuntu: Triaged Bug description: No mouse over highlight in libreoffice menus in Kubuntu 15.04. Check boxes are broken/glitchy too. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libreoffice-kde 1:4.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 4 01:45:45 2015 InstallationDate: Installed on 2015-05-03 (0 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1451276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451276] Re: No mouse over highlight in libreoffice menus in Kubuntu
** Tags added: wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1451276 Title: No mouse over highlight in libreoffice menus in Kubuntu Status in libreoffice package in Ubuntu: Triaged Bug description: No mouse over highlight in libreoffice menus in Kubuntu 15.04. Check boxes are broken/glitchy too. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libreoffice-kde 1:4.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 4 01:45:45 2015 InstallationDate: Installed on 2015-05-03 (0 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1451276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451276] Re: No mouse over highlight in libreoffice menus in Kubuntu
** Tags added: kubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1451276 Title: No mouse over highlight in libreoffice menus in Kubuntu Status in libreoffice package in Ubuntu: Triaged Bug description: No mouse over highlight in libreoffice menus in Kubuntu 15.04. Check boxes are broken/glitchy too. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libreoffice-kde 1:4.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 4 01:45:45 2015 InstallationDate: Installed on 2015-05-03 (0 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1451276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451276] Re: No mouse over highlight in libreoffice menus in Kubuntu 15.04
That need to be fixed for Kubuntu 15.10 or simply ship libreoffice-gtk instead -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1451276 Title: No mouse over highlight in libreoffice menus in Kubuntu 15.04 Status in libreoffice package in Ubuntu: Triaged Bug description: No mouse over highlight in libreoffice menus in Kubuntu 15.04. Check boxes are broken/glitchy too. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libreoffice-kde 1:4.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 4 01:45:45 2015 InstallationDate: Installed on 2015-05-03 (0 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1451276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1557026] Re: [SRU]Network Manager sets powersave off by default in xenial
>From results on the forums I visit, this creates more issues than it solves -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1557026 Title: [SRU]Network Manager sets powersave off by default in xenial Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Status in network-manager source package in Yakkety: Fix Released Bug description: [Impact] NetworkManager consumes more power than previous releases because powersave support is not updated. [Test Case] With the patch applied, network device power management should be on when supported, for example: $ sudo iwconfig wlan0 | grep "Power Management" Power Management:on [Regression Potential] Regression may happen when the power management feature of certain device isn't implemented properly in kernel, but since we are quite conservative on enabling power management in kernel development such case should be rare. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1557026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Luke and Joakim, thanks for your effort in this bug. With Luke's latest PPA, things still don't work unless I use a terminal command I found on askubuntu pacmd set-card-profile `pacmd list-cards | grep bluez_card -B1 | grep index | awk '{print $2}'` off; sleep 2 ; echo -e "disconnect xx:xx:xx:xx:xx:xx\n quit"|bluetoothctl;sleep 5; echo -e "connect xx:xx:xx:xx:xx:xx\n quit"|bluetoothctl; sleep 5; pacmd set-card-profile `pacmd list-cards | grep bluez_card -B1 | grep index | awk '{print $2}'` a2dp_sink Where xx:xx:xx:xx:xx:xx is the MAC address of my headphones -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Luke, I haven't had a pulseaudio crash and I have been able to connect to 2 different headsets since installing 16.04 however getting A2DP to work by switching it in sound settings is usually impossible. Both headsets have volume controls and microphones. A little bluetooth speaker without microphone or volume controls uses A2DP without issues The behavior I see is similar to your comment #18 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670031] Re: Wireless driver (QCA-9377) not working properly
Open a terminal and enter sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf as one line, then reboot and see if your wifi is improved -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1670031 Title: Wireless driver (QCA-9377) not working properly Status in network-manager package in Ubuntu: New Bug description: Hello guys, I have Lenovo Ideapad 500S-13ISK. It is bundled with Qualcomm Atheros QCA-9377 (rev 30) 802.11ac wireless card. Currently I have running Ubuntu 16.10 with all security updates. Wireless is dropping constantly. I tried different GNU/Linux distributions but the result is either same or worse. I assume is something related to NetworkManager and eventually Systemd. The thing is that I loose signal at some point but the network manager indicates that I have connection. After toggling Airplane mode it manages to continue to work properly but I am loosing the list with wireless connections which are available to be. For some reason it starts to show that I am connected through cable, instead of wireless. The only two ways to resolve constant drops in the signal I found is to toggle Airplane mode or restart NetworkManager. Both results to wrong indication and disables me from choosing another network. ➜ ~ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 ➜ ~ apt-cache policy network-manager network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://bg.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1670031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1612883] [NEW] ppa LibreOffice Fresh install wrong UI language
Public bug reported: After making a new installation of Linux Mint 18 Sarah with Cinnamon desktop and locale en_GB.UTF8, wanting the latest Libre Office Fresh, I added the LibreOffice (Fresh) ppa to Software Sources, and went to Update Manager: after refresh (as expected) it offered the package Libre Office 5.2.0.4 (with ~-l10n package), install of this went ok except that on checking Tools > Options > Language, UI language was English (USA) only (no alternative), not English (UK) that I expected (other language options were ok). Note: no option to specify language/locale during installation of LO, I expected it to just pick up the language automatically from system locale I had not used or tweaked LibreOffice in any way prior to adding the ppa, and installing LO Fresh on this system. Subsequently uninstalled LO Fresh and PPA, installed 'standard' (for LM 18) LO 5.1 (including ~l10n-en-gb), then added ppa and reinstalled LO Fresh (5.2) - this did correctly set UI language to English(UK) lsb_release -rd Description:Linux Mint 18 Sarah Release:18 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: fresh libreoffice ppa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1612883 Title: ppa LibreOffice Fresh install wrong UI language Status in libreoffice package in Ubuntu: New Bug description: After making a new installation of Linux Mint 18 Sarah with Cinnamon desktop and locale en_GB.UTF8, wanting the latest Libre Office Fresh, I added the LibreOffice (Fresh) ppa to Software Sources, and went to Update Manager: after refresh (as expected) it offered the package Libre Office 5.2.0.4 (with ~-l10n package), install of this went ok except that on checking Tools > Options > Language, UI language was English (USA) only (no alternative), not English (UK) that I expected (other language options were ok). Note: no option to specify language/locale during installation of LO, I expected it to just pick up the language automatically from system locale I had not used or tweaked LibreOffice in any way prior to adding the ppa, and installing LO Fresh on this system. Subsequently uninstalled LO Fresh and PPA, installed 'standard' (for LM 18) LO 5.1 (including ~l10n-en-gb), then added ppa and reinstalled LO Fresh (5.2) - this did correctly set UI language to English(UK) lsb_release -rd Description: Linux Mint 18 Sarah Release: 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1612883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1614870] Re: Problems with font cache after update
This also started to happen to me in 16.04. When I remove a certain folder with lots of fonts (the ones I copied from Mac OS X partition) from my fonts folder, the problem seems to go away. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1614870 Title: Problems with font cache after update Status in fontconfig package in Ubuntu: Confirmed Bug description: After last update on my 14.04 trusty machine, it takes a long time to regenerate the fonts cache. Now after that, most graphical applications take about 30 seconds to start with 100% CPU load. It is impossible to work with my system in this state. I already tried purging and reinstallong all fontconfig-related packages and completely deleted and rebuildt my font cache, but the problem persists. Before the update everything was fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.0-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: MATE Date: Fri Aug 19 10:11:10 2016 InstallationDate: Installed on 2014-04-16 (856 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1614870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619999] [NEW] package nvidia-304-updates 304.131-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30
Public bug reported: trying to get my third display to be reconized. it worked fine in the previous version of Ubuntu. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-304-updates 304.131-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 3 18:48:08 2016 DistUpgraded: 2016-07-05 09:02:55,443 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304-updates, 304.131, 4.4.0-28-generic, x86_64: installed vboxhost, 5.0.24, 4.2.0-41-generic, x86_64: installed vboxhost, 5.0.24, 4.4.0-28-generic, x86_64: installed ErrorMessage: subprocess installed post-installation script returned error exit status 30 GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1028:0581] NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Device [196e:082e] InstallationDate: Installed on 2016-01-29 (219 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmDisplayLog: Cannot do multiple crtcs without X server dirty tracking 2 interface randr: failed to set shadow slave pixmap MachineType: Dell Inc. Inspiron 660 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: nvidia-graphics-drivers-304-updates Title: package nvidia-304-updates 304.131-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 UpgradeStatus: Upgraded to xenial on 2016-07-05 (60 days ago) dmi.bios.date: 11/23/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0XR1GT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd11/23/2012:svnDellInc.:pnInspiron660:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron 660 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Sep 2 13:15:05 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 ** Affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/161 Title: package nvidia-304-updates 304.131-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 Status in nvidia-graphics-drivers-304-updates package in Ubuntu: New Bug description: trying to get my third display to be reconized. it worked fine in the previous version of Ubuntu. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-304-updates 304.131-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 3 18:48:08 2016 DistUpgraded: 2016-07-05 09:02:55,443 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304-updates, 304.131, 4.4.0-28-generic, x86_64: installed vboxhost, 5.0.24, 4.2.0-41-generic, x86_64: installed vboxhost, 5.0.24, 4.4.0-28-generic, x86_64: installed Err
[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
I wonder if the pulseaudio commit will fix the switching https://github.com/pulseaudio/pulseaudio/commit/e32a462cc4201d9c3c7305d0f806d16a09f08875 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Joakim Koed I would like to hear a comment about the commit I mentioned https://github.com/pulseaudio/pulseaudio/commit/e32a462cc4201d9c3c7305d0f806d16a09f08875 It does seem to be related to the switching profiles issues -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1274613] Re: module-bluetooth-discover does not load on login
At one time this bug was fixed with https://launchpad.net/ubuntu/+source/blueman/1.23-git201406261335-deb-1ubuntu1/+build/6155310/+files/blueman_1.23-git201406261335-deb-1ubuntu1_amd64.deb But it longer is in the repos -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1274613 Title: module-bluetooth-discover does not load on login Status in pulseaudio package in Ubuntu: Triaged Bug description: The following lines appear in /etc/pulse/default.pa, which I have not modified: .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif Expected: module-bluetooth-discover is loaded on login, as configured. Observed: pulseaudio's module-bluetooth-discover does not load on login. My system does not detect and set up sinks when I connect to Bluetooth devices (including an A2DP speaker and a headset). If I issue, in a terminal window: $ pactl load-module module-bluetooth-discover 24 …then the devices are detected and sinks set up correctly. $ lsb_release -rd && apt-cache policy pulseaudio-module-bluetooth Description:Ubuntu 13.10 Release:13.10 pulseaudio-module-bluetooth: Installed: 1:4.0-0ubuntu6 Candidate: 1:4.0-0ubuntu6 Version table: *** 1:4.0-0ubuntu6 0 500 http://mirrors.mit.edu/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.30-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: khaeru 2051 F pulseaudio Date: Thu Jan 30 12:18:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-29 (457 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-09-11 (140 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 085VR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn085VR5:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Luke Using your PPA, manually killing pulse and restarting it doesn't make any changes and the only way to use A2DP is the command I put in comment 100 The bug only affects audio devices that support HSP/HFP as I have a small bluetooth speaker that automatically uses A2DP without fail -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Xenial: In Progress Status in pulseaudio source package in Yakkety: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
That works much better for switching profiles with 1:8.0-0ubuntu3.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Xenial: Fix Committed Status in pulseaudio source package in Yakkety: Fix Committed Bug description: Impact: A patch we carry for Ubuntu touch introduced a change that originally was required to make sure PulseAudio did not crash. This patch was ported to PulseAudio 8 in Xenial, but the patch author's bluetooth hardware that was to hand at the time worked so was assumed to be ok. However, the opposite is now happening, i.e PulseAudio is crashing with a subset of Bluetooth hardware. Regression potential: Very low to none. As can be read in this report, much debugging and testing has been done to find the problem, and the eventual fix. Moreover the change is the removal of a patch hunk that removed a line of code originally present in PulseAudio. Test case: NOTE that this test case applies to bluetooth hardware that is identified as not working in this bug report. 1. Install, or upgrade to Xenial or yakkety. 2. Pair your bluetooth device in the bluetooth settings in the relevant settings application for your desktop environment. 3. Once paired, you will notice that sound stops working, as pulseaudio has thrown an assertion error. 4. You do not have to remove your audio device from the paired device list, but it may be easier to do so for the next part of the testing. 5. Update to the version of PulseAudio in xenial-proposed which is 1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1. 6. Re-pair your device. Audio should continue to work, and you should be able to switch to your bluetooth device and use it. Original bug report: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Xenial: Fix Committed Status in pulseaudio source package in Yakkety: Fix Committed Bug description: Impact: A patch we carry for Ubuntu touch introduced a change that originally was required to make sure PulseAudio did not crash. This patch was ported to PulseAudio 8 in Xenial, but the patch author's bluetooth hardware that was to hand at the time worked so was assumed to be ok. However, the opposite is now happening, i.e PulseAudio is crashing with a subset of Bluetooth hardware. Regression potential: Very low to none. As can be read in this report, much debugging and testing has been done to find the problem, and the eventual fix. Moreover the change is the removal of a patch hunk that removed a line of code originally present in PulseAudio. Test case: NOTE that this test case applies to bluetooth hardware that is identified as not working in this bug report. 1. Install, or upgrade to Xenial or yakkety. 2. Pair your bluetooth device in the bluetooth settings in the relevant settings application for your desktop environment. 3. Once paired, you will notice that sound stops working, as pulseaudio has thrown an assertion error. 4. You do not have to remove your audio device from the paired device list, but it may be easier to do so for the next part of the testing. 5. Update to the version of PulseAudio in xenial-proposed which is 1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1. 6. Re-pair your device. Audio should continue to work, and you should be able to switch to your bluetooth device and use it. Original bug report: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1633583] Re: Can not connect to Bluetooth headset
DimanNe See https://workingninja.com/installing-asus-bt400-raspberry-pi-raspbian-wheezy It will show how to get the firmware needed for the broadcom bluetooth device and see if the issue still exists after the firmware install -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1633583 Title: Can not connect to Bluetooth headset Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I managed to pair with my wireless headset, but I was unable to connect to it. Every time I try to do it, I get this message in syslog: Oct 14 21:38:09 localhost bluetoothd[2246]: Unable to get Headset Voice gateway SDP record: Host is down Relating info is below Info from bluetoothctl: bluetooth]# devices Device 00:1B:66:03:C4:66 MOMENTUM M2 AEBT bluetooth]# info 00:1B:66:03:C4:66 Device 00:1B:66:03:C4:66 Name: MOMENTUM M2 AEBT Alias: MOMENTUM M2 AEBT Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: yes UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (1ddce62a-ecb1-4455-8153-0743c87aec9f) Modalias: bluetooth:v0082p004Bd010E Info from hciconfig $ sudo hciconfig -a [sudo] password for dimanne: hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:73:F2:B1 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:14866 acl:33 sco:0 events:2022 errors:0 TX bytes:17848 acl:33 sco:0 commands:1639 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'impedance #1' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) hci1: Type: Primary Bus: USB BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:2926 acl:0 sco:0 events:161 errors:0 TX bytes:5699 acl:0 sco:0 commands:157 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT rfkill: $ rfkill list 1: hci1: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Info from dmesg: $ dmesg | grep -i blue [5.170808] Bluetooth: Core ver 2.21 [5.170819] Bluetooth: HCI device and connection manager initialized [5.170821] Bluetooth: HCI socket layer initialized [5.170822] Bluetooth: L2CAP socket layer initialized [5.170826] Bluetooth: SCO socket layer initialized [5.185923] Bluetooth: hci0: BCM: chip id 63 [5.186665] Bluetooth: hci1: BCM: chip id 63 [5.202506] Bluetooth: hci0: impedance #2 [5.203150] Bluetooth: hci1: ChromeLinux_5818 [5.203498] Bluetooth: hci0: BCM20702A1 (001.002.014) build [5.203670] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cb.hcd failed with error -2 [5.203671] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not found [5.204662] Bluetooth: hci1: BCM20702A1 (001.002.014) build [5.204671] bluetooth hci1: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2 [5.204671] Bluetooth: hci1: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found [ 11.359871] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.359872] Bluetooth: BNEP filters: protocol multicast [ 11.359874] Bluetooth: BNEP socket layer initialized [ 34.046364] Bluetooth: RFCOMM TTY layer initialized [ 34.046368] Bluetooth: RFCOMM socket layer initialized [ 34.046371] Bluetooth: RFCOMM ver 1.11 [ 1193.523500] Bluetooth: hci0: BCM: chip id 63 [ 1193.539525] Bluetooth: hci0: BCM20702A [ 1193.54052
[Desktop-packages] [Bug 1678481] Re: Aol Mail techncial helpdesk 1888**406*4114 Customer support number
** Tags added: spam -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1678481 Title: Aol Mail techncial helpdesk 1888**406*4114 Customer support number Status in inkscape package in Ubuntu: New Bug description: Customer Care Number, Aol support team phone number, Aol help number- Aol Helpline Number; Aol help phone number, Aol Helpline Number, Aol Support Toll free Number, Aol Support Telephone Number, Aol Support Telephone number, Aol Support support numberAol 1-888-406-4114 SuPpOrT number, Aol nical SuPpOrT number -1-844-762-8448- PHonE NumbER. It is very popular toll free number which vide by Aol SuPpOrT, Aol Customer PhoNE Number, Aol CustomerNumber, 1-844-762-8448 Aol Customer SuPpOrT PhoNENumber, Aol Customer SuPpOrT Number, Aol Customer Number, Aol Customer Number, Aol SuPpOrT team PhoNE number. Call, Aol SuPpOrT PHonE NumbER, Aol SuPpOrT 1-844-762-8448 PhoNE Number, Aol Help Desk PhoNE Number, Aol SuPpOrT number, Aol SuPpOrT PHonENumbER, Aol PhoNE number, Aol Support Phone Number, Aol SuPpOrT PHonENumbER, Aol SuPpOrT, Aol Customer PhoNE Number, Aol CustomerNumber, Aol Customer SuPpOrT PhoNE Number, Aol Customer SuPpOrT Number, Aol Customer Number, Aol Customer Number, Aol SuPpOrT team PhoNE number, Aol help number- Aol Number; Aol help PHonE NumbER, Aol Number, Aol SuPpOrT Toll freeNumber, Aol SuPpOrT TELEPhoNE Number, Aol SuPpOrT TELEPhoNE number, Aol SuPpOrT number, Aol SuPpOrTnumber, Aol SuPpOrTnumber, Aol 24/7 SuPpOrTPhoNE number, Aol TELEPhoNE 18884064114Aol Support Phone Number Aol support phone number 8448 Aol support phone number canada Aol nical support phone number Aol nical support phone number australia Aol nical support phone number uk Aol nical support phone number us Aol customer support phone number support phone number 18884064114Aol Support Phone Number Aol customer support phone number usa customer support phone number Aol support phone number Aol support phone number us Aol support support number Aol nical support support number Aol enterprise support phone number support phone number for Aol nical support phone number for Aol Aol for mac support phone number customer support phone number for Aol nical support phone number Aol 18884064114Aol Support Phone Number Aol customer support phone number Aol online support phone number Aol online customer support phone number Aol online nical support telephone number Aol point of sale support phone number Aol support phone number Aol advisor support phone number Aol pos support phone number Aol support phone number Aol nical support phone number Aol pos nical support phone number Aol nical support phone number Aol premier nical support phone number Aol plus support phone number Aol 2014 nical support phone number quicken support phone number Aol 2014 support phone number Aol customer service support phone number turbotax nical support phone number Aol support phone number usa Aol customer support phone number us Aol 2014 customer support phone number Aol 2013 nical support phone number 18884064114Aol Support Phone Number Aol premier 2012 nical support phone number Aol nical support 844 number Aol support number uk Aol support number 8448 Aol support number canada Aol support number australia Aol support number south africa Aol support number india Aol support number united states Aol support number enterprise Aol support telephone number Aol support number Aol support number Aol support number us Aol support phone number australia Aol support phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1678481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1680921] [NEW] package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Public bug reported: did not install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libasyncns0:i386 0.8-5build1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 13:48:11 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu7 DuplicateSignature: package:libasyncns0:i386:0.8-5build1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libasyncns0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-05 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libasyncns Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libasyncns (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libasyncns in Ubuntu. https://bugs.launchpad.net/bugs/1680921 Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libasyncns package in Ubuntu: New Bug description: did not install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libasyncns0:i386 0.8-5build1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 13:48:11 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu7 DuplicateSignature: package:libasyncns0:i386:0.8-5build1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libasyncns0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-05 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libasyncns Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libasyncns/+bug/1680921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1429497] Re: evolution-source-registry crashed with signal 5 in g_main_context_new()
** This bug is no longer a duplicate of private bug 1379354 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1429497 Title: evolution-source-registry crashed with signal 5 in g_main_context_new() Status in evolution-data-server package in Ubuntu: Confirmed Bug description: ? ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: evolution-data-server 3.12.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Mar 8 00:36:50 2015 ExecutablePath: /usr/lib/evolution/evolution-source-registry InstallationDate: Installed on 2014-05-29 (282 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130609) ProcCmdline: /usr/lib/evolution/evolution-source-registry Signal: 5 SourcePackage: evolution-data-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: evolution-source-registry crashed with signal 5 in g_main_context_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1429497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization)
Some users may need to disable wifi power management with sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf The command is one line and I know some Ralink USB devices work poorly with power management enabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1681513 Title: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451276] Re: No mouse over highlight in libreoffice menus in Kubuntu
Why shipping libreoffice-kde with Kubuntu whereas it's broken and don't seem to be fixed anytime soon ? Why not simply ship libreoffice-gtk instead. It's not KDE but works perfectly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1451276 Title: No mouse over highlight in libreoffice menus in Kubuntu Status in libreoffice package in Ubuntu: Triaged Bug description: No mouse over highlight in libreoffice menus in Kubuntu 15.04. Check boxes are broken/glitchy too. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libreoffice-kde 1:4.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 4 01:45:45 2015 InstallationDate: Installed on 2015-05-03 (0 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1451276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1010421] Re: Text antialiasing is green.....
I also have this problem on Netrunner 14 (based on Kubuntu 14.04). This workaround works perfectly : https://bbs.archlinux.org/viewtopic.php?pid=1486825#p1486825 I don't know if it's still happen on more recent version of Ubuntu, KDE, Gnome, etc... If anyone have more infos I will be glad to read them. ** Package changed: gimp (Ubuntu) => fontconfig (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1010421 Title: Text antialiasing is green. Status in fontconfig package in Ubuntu: Confirmed Bug description: g. So upgraded to Gimp 2.8 and now text antialaising is green. Use white text on a black background to check it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1010421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451276] Re: No mouse over highlight in libreoffice menus in Kubuntu
Can I have an answer please ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1451276 Title: No mouse over highlight in libreoffice menus in Kubuntu Status in libreoffice package in Ubuntu: Triaged Bug description: No mouse over highlight in libreoffice menus in Kubuntu 15.04. Check boxes are broken/glitchy too. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libreoffice-kde 1:4.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 4 01:45:45 2015 InstallationDate: Installed on 2015-05-03 (0 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1451276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451276] Re: No mouse over highlight in libreoffice menus in Kubuntu
I ask it on G+ and I have some feedback https://plus.google.com/103317747728601767381/posts/1wZggzRvQqu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1451276 Title: No mouse over highlight in libreoffice menus in Kubuntu Status in libreoffice package in Ubuntu: Triaged Bug description: No mouse over highlight in libreoffice menus in Kubuntu 15.04. Check boxes are broken/glitchy too. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libreoffice-kde 1:4.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 4 01:45:45 2015 InstallationDate: Installed on 2015-05-03 (0 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1451276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1071922] Re: double tap does not open folders
Almost same resut here. Can't open folder with double tap or single tap in Nautilus. I did not tried other file manager yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1071922 Title: double tap does not open folders Status in Ubuntu on the Nexus 7: Confirmed Status in “nautilus” package in Ubuntu: New Bug description: On the Nexus7 device double-tapping does not work in Nautilus. Even single taps are not always registered. In thunar navigating via double tap works fine. The mouse settings panel's double tap timeout test works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1071922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1256540] Re: "Ejecting" USB (ex. Camera) doesn't offer to empty Trash
I have this problem in Ubuntu 14.04. Nautilus don't ask "Do you want to empty the trash" when I unmount an usb stick. In Ubuntu 13.10 when I unmount a usb stick in nautilus it ask me if I want to empty the trash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1256540 Title: "Ejecting" USB (ex. Camera) doesn't offer to empty Trash Status in “nautilus” package in Ubuntu: Confirmed Bug description: I have Lubuntu 13.10 (originally 12.04). I added Nautilus, so that I could have it show date/time for photos under the thumbnails, so I can easily group them. [The current version does not have the option of selecting the type of date displayed under the thumbnails in the preferences, so I had to install Nemo, which is based on an earlier version of Nautilus, and still can. I retained Nautilus, for some reason, and the bug is true for both apps. ] When I copy photos from my USB-attached camera, I send them to trash when I am satisfied the copy was successful. When I had regular Ubuntu (various versions prior to 12.04) and clicked on "Eject" or "Safely remove drive", or whatever, I was asked whether or not I wished to empty the trash or not. At some point in Nautilus' development, some things changed. Now, there is only one option: Eject (or the equivilent clicking on the eject icon next to the device name). Now, when I select "Eject" or click on the icon, I am NOT asked if I want to empty the trash. I have repeatedly attached/removed the camera and tried both the context item and icon, but am not asked about the trash. I have to separately "select all" files in the two Trash sub-directories and click shift-del (and confirm that I wish to permanently delete the files). Why is Nautilus not asking me if I want to empty the trash? [Awhile ago, there was some discussion about the USB removal options that used to be present: "Eject", "Safely Remove Drive", and I think there might have also been a third one. I imagine the consensus was that having multiple options for essentially (literally?) the same operation was probably confusing to the user, and therefore the options were reduced to "Eject". Am I correct? The Trash ought to be emptied, in any case...] --- scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy scott@scott-ASUS-M2N68-AM-PLUS:~$ nautilus --version GNOME nautilus 3.8.2 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20~ppa1-generic-tuxonice 3.11.6 Uname: Linux 3.11.0-13-generic-tuxonice i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sat Nov 30 11:48:52 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-10-27 (33 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [deleted] usr_lib_nautilus: evince3.10.0-0ubuntu2 file-roller 3.10.1-0ubuntu1 gnome-mplayer 1.0.8-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1256540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282649] Re: Unable to make screenshot with key in Unity session in Trusty
Hello, I have an Apple Aluminium keyboard without a print screen key. Usually I set F16 to take a screenshot but it doesn't work in Ubuntu 14.04. I hope you can fix it. In the meantime I set Ctrl + M to take a screenshot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1282649 Title: Unable to make screenshot with key in Unity session in Trusty Status in “unity-settings-daemon” package in Ubuntu: Fix Released Bug description: In Trusty with all installed updates it is not possible to make ScreenShot with keyboard button. The sound /usr/share/sounds/ubuntu/stereo/dialog-error.ogg is played and desired screenshot is not saved in ~/Pictures. Tested in guest and normal sessions. Please fix this bug. Do not forget about , and . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 20 19:40:24 2014 DistUpgraded: 2013-11-19 13:23:13,179 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:907a] InstallationDate: Installed on 2013-10-20 (123 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MachineType: Sony Corporation VPCF13Z1R ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=1d9289fd-0252-4f52-9d1e-fe6baf51083a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-19 (93 days ago) dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y9 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF13Z1R dmi.product.version: C607OEHZ dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 20 19:32:11 2014 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1345778] Re: Nautilus in Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick
*** This bug is a duplicate of bug 1356871 *** https://bugs.launchpad.net/bugs/1356871 ** Description changed: - Nautilus in Ubuntu 14.04 x64 don't ask "Do you want to empty the trash" when I unmount an usb stick. - - In Ubuntu 13.10 when I unmount a usb stick in nautilus it ask me if I want to empty the trash but it doesn't in Ubuntu 14.04. + Nautilus in Ubuntu 14.04 x64 don't ask "Do you want to empty the trash" + when I unmount an usb stick. + + It's important to easily only empty the trash of the usb stick. + + In Ubuntu 13.10 when I unmount a usb stick in nautilus it ask me if I + want to empty the trash but it doesn't in Ubuntu 14.04. ** This bug has been marked a duplicate of bug 1356871 Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1345778 Title: Nautilus in Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick Status in “nautilus” package in Ubuntu: Confirmed Bug description: Nautilus in Ubuntu 14.04 x64 don't ask "Do you want to empty the trash" when I unmount an usb stick. It's important to easily only empty the trash of the usb stick. In Ubuntu 13.10 when I unmount a usb stick in nautilus it ask me if I want to empty the trash but it doesn't in Ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1345778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1356871] Re: Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick
** Description changed: Ubuntu 14.04 x64 don't ask "Do you want to empty the trash" when I unmount an usb stick. + + It's important to easily only empty the trash of the usb stick. In Ubuntu 13.10 when I unmount a usb stick it ask me if I want to empty the trash but it doesn't in Ubuntu 14.04. I already report the bug here https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1345778 ** Description changed: Ubuntu 14.04 x64 don't ask "Do you want to empty the trash" when I unmount an usb stick. It's important to easily only empty the trash of the usb stick. In Ubuntu 13.10 when I unmount a usb stick it ask me if I want to empty the trash but it doesn't in Ubuntu 14.04. - - I already report the bug here - https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1345778 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-vfs in Ubuntu. https://bugs.launchpad.net/bugs/1356871 Title: Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick Status in “gnome-vfs” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 x64 don't ask "Do you want to empty the trash" when I unmount an usb stick. It's important to easily only empty the trash of the usb stick. In Ubuntu 13.10 when I unmount a usb stick it ask me if I want to empty the trash but it doesn't in Ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1356871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1256540] Re: "Ejecting" USB (ex. Camera) doesn't offer to empty Trash
*** This bug is a duplicate of bug 1356871 *** https://bugs.launchpad.net/bugs/1356871 ** This bug is no longer a duplicate of bug 1345778 Nautilus in Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick ** This bug has been marked a duplicate of bug 1356871 Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1256540 Title: "Ejecting" USB (ex. Camera) doesn't offer to empty Trash Status in “nautilus” package in Ubuntu: Confirmed Bug description: I have Lubuntu 13.10 (originally 12.04). I added Nautilus, so that I could have it show date/time for photos under the thumbnails, so I can easily group them. [The current version does not have the option of selecting the type of date displayed under the thumbnails in the preferences, so I had to install Nemo, which is based on an earlier version of Nautilus, and still can. I retained Nautilus, for some reason, and the bug is true for both apps. ] When I copy photos from my USB-attached camera, I send them to trash when I am satisfied the copy was successful. When I had regular Ubuntu (various versions prior to 12.04) and clicked on "Eject" or "Safely remove drive", or whatever, I was asked whether or not I wished to empty the trash or not. At some point in Nautilus' development, some things changed. Now, there is only one option: Eject (or the equivilent clicking on the eject icon next to the device name). Now, when I select "Eject" or click on the icon, I am NOT asked if I want to empty the trash. I have repeatedly attached/removed the camera and tried both the context item and icon, but am not asked about the trash. I have to separately "select all" files in the two Trash sub-directories and click shift-del (and confirm that I wish to permanently delete the files). Why is Nautilus not asking me if I want to empty the trash? [Awhile ago, there was some discussion about the USB removal options that used to be present: "Eject", "Safely Remove Drive", and I think there might have also been a third one. I imagine the consensus was that having multiple options for essentially (literally?) the same operation was probably confusing to the user, and therefore the options were reduced to "Eject". Am I correct? The Trash ought to be emptied, in any case...] --- scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy scott@scott-ASUS-M2N68-AM-PLUS:~$ nautilus --version GNOME nautilus 3.8.2 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20~ppa1-generic-tuxonice 3.11.6 Uname: Linux 3.11.0-13-generic-tuxonice i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sat Nov 30 11:48:52 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-10-27 (33 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [deleted] usr_lib_nautilus: evince3.10.0-0ubuntu2 file-roller 3.10.1-0ubuntu1 gnome-mplayer 1.0.8-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1256540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192028] Re: Compiz refresh rate resets to 50 Hz automatically w/ Nvidia proprietary driver
Me too, my refresh rate is still being detected as 50Hz according to CCSM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1192028 Title: Compiz refresh rate resets to 50 Hz automatically w/ Nvidia proprietary driver Status in Compiz: Fix Committed Status in One Hundred Papercuts: Triaged Status in “compiz” package in Ubuntu: Fix Released Bug description: There have been similar bug reports to this one, such as bug #1009338 and bug #1027868, but I believe this case is different. The problem I am having is that even after I set the refresh rate options in compiz to 60 Hz (after disabling the "Detect Refresh Rate" option), a reboot will have the settings revert. If I change settings in the compiz config settings manager, they should remain even after a reboot. --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 313.30 Wed Mar 27 16:56:45 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-04-28 10:18:35,447 DEBUG enabling apt cron job DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:022e] InstallationDate: Installed on 2011-10-16 (611 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. XPS M1530 MarkForUpload: True NonfreeKernelModules: nvidia Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=67324911-aae9-47ca-a177-6c818959ed59 ro quiet splash ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Tags: raring raring ubuntu compiz-0.9 Uname: Linux 3.8.0-23-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-28 (50 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare vboxusers video dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Mon Jun 17 17:22:09 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1192028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1345778] [NEW] Nautilus in Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick
Public bug reported: Nautilus in Ubuntu 14.04 x64 don't ask "Do you want to empty the trash" when I unmount an usb stick. In Ubuntu 13.10 when I unmount a usb stick in nautilus it ask me if I want to empty the trash but it doesn't in Ubuntu 14.04. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1345778 Title: Nautilus in Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick Status in “nautilus” package in Ubuntu: New Bug description: Nautilus in Ubuntu 14.04 x64 don't ask "Do you want to empty the trash" when I unmount an usb stick. In Ubuntu 13.10 when I unmount a usb stick in nautilus it ask me if I want to empty the trash but it doesn't in Ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1345778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1256540] Re: "Ejecting" USB (ex. Camera) doesn't offer to empty Trash
*** This bug is a duplicate of bug 1345778 *** https://bugs.launchpad.net/bugs/1345778 ** This bug has been marked a duplicate of bug 1345778 Nautilus in Ubuntu 14.04 don't ask “Do you want to empty the trash” when I unmount an usb stick -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1256540 Title: "Ejecting" USB (ex. Camera) doesn't offer to empty Trash Status in “nautilus” package in Ubuntu: Confirmed Bug description: I have Lubuntu 13.10 (originally 12.04). I added Nautilus, so that I could have it show date/time for photos under the thumbnails, so I can easily group them. [The current version does not have the option of selecting the type of date displayed under the thumbnails in the preferences, so I had to install Nemo, which is based on an earlier version of Nautilus, and still can. I retained Nautilus, for some reason, and the bug is true for both apps. ] When I copy photos from my USB-attached camera, I send them to trash when I am satisfied the copy was successful. When I had regular Ubuntu (various versions prior to 12.04) and clicked on "Eject" or "Safely remove drive", or whatever, I was asked whether or not I wished to empty the trash or not. At some point in Nautilus' development, some things changed. Now, there is only one option: Eject (or the equivilent clicking on the eject icon next to the device name). Now, when I select "Eject" or click on the icon, I am NOT asked if I want to empty the trash. I have repeatedly attached/removed the camera and tried both the context item and icon, but am not asked about the trash. I have to separately "select all" files in the two Trash sub-directories and click shift-del (and confirm that I wish to permanently delete the files). Why is Nautilus not asking me if I want to empty the trash? [Awhile ago, there was some discussion about the USB removal options that used to be present: "Eject", "Safely Remove Drive", and I think there might have also been a third one. I imagine the consensus was that having multiple options for essentially (literally?) the same operation was probably confusing to the user, and therefore the options were reduced to "Eject". Am I correct? The Trash ought to be emptied, in any case...] --- scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy scott@scott-ASUS-M2N68-AM-PLUS:~$ nautilus --version GNOME nautilus 3.8.2 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20~ppa1-generic-tuxonice 3.11.6 Uname: Linux 3.11.0-13-generic-tuxonice i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sat Nov 30 11:48:52 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-10-27 (33 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [deleted] usr_lib_nautilus: evince3.10.0-0ubuntu2 file-roller 3.10.1-0ubuntu1 gnome-mplayer 1.0.8-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1256540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054679] [NEW] seahorse crash, i believe this coincides with my pulseaudio crash when the computer attempted to idle down and isntead stayed logged in and the screen flickered
Public bug reported: Description:Ubuntu 22.04.4 LTS Release:22.04 seahorse: Installed: 41.0-2 Candidate: 41.0-2 Version table: *** 41.0-2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status I expected the computer to idle down and what happened instead is the computer did not idle down and the sound and brightness stopped working, the screen flickered dark to dim to bright. Keeping the dimmer at 5% keeps the brightness at 100% and stops the flickering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: seahorse 41.0-2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 22 03:22:28 2024 InstallationDate: Installed on 2023-10-18 (126 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/2054679 Title: seahorse crash, i believe this coincides with my pulseaudio crash when the computer attempted to idle down and isntead stayed logged in and the screen flickered and sound stopped working. Keeping the dimmer at 5% keeps the brightness at 100% and stops the flickering. Bluetooth audio speaker works. Status in seahorse package in Ubuntu: New Bug description: Description: Ubuntu 22.04.4 LTS Release: 22.04 seahorse: Installed: 41.0-2 Candidate: 41.0-2 Version table: *** 41.0-2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status I expected the computer to idle down and what happened instead is the computer did not idle down and the sound and brightness stopped working, the screen flickered dark to dim to bright. Keeping the dimmer at 5% keeps the brightness at 100% and stops the flickering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: seahorse 41.0-2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 22 03:22:28 2024 InstallationDate: Installed on 2023-10-18 (126 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/2054679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054675] [NEW] pulseaudio sound not working, coincides with brightness controller not working and screen flickering, occurred when computer attempted to go idle and instead fli
Public bug reported: Description:Ubuntu 22.04.4 LTS Release:22.04 pulseaudio: Installed: 1:15.99.1+dfsg1-1ubuntu2.1 Candidate: 1:15.99.1+dfsg1-1ubuntu2.1 Version table: *** 1:15.99.1+dfsg1-1ubuntu2.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.99.1+dfsg1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages I expected the computer to idle down and instead the computer did not idle down and chose to flicker the brightness from dim to dark to 100% and the audio stopped working. Keeping the dimmer on about 5% keeps the brightness at 100% and stops the flickering. Bluetooth audio speaker works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Thu Feb 22 03:17:38 2024 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2023-10-18 (126 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2022 dmi.bios.release: 1.57 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.57 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.57:bd07/28/2022:br1.57:efr133.121:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:sku1DV78US#ABA: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: 1DV78US#ABA dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2054675 Title: pulseaudio sound not working, coincides with brightness controller not working and screen flickering, occurred when computer attempted to go idle and instead flickered and crashed these applets Status in pulseaudio package in Ubuntu: New Bug description: Description: Ubuntu 22.04.4 LTS Release: 22.04 pulseaudio: Installed: 1:15.99.1+dfsg1-1ubuntu2.1 Candidate: 1:15.99.1+dfsg1-1ubuntu2.1 Version table: *** 1:15.99.1+dfsg1-1ubuntu2.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.99.1+dfsg1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages I expected the computer to idle down and instead the computer did not idle down and chose to flicker the brightness from dim to dark to 100% and the audio stopped working. Keeping the dimmer on about 5% keeps the brightness at 100% and stops the flickering. Bluetooth audio speaker works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Thu Feb 22 03:17:38 2024 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2023-10-18 (126 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2022 dmi.bios.release: 1.57 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.57 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.57:bd07/28/2022:br1.57:efr133.121:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:sku1DV78US#ABA: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: 1DV78US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2054675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launc
[Desktop-packages] [Bug 1940543] Re: Show Hidden Files does not persist and even resets during the same session
I think I know why this is happening now. One of the first things I do when I do a fresh install is remove MySQL since I need to use MySQL 5.7 as 8 causes issues with the projects I work on. This shows me it is going to remove: colord gnome-control-center hplip libhpmud0 libmysqlclient21 libsane libsane-hpaio libsnmp35 mysql-common mysql-workbench-community printer-driver-hpcups sane-utils simple-scan ubuntu-desktop ubuntu-desktop-minimal I normally use `-y` flag but this time I didn't so I wasn't even aware of this happening. This explains why I had to reinstall the desktop and the gnome control center. This is why I was having issues with the hidden files. While I see this is not a "bug", depending on MySQL 8 is frustrating as this causes many issues when all databases used in enterprise are working with MySQL 5.7. This is mostly due to AWS not supporting 8 for Aurora so this is just an inconvenience for now. I will need to find a better way to install MySQL 5.7 next to 8 as 5.7 is a requirement for my needs and 8 causes too many issues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1940543 Title: Show Hidden Files does not persist and even resets during the same session Status in nautilus package in Ubuntu: New Bug description: Since 20.04 has been released, the option "Show Hidden Files" has never lasted long. It never persists over a reboot and even during the same session, it will just hide the files after some random (it seems random) interval. This happens for me on 3 different computers, all different builds. This happens on a vanilla install too. I have never been able to make "Show Hidden Files" last longer than an hourish, and never over a reboot. I work a lot in hidden files, this is mostly just frustrating to me since it happens randomly and when I am moving around a project, I have to keep toggling "Show Hidden Files" to get work done. I did have to reinstall `gnome-control-center` after a fresh install and updating Ubuntu 20.04 the latest version, I am not sure if that could help identify the issue but I have always had this issue on 20.04 so I am doubtful. I did this running: ``` sudo apt install --reinstall gnome-control-center ``` I had to reinstall this since Settings was no longer available after the system was updated (fresh install with `sudo apt update && sudo apt upgrade` is what broken it for me to have to reinstall it. I even tried using: ``` gsettings set org.gtk.Settings.FileChooser show-hidden true ``` but the issue still happens. Also, not sure why nautilus is installed, I thought 20.04 was gnome? Again, this is a fresh install (15 days old) ``` $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` ``` $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ``` ``` apt-cache policy gnome gnome: Installed: (none) Candidate: 1:3.30+2 Version table: 1:3.30+2 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:46:31 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1280, 1393)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-08-03 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1940543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : htt
[Desktop-packages] [Bug 1995798] Re: MT7921K high latency when bluetooth headset is used
** Bug watch added: Linux Kernel Bug Tracker #216668 https://bugzilla.kernel.org/show_bug.cgi?id=216668 ** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=216668 Importance: Unknown Status: Unknown ** Project changed: bluez => linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995798 Title: MT7921K high latency when bluetooth headset is used Status in Linux: Unknown Status in bluez package in Ubuntu: New Bug description: When I use onboard WiFi and Bluetooth headset at the same time, the latency goes from ~30-50ms to 200-6500ms Motherboard: ASUS TUF GAMING X670E-PLUS WIFI BIOS: 0809 Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream 6.0.[135] $ lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 Also made upstream kernel bz: https://bugzilla.kernel.org/show_bug.cgi?id=216668 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 Uname: Linux 6.0.5-060005-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 15:44:14 2022 InstallationDate: Installed on 2022-10-15 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2022 dmi.bios.release: 8.9 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:6F:D9:DD:4A:B0 ACL MTU: 1021:6 SCO MTU: 240:8 UP RUNNING PSCAN RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0 TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1995798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories
I too have this issue with third-party .deb files. I have just installed 16.04 in UEFI with / and /home on their own partitions. When I booted, I updated my box and was able to install Slack using the Software Center. After that, I went to install Chrome and it wouldn't work. Now, no third-party .deb files will install through the software center. I am able to install any default package from the Ubuntu Software Center but I am not able to install any .deb files unless I manually install them using: `sudo dpkg -i PATH_TO_DEB_FILE.deb` I have fully updated my system after a fresh install. I ran: ``` sudo apt update Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease Hit:2 http://dl.google.com/linux/chrome/deb stable Release Hit:4 http://us.archive.ubuntu.com/ubuntu xenial InRelease Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Fetched 306 kB in 0s (542 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. ``` ``` sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` ``` sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue still persists. At this point, I can only install manually. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1672424 Title: Cannot install Debian files outside of the repositories Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Released Status in gnome-software source package in Yakkety: Fix Released Status in gnome-software source package in Zesty: Fix Released Bug description: Impact -- It is not possible to use the default Software app to install .debs for packages that are not already available in Ubuntu. Test Case - 1. a. Download the .deb for a simple app for your version of Ubuntu directly from Launchpad. For 16.10, try https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/ Click amd64 then download the last .deb on that page. b. Open the .deb with gnome-software: gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb gnome-software should open to a page with an Install button for the package. This test case should already work. 2. a. Download a .deb that is not already in Ubuntu. It is important that the package not be available in your local apt cache. https://www.google.com/chrome/ https://itch.io/app b. Open the .deb with gnome-software gnome-software --local-filename=itch_23.2.1_amd64.deb gnome-software should open to a page with an Install button for the package. Click Install and verify that the app is installed. What Happens The second test fails. On Ubuntu 17.04, I get a popup "Sorry this did not work The file is not supported" On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No file_to_app results to show" Regression Potential Original Bug Report --- .deb files fail to install from non repository locations i.e. The file manager gnome-software claims "this file type is not supported". Using dpkg from the command line works as expected so the files aren't corrupt. This happened last distribution as well when it was first released. Might be a regression caused by adding snap package capabilities to the software-center? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 13 10:02:00 2017 InstallationDate: Installed on 2017-02-20 (20 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions -- Mailing lis
[Desktop-packages] [Bug 1713241] Re: I am unable to create Wifi HotSpot on my Ubuntu17.10. Kindly help
There is no module loaded for your wifi, what have you done to try to fix this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1713241 Title: I am unable to create Wifi HotSpot on my Ubuntu17.10. Kindly help Status in network-manager package in Ubuntu: New Bug description: Hi People, I"m unable to create wifihotspot on my Ubuntu 17.10 version laptop. I was even not able to do it in Ubuntu 16.04 version as well. Here is my Laptop's Network hardware http://paste.ubuntu.com/25396803/ I got Acer 4720Z laptop. 32 bit. And even in my network manager, the Device mac number isn't available to chose. Kindly help. This issue has been reported on various forums, not just for 17.10 but also, 16.04,17.04 and there is no proper guidance to any or no possible solution yet available online. Kindly help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779569] Re: thunderbird showing weird images in some mail
sudo apt-get install fonts-symbola May be a dupe of https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1779569 Title: thunderbird showing weird images in some mail Status in thunderbird package in Ubuntu: New Bug description: New install of 18.04 and thunderbird is showing weird images in odd places for some email. See screen shot for example. In this case it is a weird rainbow, but I have also seen other things like a big stop sign and other strange stuff. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1779569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782470] Re: ubuntu 16.04 linux kernel 4.15.0-24-generic wireless
Boot into the kernel with working internet, in terminal do sudo apt-get install --reinstall linux-modules-extra-4.15.0-24 Reboot and see if wireless works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1782470 Title: ubuntu 16.04 linux kernel 4.15.0-24-generic wireless Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: I am not able to connect to wifi after update. Wireless connection is misssing in network setting. My ubuntu version is 16.04. And the kernel version is linux kernel 4.15.0-24-generic. I can connect to wifi when I go back to my earlier kernel version of 4.13,0-45 generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871791] [NEW] Update to Unicode 12.1 release
Public bug reported: Google has released a new version of their Noto Emoji font. I don't believe this requires a freeze exception since we should do these updates if possible so that emoji display correctly in Ubuntu. For more details, see https://blog.emojipedia.org/google-march-2020-pixel-feature-drop-emoji-changelog/ If we don't take this particular update, the biggest downside will be that emojis show up as separate parts. For example, the gender neutral health care worker will appear as two characters (adult and the medical symbol) instead of as a single character. https://emojipedia.org/health-worker/ However, we will also need an updated Pango for those new combined emoji to display as a single emoji in apps using Pango (such as GTK apps). https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539f4a15a2ae3977d715e82035ea5b32d7 ** Affects: fonts-noto-color-emoji (Ubuntu) Importance: Undecided Assignee: Jeremy Bicha (jbicha) Status: New ** Tags: focal upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1871791 Title: Update to Unicode 12.1 release Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: Google has released a new version of their Noto Emoji font. I don't believe this requires a freeze exception since we should do these updates if possible so that emoji display correctly in Ubuntu. For more details, see https://blog.emojipedia.org/google-march-2020-pixel-feature-drop-emoji-changelog/ If we don't take this particular update, the biggest downside will be that emojis show up as separate parts. For example, the gender neutral health care worker will appear as two characters (adult and the medical symbol) instead of as a single character. https://emojipedia.org/health-worker/ However, we will also need an updated Pango for those new combined emoji to display as a single emoji in apps using Pango (such as GTK apps). https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539f4a15a2ae3977d715e82035ea5b32d7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1871791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871791] Re: Update to Unicode 12.1 release
** Changed in: fonts-noto-color-emoji (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1871791 Title: Update to Unicode 12.1 release Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: Google has released a new version of their Noto Emoji font. I don't believe this requires a freeze exception since we should do these updates if possible so that emoji display correctly in Ubuntu. For more details, see https://blog.emojipedia.org/google-march-2020-pixel-feature-drop-emoji-changelog/ If we don't take this particular update, the biggest downside will be that emojis show up as separate parts. For example, the gender neutral health care worker will appear as two characters (adult and the medical symbol) instead of as a single character. https://emojipedia.org/health-worker/ However, we will also need an updated Pango for those new combined emoji to display as a single emoji in apps using Pango (such as GTK apps). https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539f4a15a2ae3977d715e82035ea5b32d7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1871791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871791] Re: Update to Unicode 12.1 release
** Description changed: Google has released a new version of their Noto Emoji font. I don't believe this requires a freeze exception since we should do these updates if possible so that emoji display correctly in Ubuntu. For more details, see https://blog.emojipedia.org/google-march-2020-pixel-feature-drop-emoji-changelog/ + and + https://emojipedia.org/emoji-12.1/ If we don't take this particular update, the biggest downside will be that emojis show up as separate parts. For example, the gender neutral health care worker will appear as two characters (adult and the medical symbol) instead of as a single character. https://emojipedia.org/health-worker/ - - However, we will also need an updated Pango for those new combined emoji - to display as a single emoji in apps using Pango (such as GTK apps). - - https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539f4a15a2ae3977d715e82035ea5b32d7 ** Changed in: fonts-noto-color-emoji (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1871791 Title: Update to Unicode 12.1 release Status in fonts-noto-color-emoji package in Ubuntu: Fix Committed Bug description: Google has released a new version of their Noto Emoji font. I don't believe this requires a freeze exception since we should do these updates if possible so that emoji display correctly in Ubuntu. For more details, see https://blog.emojipedia.org/google-march-2020-pixel-feature-drop-emoji-changelog/ and https://emojipedia.org/emoji-12.1/ If we don't take this particular update, the biggest downside will be that emojis show up as separate parts. For example, the gender neutral health care worker will appear as two characters (adult and the medical symbol) instead of as a single character. https://emojipedia.org/health-worker/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1871791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871791] Re: Update to Unicode 12.1 release
** Description changed: Google has released a new version of their Noto Emoji font. I don't believe this requires a freeze exception since we should do these updates if possible so that emoji display correctly in Ubuntu. For more details, see - https://blog.emojipedia.org/google-march-2020-pixel-feature-drop-emoji-changelog/ + https://emojipedia.org/google/android-10.0-march-2020-feature-drop/ and https://emojipedia.org/emoji-12.1/ If we don't take this particular update, the biggest downside will be that emojis show up as separate parts. For example, the gender neutral health care worker will appear as two characters (adult and the medical symbol) instead of as a single character. https://emojipedia.org/health-worker/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1871791 Title: Update to Unicode 12.1 release Status in fonts-noto-color-emoji package in Ubuntu: Fix Committed Bug description: Google has released a new version of their Noto Emoji font. I don't believe this requires a freeze exception since we should do these updates if possible so that emoji display correctly in Ubuntu. For more details, see https://emojipedia.org/google/android-10.0-march-2020-feature-drop/ and https://emojipedia.org/emoji-12.1/ If we don't take this particular update, the biggest downside will be that emojis show up as separate parts. For example, the gender neutral health care worker will appear as two characters (adult and the medical symbol) instead of as a single character. https://emojipedia.org/health-worker/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1871791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871972] [NEW] Update pango for Unicode 13.0
Public bug reported: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ By doing this update for Ubuntu 18.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts-noto- color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871972 Title: Update pango for Unicode 13.0 Status in pango1.0 package in Ubuntu: New Bug description: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ By doing this update for Ubuntu 18.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts- noto-color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871972] Re: Update pango for Unicode 13.0
** Description changed: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ + + Pango is used by many apps (particularly GTK apps) to display emoji. By doing this update for Ubuntu 18.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts-noto- color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. + References + =- https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 + https://emojipedia.org/emoji-13.0/ + https://github.com/googlefonts/noto-emoji/releases -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871972 Title: Update pango for Unicode 13.0 Status in pango1.0 package in Ubuntu: New Bug description: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ Pango is used by many apps (particularly GTK apps) to display emoji. By doing this update for Ubuntu 18.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts- noto-color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. References =- https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 https://emojipedia.org/emoji-13.0/ https://github.com/googlefonts/noto-emoji/releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871972] Re: Update pango for Unicode 13.0
Yes, only 20.04. ** Description changed: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ - Pango is used by many apps (particularly GTK apps) to display emoji. - - By doing this update for Ubuntu 18.04 LTS now, it will be easier to get + By doing this update for Ubuntu 20.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts-noto- color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. - References - =- https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 - https://emojipedia.org/emoji-13.0/ - https://github.com/googlefonts/noto-emoji/releases -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871972 Title: Update pango for Unicode 13.0 Status in pango1.0 package in Ubuntu: Fix Committed Bug description: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ By doing this update for Ubuntu 20.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts- noto-color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870794] Re: missing some emojis
Historically, Google tends to release its annual Unicode/Emoji update for this font around the time it releases the next major version of Android. Android 11 is expected in the 3rd quarter of 2020. We probably will push the update to Ubuntu 20.04 LTS then. ** Summary changed: - missing some emojis + Update for Unicode 13 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1870794 Title: Update for Unicode 13 Status in fonts-noto-color-emoji package in Ubuntu: Confirmed Bug description: The current version is missing some emojis which are already available upstream. I didn't check them all but it seems they are v13 emojis. You can see the missing ones as tofu from here: https://unicode.org/emoji/charts/full-emoji-list.html ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 17:25:41 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1870794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
** Bug watch added: Debian Bug tracker #956520 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956520 ** Also affects: pango1.0 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956520 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 package in Debian: Unknown Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from focal
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from focal Status in adobe-flashplugin package in Ubuntu: New Status in flashplugin-nonfree package in Ubuntu: New Status in pepperflashplugin-nonfree package in Ubuntu: New Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in Focal. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in Focal? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1871471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends
@AsciiWorld, unless things changed in Ubuntu 20.04 LTS, you can use the Software app to install GNOME Shell extensions. chrome-gnome-shell is in universe. It needs to be in main before it can be installed by default in the Canonical-supported flavors. See https://wiki.ubuntu.com/MainInclusionProcess and bug 1695565 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: Add chrome-gnome-shell to ubuntu-desktop recommends Status in One Hundred Papercuts: Opinion Status in chrome-gnome-shell package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Please, consider adding the chrome-gnome-shell package as a recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The chrome-gnome-shell package provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers that is necessary for users to be able to manage GNOME Shell extensions using a extensions.gnome.org website. Since the Shell Extensions support was removed from gnome-software since 3.36 and the replacement Extensions application cannot be used to find and install new extensions, there is not any user friendly way to install new Shell Extensions without having the chrome-gnome-shell package installed. More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends
We can do #3. Do you want to update the bug description for that? We'll need to file this as a potential SRU, but it might get fixed before the 20.04 LTS release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: Add chrome-gnome-shell to ubuntu-desktop recommends Status in One Hundred Papercuts: Opinion Status in chrome-gnome-shell package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Please, consider adding the chrome-gnome-shell package as a recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The chrome-gnome-shell package provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers that is necessary for users to be able to manage GNOME Shell extensions using a extensions.gnome.org website. Since the Shell Extensions support was removed from gnome-software since 3.36 and the replacement Extensions application cannot be used to find and install new extensions, there is not any user friendly way to install new Shell Extensions without having the chrome-gnome-shell package installed. More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873692] [NEW] Do Not Disturb setting does not persist across login sessions
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Selecting do not disturb from settings does not persist across login sessions. What I did - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar What happens: - Do Not Disturb is reset to disabled on each new login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873692 Title: Do Not Disturb setting does not persist across login sessions Status in gnome-control-center package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Selecting do not disturb from settings does not persist across login sessions. What I did - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar What happens: - Do Not Disturb is reset to disabled on each new login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions
I have a feeling you are right that it may not be gnome-control-center doing this as setting the default value of show-banners in /usr/share/glib2.0/schemas to false ends up being ignored at login. It is unclear to me what the desired behaviour is from those discussions, but my expectation is that an exposed user setting will stay set until I unset it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873692 Title: Do Not Disturb setting does not persist across login sessions Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Selecting do not disturb from settings does not persist across login sessions. What I did - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar What happens: - Do Not Disturb is reset to disabled on each new login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions
Done (https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/961). Hopefully I submitted it correctly. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #961 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/961 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873692 Title: Do Not Disturb setting does not persist across login sessions Status in gnome-shell package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Selecting do not disturb from settings does not persist across login sessions. What I did - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar What happens: - Do Not Disturb is reset to disabled on each new login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: [SRU] Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: [SRU] Move gnome-shell-extension-prefs to universe and add chrome- gnome-shell to its recommends Status in gnome-shell package in Ubuntu: In Progress Bug description: [Impact] * Since GNOME 3.36, Shell Extensions can no longer be installed using GNOME Software (Ubuntu Software), instead there was a new Extensions (gnome-shell-extension-prefs) application prepared to replace this functionality. However, this application itself does not support installing new extensions, instead, it opens a web browser with a extensions.gnome.org website that allows browsing and installing new extensions. This website depends on a chrome-gnome-shell package that provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers for this functionality. Without this connector, it is not possible to install Shell Extensions on Ubuntu 20.04. * In this SRU, I want to propose adding this chrome-gnome-shell package to recommends of the gnome-shell-extension-prefs package. However, since the gnome-shell-extension-prefs package is in a main repository and chrome-gnome-shell is in universe, it would be probably also needed to first move the gnome-shell-extension-prefs package to universe. [Test Case] * Install the "gnome-shell-extension-prefs" (Extensions) application. * Open the "Extensions" application, click the "i" button in the window header, click the "extensions.gnome.org" link. * In the web browser window, click on link inside the blue notification on extensions.gnome.org to install a browser extension (frontend for the connector), then refresh the page. * After this, a red notification appears on the web page telling the user that host connector is not running. [Regression Potential] * Without the chrome-gnome-shell package installed, it is not possible to install Shell Extensions on Ubuntu 20.04. [Other Info] * More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: [SRU] Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends
gnome-shell-extension-prefs is now in universe. That makes the remainder of this bug a simple SRU candidate. I uploaded this change to the focal queue earlier today. It will need to be manually approved to be accepted into Ubuntu 20.04 LTS. ** Summary changed: - [SRU] Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends + [SRU] Add chrome-gnome-shell to the recommends of gnome-shell-extension-prefs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: [SRU] Add chrome-gnome-shell to the recommends of gnome-shell- extension-prefs Status in gnome-shell package in Ubuntu: In Progress Bug description: [Impact] * Since GNOME 3.36, Shell Extensions can no longer be installed using GNOME Software (Ubuntu Software), instead there was a new Extensions (gnome-shell-extension-prefs) application prepared to replace this functionality. However, this application itself does not support installing new extensions, instead, it opens a web browser with a extensions.gnome.org website that allows browsing and installing new extensions. This website depends on a chrome-gnome-shell package that provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers for this functionality. Without this connector, it is not possible to install Shell Extensions on Ubuntu 20.04. * In this SRU, I want to propose adding this chrome-gnome-shell package to recommends of the gnome-shell-extension-prefs package. However, since the gnome-shell-extension-prefs package is in a main repository and chrome-gnome-shell is in universe, it would be probably also needed to first move the gnome-shell-extension-prefs package to universe. [Test Case] * Install the "gnome-shell-extension-prefs" (Extensions) application. * Open the "Extensions" application, click the "i" button in the window header, click the "extensions.gnome.org" link. * In the web browser window, click on link inside the blue notification on extensions.gnome.org to install a browser extension (frontend for the connector), then refresh the page. * After this, a red notification appears on the web page telling the user that host connector is not running. [Regression Potential] * Without the chrome-gnome-shell package installed, it is not possible to install Shell Extensions on Ubuntu 20.04. [Other Info] * More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: [SRU] Add chrome-gnome-shell to the recommends of gnome-shell-extension-prefs
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: [SRU] Add chrome-gnome-shell to the recommends of gnome-shell- extension-prefs Status in gnome-shell package in Ubuntu: In Progress Bug description: [Impact] * Since GNOME 3.36, Shell Extensions can no longer be installed using GNOME Software (Ubuntu Software), instead there was a new Extensions (gnome-shell-extension-prefs) application prepared to replace this functionality. However, this application itself does not support installing new extensions, instead, it opens a web browser with a extensions.gnome.org website that allows browsing and installing new extensions. This website depends on a chrome-gnome-shell package that provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers for this functionality. Without this connector, it is not possible to install Shell Extensions on Ubuntu 20.04. * In this SRU, I want to propose adding this chrome-gnome-shell package to recommends of the gnome-shell-extension-prefs package. However, since the gnome-shell-extension-prefs package is in a main repository and chrome-gnome-shell is in universe, it would be probably also needed to first move the gnome-shell-extension-prefs package to universe. [Test Case] * Install the "gnome-shell-extension-prefs" (Extensions) application. * Open the "Extensions" application, click the "i" button in the window header, click the "extensions.gnome.org" link. * In the web browser window, click on link inside the blue notification on extensions.gnome.org to install a browser extension (frontend for the connector), then refresh the page. * After this, a red notification appears on the web page telling the user that host connector is not running. [Regression Potential] * Without the chrome-gnome-shell package installed, it is not possible to install Shell Extensions on Ubuntu 20.04. [Other Info] * More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883534] Re: Screen flickering
*** This bug is a duplicate of bug 1853094 *** https://bugs.launchpad.net/bugs/1853094 Dear Mr Daniel Van Vugt, Choosing 'ubuntu on Wayland' in logging screen fixed the flickerings, thanks a lot ! Best, Jeremy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1883534 Title: Screen flickering Status in xorg package in Ubuntu: New Bug description: To whom it may concern, As stated I have screen flickerings (see lightning like flickering on photo attached for portrait screen, for horizontal screen I also have screen flickering on the upper part but hard to catch in a photo) on freshly installed Ubuntu 20.04 LTS. I have tried this: https://askubuntu.com/questions/1231441/ubuntu-screen-flickering and this: https://learnubuntumate.weebly.com/screen-tearing-on-intel- graphics.html without success. I have also seen some other people mentioning screen flickering on ubuntu 20.04 here: https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/ without solution. I also know that it is very unlikely hardware problem because my screens were displaying well on archlinux. I think my graphic card info are already included in the report but just in case: Intel Corporation UHD Graphics 630. Might be intel driver problems ? Could you help me on this please ? Best regards, Jeremy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 15:05:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] InstallationDate: Installed on 2020-06-12 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046a:0023 Cherry GmbH Keyboard Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0615 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions
Hi, I have now installed gnome-shell/focal-proposed,now 3.36.3-1ubuntu1~20.04.2 amd64 [installed] and the patch works as expected. The setting of Do Not Disturb persists across login sessions. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873692 Title: Do Not Disturb setting does not persist across login sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Bug description: [ Impact ] Selecting do not disturb from settings does not persist across login sessions. [ Test case ] - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar [ Regresion potential ] Togglingg the do not disturb toggle doesn't work anymore Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status - Do Not Disturb is reset to disabled on each new login ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bashSourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1873692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
@Daniel, this bug has absolutely nothing to do with using an Android Emulator. I literally get this crash every five minutes, and I've never used emulation or virtualization of any kind on either of my machines. I think the Android Emulator was just a red herring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
I can confirm that xkb-data 2.23.1-1ubuntu1.18.04.1 fixes this issue for me on bionic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Status in xkeyboard-config source package in Disco: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
When can we expect a release of the proposed xkb-data? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Status in xkeyboard-config source package in Disco: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
@Daniel, I understand that you want to reproduce it. However, if you aren't experiencing this bug, then that tells me you don't have a hardware configuration that is affected by it. If you're affected, reproducing it is very easy - simply use the keyboard shortcut designated for switching up or down to another workspace. Every time I do this, I have a one in five chance of GNOME crashing. It's so common that I have no chance of NOT reproducing it. As for apps, if it matters, I only have Firefox, Thunderbird, and gnome- terminal open at any one time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805025] Re: gnome-control-center power - 'Turn off Wi-Fi to save power' label is confusing
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #53 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/53 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/53 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1805025 Title: gnome-control-center power - 'Turn off Wi-Fi to save power' label is confusing Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: The 'Turn off Wi-Fi to save power' setting defaults to ON. Toggling 'Turn off Wi-Fi to save power' to OFF causes the wifi device to be soft blocked. BEFORE$ sudo rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no AFTER$ sudo rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: no $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.2 Candidate: 1:3.28.2-0ubuntu0.18.04.2 Version table: *** 1:3.28.2-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: Power saving for wifi will be disabled. Actual behavior: Wifi is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1805025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819183] [NEW] FFe: Update pygobject to 3.32
Public bug reported: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.31.4-1 is in Debian experimental ready to be synced over once this FFe is approved. 3.32.0 is expected next week. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: New Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.31.4-1 is in Debian experimental ready to be synced over once this FFe is approved. 3.32.0 is expected next week. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install
amano, please open a new bug for new issues instead of commenting on old closed bugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32
** Description changed: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. - 3.31.4-1 is in Debian experimental ready to be synced over once this FFe - is approved. 3.32.0 is expected next week. + 3.32.0-1 is in Debian experimental ready to be synced over once this FFe + is approved. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS - https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) + https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: New Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.32.0-1 is in Debian experimental ready to be synced over once this FFe is approved. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: New Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.32.0-1 is in Debian experimental ready to be synced over once this FFe is approved. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32
This bug was fixed in the package pygobject - 3.32.0-1 --- pygobject (3.32.0-1) experimental; urgency=medium * New upstream release -- Jeremy Bicha Sun, 10 Mar 2019 12:59:34 -0400 pygobject (3.31.4-1) experimental; urgency=medium * New upstream release * Bump minimum glib to 2.48.0 -- Jeremy Bicha Fri, 08 Mar 2019 09:45:40 -0500 ** Changed in: pygobject (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: Fix Released Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.32.0-1 is in Debian experimental ready to be synced over once this FFe is approved. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820139] Re: [disco-proposed] What version of the gnome shell is correct?
The About page in the Settings app shows the overall GNOME version which isn't necessarily the same as the GNOME Shell version. The version number in the About page is provided by gnome-desktop3 which will be updated to 3.32.0 in the next several days. ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1820139 Title: [disco-proposed] What version of the gnome shell is correct? Status in gnome-shell package in Ubuntu: Invalid Bug description: Hi guys What version of the gnome shell is correct? See attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820143] Re: Package python-vte missing from Ubuntu 19.04
The removal of python-vte was intentional. It is part of an old vte version that hasn't been maintained for years. Please ask the developer of the app that needs python-vte to switch to GObject Introspection. The Debian package for the vte GObject Introspection support is gir1.2-vte-2.91 ** Package changed: ubuntu => vte (Ubuntu) ** Changed in: vte (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1820143 Title: Package python-vte missing from Ubuntu 19.04 Status in vte package in Ubuntu: Won't Fix Bug description: The python-vte package is missing from Ubuntu 19.04. Would you please add it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1820143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
On my end, I haven't been able to reproduce this so far with Ubuntu Appindicators disabled. It's very stable for me now. I am not 100% sure this is the fix for me, time will tell. But it's definitely more stable and possibly even fixed now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820135] Re: UI freeze exception to address three icon bugs
https://launchpad.net/ubuntu/+source/yaru-theme/19.04.2 ** Changed in: yaru-theme (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1820135 Title: UI freeze exception to address three icon bugs Status in yaru-theme package in Ubuntu: Fix Released Bug description: Following UI freeze, testing has discovered some icon bugs which could be fixed if an exception were granted. They are as follows. 1) Missing symlinks cause Gnome control centre to fall back to non- Yaru symbols for power settings and online accounts. The fallback symbols are thicker than the corresponding ones in Yaru and look out of place next to the others. https://github.com/ubuntu/yaru/issues/1259 describes the issue and https://github.com/ubuntu/yaru/pull/1262 fixes it by adding the missing symlinks (both with screenshots). 2) A background process puts a poorly rendered, pixellated Yaru icon on the launcher when it errors. The cause was determined to be a symlink. Removing this causes the process to fall back to a pre-Yaru icon which is properly rendered. The proposed fix at this stage is merely to remove the symlink, because an old icon rendered properly is better than a Yaru one with pixels. https://github.com/ubuntu/yaru/issues/1210 describes the issue and diagnosis (with screenshots) and https://github.com/ubuntu/yaru/pull/1267 fixes it. 3) A missing symlink causes Gnome Notes to use a non-Yaru icon when we have a Yaru icon for Notes. Adding the missing symlink would fix this. https://github.com/ubuntu/yaru/issues/1180#issuecomment-472493170 describes the problem with screenshot. All three issues could be fixed and fully tested with minimal risk simply by adding a small number of symlinks and removing one other. The benefit would be making the theme more polished in time for 19.04, rather than shipping it with three bugs that could be fixed. The changes have been tested by the Yaru team in branches of Yaru and the nature of these cosmetic changes makes them low risk. Because they're icon defects, they would otherwise be visible to all users of Ubuntu, and fixing them would have a good ratio of risk to benefit IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1820135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820767] Re: GNOME 3.32 icon name changes
Launchpad expects a space between the LP: and the # So I'm manually closing. https://launchpad.net/ubuntu/+source/yaru-theme/19.04.2 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1820767 Title: GNOME 3.32 icon name changes Status in yaru-theme package in Ubuntu: Fix Released Bug description: The following GNOME 3.32 app were released after UI Freeze (with no previous 3.31 releases) with a different app icon name. - preferences-desktop-font → org.gnome.font-viewer - gnome-characters → org.gnome.Characters - applets-screenshooter → org.gnome.Screenshot Except for gnome-screenshot, these releases also adapt to the new GNOME menu guidelines so I think we do need to do these updates. Without the proposed change, those applications will appear with GNOME upstream icons, instead of the Yaru ones, this is why I consider this a UI Freeze exception. This change is addressed adding new symlinks between the new and the old icon names, without removing the latters, so that the risk of regression issues is really low, if not zero - if any of the applications above should appear with the old icon name, the old symlink will provide the correct icon name - if any of the applications above should appear with an icon name different than the old or the new, upstream icon will be used anyway as it would be without this change Finally, the change has been tested installing the affected applications from [[https://launchpad.net/~jbicha/+archive/ubuntu/temp332/+packages|here]] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1820767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852540] Re: changed gmail password now cannot connect imap with thunderbird 60.9.0
This problem is really unexpected and has caused me a lot of grief. When I got a message from a identity protection service that my gmail account MAY have been compromised, I changed my gmail password. Then as soon as I tried to get mail via thunderbird, I got imap authentication errors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1852540 Title: changed gmail password now cannot connect imap with thunderbird 60.9.0 Status in thunderbird package in Ubuntu: New Bug description: this is a KNOWN problem as I have seen similar question on the Internet and it appears that something screwed up with Thunderbird in recent updates with their OAuth2 authentication method code. I am running Thunderbird 60.9.0 which appears to be the latest available for Ubuntu (Kubuntu) 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1852540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp