[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Exactly the same problem with Samsung Notebook 9 Pro (np930mbe-k04us) which also has an ALC298. Headphones are working with model=mono-speakers. I attached my Realtek dump. I'm also soliciting the arch forum for help (I'm running arch): https://bbs.archlinux.org/viewtopic.php?pid=1897858 ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5353056/+files/RtHDDump.txt -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Inst
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
I attached the Realtek dump with my headphones plugged into the jack for comparison. ** Attachment added: "RtHDDump.txt.headphonesInJack" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5353097/+files/RtHDDump.txt.headphonesInJack -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Can't switch to HSP profile with my Aftershokz. Says: "Failed to change profile to headset_head_unit" -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
Same problem on Ubuntu 19.10 on HP 250 G7. Tried editing logind.conf as per previous suggestions, but no combination solved the problem. Tried installing pm-utils, which weren't installed (see #117), that didn't help either. Tried turning off the automatic suspend and automatic blank screen in the Power settings, thinking that they might for whatever reason be interfering; no success. Tried uncommenting InhibitDelayMaxSec, HoldoffTimeoutSec and LidSwitchIgnoreInhibited (with both 'yes' and 'no'), none of those did it. Closing the lid only blanks the screen (fans are running), even if I leave it for some time. Opening the lid turns the screen back on, but doesn't open up the login screen. Besides the unsuccessful editing of logind.conf, the only other concurrent issue that I haven't found anyone else encountering, is that, in my case, closing the lid and then opening it also turns on Airplane mode, and then the next time I close it and open it, it turns the Airplane mode off. As I often need a quick suspend, as a temporary workaround, I set it up so that the physical power button suspends it. This works as intended, without any problems, so instead of having to close the lid, I have to press the button, then close the lid. It's better than having to open the top right menu, press Alt and click suspend, then close the lid, every time, but I'd still like to solve the problem properly... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in pm-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) 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: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+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 998602] Re: Radio kill function key needs to remember and honor the state from last shutdown
Same behavior as originally reported, even with a USB startup disk I created using 12.04 ISO image. Steps followed this time: 1) boot with startup disk -> Try Ubuntu. 2) configure WiFi. /var/lib/rfkill/saved-state was not yet created. Disable all radio using RF kill function key on physical keyboard. 3) reboot, once again select Try Ubuntu. Unity shell shows WiFi icon as disabled in the notification area. /var/lib/rfkill/saved-state was found with following contents $ cat /var/lib/rfkill/saved-state dell-wifi 1 dell-bluetooth 1 phy0 1 hci0 0 4) now press radio kill function key once again that was used in step 2 above. Expect that WiFi is now enabled; it is NOT. Press the key once again. This time, WiFi is enabled that was configured in step 2 above. Contents of /var/lib/rfkill/saved-state are still the same, assuming they will be written to during shut-down to reflect transition from 1 to 0. This is how it has ALWAYS worked for me: both before and with 12.04. So, looks like while the /etc/init based mechanism seems to write the state, the mechanism that is supposed to honor that is not working. Is it working on your PC? I will be surprised. -- 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/998602 Title: Radio kill function key needs to remember and honor the state from last shutdown Status in “network-manager” package in Ubuntu: Incomplete Bug description: If all radio (WiFi, Bluetooth, etc.) were disabled using Fn+ combination at the time of last shutdown, a subsequent restart correctly renders all the radios in switched off state: WiFi is disabled, Bluetooth and WiFi UI shows them as disabled. 'ifconfig' does not show WLAN entry. However, pressing the same key combination in expectation of enabling the radios does not enable. Only after pressing the key combination for the second time enables radios. It appears as if at the time of the first press after a reboot, the state is assumed to be enabled. Also, upon reboot with radios disabled and before they are enabled again, external Bluetooth devices are found to be working fine with the PC! Pointer for a Bluetooth mouse moves and clicks happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/998602/+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 996900] [NEW] Disabled wireless network cannot be re-enabled from 'Wireless Networks' UI
Public bug reported: In the top right corner, click on the icon for wireless networks. From the drop-down menu shown, click on 'Enable wireless' to disable it. You will notice that this disables Bluetooth as well. This is unexpected as Bluetooth has a separate UI for enabling or disabling it. This is troublesome for the following use case: 1) initially both Bluetooth and WiFi (802.11) is enabled and working fine. 2) for some reason the user needs to keep Bluetooth enabled, say, for using a Bluetooth enabled moue, but wants to keep the wireless networking disabled. 3) due to this bug, when wireless networking is disabled, the Bluetooth mouse is rendered useless until wireless networking is re-enabled. This erroneous behavior is equivalent of the 'radio-kill' switch found on laptops that disables all radios in one shot. The fact that there are different UI for disabling Bluetooth and WiFi indicates a different intent--that of providing more granular control. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.14-c2new x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 09:32:41 2012 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.11.14 dev wlan2 proto static 169.254.0.0/16 dev wlan2 scope link metric 1000 192.168.11.0/24 dev wlan2 proto kernel scope link src 192.168.11.15 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-05-05 (4 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Oarelahb b4ce06d6-8bf0-4f81-ac0b-8692127a9938 802-11-wireless 1332906797 Wednesday 28 March 2012 09:23:17 AM IST yes no /org/freedesktop/NetworkManager/Settings/2 Soham 68da02c3-d3f5-4946-adca-1b2af1cc722f 802-11-wireless 1336536138 Wednesday 09 May 2012 09:32:18 AM IST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan2 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/996900 Title: Disabled wireless network cannot be re-enabled from 'Wireless Networks' UI Status in “network-manager” package in Ubuntu: New Bug description: In the top right corner, click on the icon for wireless networks. From the drop-down menu shown, click on 'Enable wireless' to disable it. You will notice that this disables Bluetooth as well. This is unexpected as Bluetooth has a separate UI for enabling or disabling it. This is troublesome for the following use case: 1) initially both Bluetooth and WiFi (802.11) is enabled and working fine. 2) for some reason the user needs to keep Bluetooth enabled, say, for using a Bluetooth enabled moue, but wants to keep the wireless networking disabled. 3) due to this bug, when wireless networking is disabled, the Bluetooth mouse is rendered useless until wireless networking is re-enabled. This erroneous behavior is equivalent of the 'radio-kill' switch found on laptops that disables all radios in one shot. The fact that there are different UI for disabling Bluetooth and WiFi indicates a different intent--that of providing more granular control. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.14-c2new x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 09:32:41 2012 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.11.14 dev wlan2 proto static 169.254.0.0/16 dev wlan2 scope link metric 1000 192.168.11.0/24 dev wlan2 proto kernel scope link src 192.168.11.15 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true W
[Desktop-packages] [Bug 996900] Re: Disabling wireless from 'Wireless Networks' UI also disables Bluetooth
-- 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/996900 Title: Disabled wireless network cannot be re-enabled from 'Wireless Networks' UI Status in “network-manager” package in Ubuntu: New Bug description: In the top right corner, click on the icon for wireless networks. From the drop-down menu shown, click on 'Enable wireless' to disable it. You will notice that this disables Bluetooth as well. This is unexpected as Bluetooth has a separate UI for enabling or disabling it. This is troublesome for the following use case: 1) initially both Bluetooth and WiFi (802.11) is enabled and working fine. 2) for some reason the user needs to keep Bluetooth enabled, say, for using a Bluetooth enabled moue, but wants to keep the wireless networking disabled. 3) due to this bug, when wireless networking is disabled, the Bluetooth mouse is rendered useless until wireless networking is re-enabled. This erroneous behavior is equivalent of the 'radio-kill' switch found on laptops that disables all radios in one shot. The fact that there are different UI for disabling Bluetooth and WiFi indicates a different intent--that of providing more granular control. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.14-c2new x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 09:32:41 2012 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.11.14 dev wlan2 proto static 169.254.0.0/16 dev wlan2 scope link metric 1000 192.168.11.0/24 dev wlan2 proto kernel scope link src 192.168.11.15 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-05-05 (4 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Oarelahb b4ce06d6-8bf0-4f81-ac0b-8692127a9938 802-11-wireless 1332906797 Wednesday 28 March 2012 09:23:17 AM IST yes no /org/freedesktop/NetworkManager/Settings/2 Soham 68da02c3-d3f5-4946-adca-1b2af1cc722f 802-11-wireless 1336536138 Wednesday 09 May 2012 09:32:18 AM IST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan2 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/996900/+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 996900] Re: Disabled wireless network cannot be re-enabled from 'Wireless Networks' UI
** Summary changed: - Disabling wireless from 'Wireless Networks' UI also disables Bluetooth + Disabled wireless network cannot be re-enabled from 'Wireless Networks' UI -- 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/996900 Title: Disabled wireless network cannot be re-enabled from 'Wireless Networks' UI Status in “network-manager” package in Ubuntu: New Bug description: In the top right corner, click on the icon for wireless networks. From the drop-down menu shown, click on 'Enable wireless' to disable it. You will notice that this disables Bluetooth as well. This is unexpected as Bluetooth has a separate UI for enabling or disabling it. This is troublesome for the following use case: 1) initially both Bluetooth and WiFi (802.11) is enabled and working fine. 2) for some reason the user needs to keep Bluetooth enabled, say, for using a Bluetooth enabled moue, but wants to keep the wireless networking disabled. 3) due to this bug, when wireless networking is disabled, the Bluetooth mouse is rendered useless until wireless networking is re-enabled. This erroneous behavior is equivalent of the 'radio-kill' switch found on laptops that disables all radios in one shot. The fact that there are different UI for disabling Bluetooth and WiFi indicates a different intent--that of providing more granular control. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.14-c2new x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 09:32:41 2012 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.11.14 dev wlan2 proto static 169.254.0.0/16 dev wlan2 scope link metric 1000 192.168.11.0/24 dev wlan2 proto kernel scope link src 192.168.11.15 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-05-05 (4 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Oarelahb b4ce06d6-8bf0-4f81-ac0b-8692127a9938 802-11-wireless 1332906797 Wednesday 28 March 2012 09:23:17 AM IST yes no /org/freedesktop/NetworkManager/Settings/2 Soham 68da02c3-d3f5-4946-adca-1b2af1cc722f 802-11-wireless 1336536138 Wednesday 09 May 2012 09:32:18 AM IST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan2 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/996900/+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 996900] Re: Disabled wireless network cannot be re-enabled from 'Wireless Networks' UI
The bug originally reported as above cannot be recreated with the latest updates to 12.04. It was observed immediately after upgrading from 11.10. Means, disabling WiFi does not disable Bluetooth. Now I see some different issues and hence changed the bug summary/ title. 1) A previously disabled WiFi does not get enabled when 'Enable wireless' is selected from the drop-down UI menu. UI shows 'Wireless is disabled' 2) Press the hardware buttons to switch off radios. This shows both Bluetooth and WiFi as disabled in the UI. However, Bluetooth mouse continues working fine. 3) Enabling radios using hardware switch now enables both Bluetooth and WiFi. ** Visibility changed to: Private ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/996900/+attachment/3137852/+files/IpAddr.txt ** Attachment removed: "NetDevice.wlan2.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/996900/+attachment/3137855/+files/NetDevice.wlan2.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/996900/+attachment/3137860/+files/WifiSyslog.txt -- 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/996900 Title: Disabled wireless network cannot be re-enabled from 'Wireless Networks' UI Status in “network-manager” package in Ubuntu: New Bug description: In the top right corner, click on the icon for wireless networks. From the drop-down menu shown, click on 'Enable wireless' to disable it. You will notice that this disables Bluetooth as well. This is unexpected as Bluetooth has a separate UI for enabling or disabling it. This is troublesome for the following use case: 1) initially both Bluetooth and WiFi (802.11) is enabled and working fine. 2) for some reason the user needs to keep Bluetooth enabled, say, for using a Bluetooth enabled moue, but wants to keep the wireless networking disabled. 3) due to this bug, when wireless networking is disabled, the Bluetooth mouse is rendered useless until wireless networking is re-enabled. This erroneous behavior is equivalent of the 'radio-kill' switch found on laptops that disables all radios in one shot. The fact that there are different UI for disabling Bluetooth and WiFi indicates a different intent--that of providing more granular control. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.14-c2new x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 09:32:41 2012 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.11.14 dev wlan2 proto static 169.254.0.0/16 dev wlan2 scope link metric 1000 192.168.11.0/24 dev wlan2 proto kernel scope link src 192.168.11.15 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-05-05 (4 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Oarelahb b4ce06d6-8bf0-4f81-ac0b-8692127a9938 802-11-wireless 1332906797 Wednesday 28 March 2012 09:23:17 AM IST yes no /org/freedesktop/NetworkManager/Settings/2 Soham 68da02c3-d3f5-4946-adca-1b2af1cc722f 802-11-wireless 1336536138 Wednesday 09 May 2012 09:32:18 AM IST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan2 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/996900/+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 998602] [NEW] Radio kill function key needs to remember and honor the state from last shutdown
Public bug reported: If all radio (WiFi, Bluetooth, etc.) were disabled using Fn+ combination at the time of last shutdown, a subsequent restart correctly renders all the radios in switched off state: WiFi is disabled, Bluetooth and WiFi UI shows them as disabled. 'ifconfig' does not show WLAN entry. However, pressing the same key combination in expectation of enabling the radios does not enable. Only after pressing the key combination for the second time enables radios. It appears as if at the time of the first press after a reboot, the state is assumed to be enabled. Also, upon reboot with radios disabled and before they are enabled again, external Bluetooth devices are found to be working fine with the PC! Pointer for a Bluetooth mouse moves and clicks happen. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Description changed: If all radio (WiFi, Bluetooth, etc.) were disabled using Fn+ combination at the time of last shutdown, a subsequent restart correctly - renders all the radios in switched off state. However, pressing the same - key combination in expectation of enabling the radios does not enable. - Only after pressing the key combination for the second time enables - radios. It appears as if at the time of the first press after a reboot, - the state is assumed to be enabled. + renders all the radios in switched off state: WiFi is disabled, + Bluetooth and WiFi UI shows them as disabled. 'ifconfig' does not show + WLAN entry. However, pressing the same key combination in expectation of + enabling the radios does not enable. Only after pressing the key + combination for the second time enables radios. It appears as if at the + time of the first press after a reboot, the state is assumed to be + enabled. Also, upon reboot with radios disabled and before they are enabled again, external Bluetooth devices are found to be working fine with the PC! Pointer for a Bluetooth mouse moves and clicks happen. -- 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/998602 Title: Radio kill function key needs to remember and honor the state from last shutdown Status in “network-manager-applet” package in Ubuntu: New Bug description: If all radio (WiFi, Bluetooth, etc.) were disabled using Fn+ combination at the time of last shutdown, a subsequent restart correctly renders all the radios in switched off state: WiFi is disabled, Bluetooth and WiFi UI shows them as disabled. 'ifconfig' does not show WLAN entry. However, pressing the same key combination in expectation of enabling the radios does not enable. Only after pressing the key combination for the second time enables radios. It appears as if at the time of the first press after a reboot, the state is assumed to be enabled. Also, upon reboot with radios disabled and before they are enabled again, external Bluetooth devices are found to be working fine with the PC! Pointer for a Bluetooth mouse moves and clicks happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/998602/+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 999418] [NEW] Bluetooth and WiFi remain disabled after reboot from Windows
Public bug reported: On Dell N4110 laptop, if you first boot into Windows and then reboot into Ubuntu, Bluetooth and WiFi remain disabled. Only disabling and then re-enabling radios using hardware function key combination enables it. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/999418 Title: Bluetooth and WiFi remain disabled after reboot from Windows Status in “network-manager” package in Ubuntu: New Bug description: On Dell N4110 laptop, if you first boot into Windows and then reboot into Ubuntu, Bluetooth and WiFi remain disabled. Only disabling and then re-enabling radios using hardware function key combination enables it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/999418/+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 999418] Re: Bluetooth and Wi-Fi interfaces are disabled after reboot from Windows; using hotkey to disable and enable the radios fixes it
Intel® Centrino® Wireless-N 1030 (1x2 bgn + Bluetooth) http://www.dell.com/us/p/inspiron-14r-n4110/pd#readMore $ lsmod|grep -i bluetoo bluetooth 164474 29 hidp,rfcomm,bnep,ath3k,btusb $ lsmod|grep -i 802 mac80211 269511 1 ath9k cfg80211 204001 3 ath9k,mac80211,ath Subsequent to the original bug report, later drivers get WiFi up and running fine. Bluetooth still needs to be disabled-reenabled using Fn+F2 hotkeys. Same the other way round: when first powered on and booted into Ubuntu, and then reboot in Windows 7. The experience is worse. Bluetooth has to be disabled and re-enabled multiple times before it behaves. Till then it keeps kicking out already attached and working Bluetooth devices. -- 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/999418 Title: Bluetooth and Wi-Fi interfaces are disabled after reboot from Windows; using hotkey to disable and enable the radios fixes it Status in “network-manager” package in Ubuntu: Incomplete Bug description: On Dell N4110 laptop, if you first boot into Windows and then reboot into Ubuntu, Bluetooth and WiFi remain disabled. Only disabling and then re-enabling radios using hardware function key combination enables it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/999418/+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 492959] Re: Evince cannot save filled PDF forms
Same problem here (using evince on debian), version 3.4.0-3.1, together with poppler/cairo 0.18.4 Please fix this. I spent three hours filling in a form, and now have to note it down *again* into another program. A button called "Save As" really should *always* work. If some data would be lost, warn, but don't prevent the user from saving his work. Notmyrealname (nichmeinechtername) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/492959 Title: Evince cannot save filled PDF forms Status in Evince document viewer: Confirmed Status in “evince” package in Ubuntu: Confirmed Bug description: Binary package hint: evince Whenever I open a PDF form, and make a change to it (any change, such as filling a field), and then try to save a copy on Evince, the resulting file is empty. Not as in empty fields, but as in zero-bytes-long file. However, when trying to save a copy before any changes have been made, it works fine. This is not the same as bug 299409, since in that bug the resulting files are not empty. The particular form I'm trying to fill is http://www.box.net/shared/static/ia8aliz8ne.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/492959/+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 881485] Re: Column Table Widths don't persist
The problem is still present when saving with Libre Office docx format. The problem goes away if I change the table width to "relative" (a percentage of page width) instead of using absolute values (which seem to be the default). -- 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/881485 Title: Column Table Widths don't persist Status in “libreoffice” package in Ubuntu: New Bug description: Make a 3 column table, save in Microsoft 2007 .docx format. When you reopen the document, column widths get screwed up sometimes. (I can't figure out exactly when, but it is a pain in the ars.) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 25 08:25:35 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash 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/881485/+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 881485] [NEW] Column Table Widths don't persist
Public bug reported: Make a 3 column table, save in Microsoft 2007 .docx format. When you reopen the document, column widths get screwed up sometimes. (I can't figure out exactly when, but it is a pain in the ars.) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 25 08:25:35 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi natty -- 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/881485 Title: Column Table Widths don't persist Status in “libreoffice” package in Ubuntu: New Bug description: Make a 3 column table, save in Microsoft 2007 .docx format. When you reopen the document, column widths get screwed up sometimes. (I can't figure out exactly when, but it is a pain in the ars.) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 25 08:25:35 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash 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/881485/+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 881485] Re: Column Table Widths don't persist
Even when column width is set to 100% the problem returns, and the table selection automatically goes back to normal (not relative.) 99% seems to work fine though and the setting persists as expected. In the problem documents, the tables also sometimes left align themselves outside the specified margin. When I manually move that left line to inside the margin, save and reload, the problem returns again (column width "set relative" is automatically unchecked, and the width become huge sending the table off the right side of the page. -- 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/881485 Title: Column Table Widths don't persist Status in “libreoffice” package in Ubuntu: New Bug description: Make a 3 column table, save in Microsoft 2007 .docx format. When you reopen the document, column widths get screwed up sometimes. (I can't figure out exactly when, but it is a pain in the ars.) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 25 08:25:35 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash 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/881485/+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 881485] Re: Column Table Widths don't persist
-- 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/881485 Title: Column Table Widths don't persist Status in “libreoffice” package in Ubuntu: New Bug description: Make a 3 column table, save in Microsoft 2007 .docx format. When you reopen the document, column widths get screwed up sometimes. (I can't figure out exactly when, but it is a pain in the ars.) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 25 08:25:35 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash 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/881485/+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 881485] Re: Column Table Widths don't persist
This attached document seems to work fine in odt format, but when saved to docx, several things seem to happen: - column width is no longer relative, but static numbers - the column width numbers are very large (like 13" plus) which causes the table to go off the right of the page. When you open in docx format, you can fix them in the document, but when you save again, this get screwy again. Something seems to be wrong with how column widths are saved/stored in the docx format. ** Attachment added: "17_Mike_DefendantsCROSS_TerryGlenn.odt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/881485/+attachment/2572054/+files/17_Mike_DefendantsCROSS_TerryGlenn.odt -- 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/881485 Title: Column Table Widths don't persist Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Make a 3 column table, save in Microsoft 2007 .docx format. When you reopen the document, column widths get screwed up sometimes. (I can't figure out exactly when, but it is a pain in the ars.) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 25 08:25:35 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash 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/881485/+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 882304] Re: docx conversion fails
I mean save it in .odt format. . . Office will save it and everything seems OK, but if you try to open the saved .odt file it just fails. -- 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/882304 Title: docx conversion fails Status in “libreoffice” package in Ubuntu: New Bug description: I have a docx file from Apple Office I think. It opens fine and converts, however if I save this file in .odt format, it saves, but will NOT open again. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Oct 26 15:10:29 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash 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/882304/+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 882304] [NEW] docx conversion fails
Public bug reported: I have a docx file from Apple Office I think. It opens fine and converts, however if I save this file in .odt format, it saves, but will NOT open again. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Oct 26 15:10:29 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi natty -- 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/882304 Title: docx conversion fails Status in “libreoffice” package in Ubuntu: New Bug description: I have a docx file from Apple Office I think. It opens fine and converts, however if I save this file in .odt format, it saves, but will NOT open again. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Oct 26 15:10:29 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash 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/882304/+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 882304] Re: docx conversion fails
-- 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/882304 Title: docx conversion fails Status in “libreoffice” package in Ubuntu: New Bug description: I have a docx file from Apple Office I think. It opens fine and converts, however if I save this file in .odt format, it saves, but will NOT open again. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Oct 26 15:10:29 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash 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/882304/+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 882304] Re: docx conversion fails
This attachment is the document. LibreOffice will open it, and save it, but the resulting file cannot be read. ** Attachment added: "16_Ricky_DefenseCross_ChrisJensen.docx" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/882304/+attachment/2574496/+files/16_Ricky_DefenseCross_ChrisJensen.docx -- 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/882304 Title: docx conversion fails Status in “libreoffice” package in Ubuntu: New Bug description: I have a docx file from Apple Office I think. It opens fine and converts, however if I save this file in .odt format, it saves, but will NOT open again. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Oct 26 15:10:29 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash 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/882304/+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 1310996] [NEW] SUPER+D shortcut minimize windows
Public bug reported: Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Same crap with the shortcut keys as in 12.04. SUPER keys don't work, neither does CTRL+SHIFT+SPACE and neither does CTRL+ALT+*. Did you take an Ubuntu version from three years ago and develop from that? Fuck this ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1310996 Title: SUPER+D shortcut minimize windows Status in “unity” package in Ubuntu: New Bug description: Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Same crap with the shortcut keys as in 12.04. SUPER keys don't work, neither does CTRL+SHIFT+SPACE and neither does CTRL+ALT+*. Did you take an Ubuntu version from three years ago and develop from that? Fuck this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1310996/+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 1247221] Re: Nautilus doesn't remember setting for showing hidden files correctly when org.gtk.Settings.FileChooser show-hidden is true
Not surprisingly, this bug made it to 14.04 final release. Congratulations, Ubuntu team. -- 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/1247221 Title: Nautilus doesn't remember setting for showing hidden files correctly when org.gtk.Settings.FileChooser show-hidden is true Status in Nautilus: New Status in “nautilus” package in Ubuntu: Triaged Bug description: Description: Ubuntu 13.10 Release: 13.10 nautilus: 1:3.8.2-0ubuntu2 The default setting of not showing hidden files can be changed with strg+h. After all windows are closed nautilus remembers to show hidden files again when opening a new window. If strg+h is pressed again to hide hidden files nautilus does so but still keeps showing hidden files in new windows. When changed via gui the setting is remembered correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1247221/+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 1312735] [NEW] Nautilus asks for SSH login, even when it authenticates with a key file
Public bug reported: Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 14.04 When there's a valid key file for authentication over SSH/SFTP, Nautilus first asks for the server login, but then proceeds to log in using the key file. It should probably be the other way around. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Description changed: + Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux + Ubuntu 14.04 + When there's a valid key file for authentication over SSH/SFTP, Nautilus first asks for the server login, but then proceeds to log in using the key file. It should probably be the other way around. -- 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/1312735 Title: Nautilus asks for SSH login, even when it authenticates with a key file Status in “nautilus” package in Ubuntu: New Bug description: Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 14.04 When there's a valid key file for authentication over SSH/SFTP, Nautilus first asks for the server login, but then proceeds to log in using the key file. It should probably be the other way around. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1312735/+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 1313805] [NEW] Nautilus doesn't show file names when too many columns are displayed
Public bug reported: When too many columns are displayed and you search for a file in Nautilus, the file names will be completely hidden and the other columns take precedence. It's also not possible to resize columns... Here's a screenshot: http://imgur.com/6Of8vHE ** 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/1313805 Title: Nautilus doesn't show file names when too many columns are displayed Status in “nautilus” package in Ubuntu: New Bug description: When too many columns are displayed and you search for a file in Nautilus, the file names will be completely hidden and the other columns take precedence. It's also not possible to resize columns... Here's a screenshot: http://imgur.com/6Of8vHE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1313805/+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 1314072] [NEW] EyeOfGnome scales images wrong
Public bug reported: Ubuntu 14.04 Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux For some images, EyeOfGnome says they are at 100% size, but they are actually scaled down and blurry. Example: http://imgur.com/6Of8vHE Download that image and view it in EOG. Even when there is enough screen space to view the image at 100%, it will be scaled down a little bit despite saying it's at 100%. ** Affects: eog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1314072 Title: EyeOfGnome scales images wrong Status in “eog” package in Ubuntu: New Bug description: Ubuntu 14.04 Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux For some images, EyeOfGnome says they are at 100% size, but they are actually scaled down and blurry. Example: http://imgur.com/6Of8vHE Download that image and view it in EOG. Even when there is enough screen space to view the image at 100%, it will be scaled down a little bit despite saying it's at 100%. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1314072/+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 1283938] Re: Ubuntu 14.04 blank screen after wakeup from sleep
Same problem on a Lenovo Thinkpad T420s with an install of 64bit Xubuntu 14.04. After suspending and unsuspending, I get a password prompt. After successfully authenticating, the screen goes black. $ lshw ... *-display description: VGA compatible controller product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:49 memory:f000-f03f memory:e000-efff ioport:4000(size=64) ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: Ubuntu 14.04 blank screen after wakeup from sleep Status in “linux-lts-trusty” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Hardware: Samsung Serie 5 AMD notebook (find in attachment the hardware profile). OS: Ubuntu 14.04 (updated today). After wakeup the notebook from the sleep mode, the screen goes blank while the OS and the hardware is awake. (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system). This problem is not happening with the AMD property drivers (but they have another bug, i can't set up the brighness of the monitor). The problem in my opinion is related to this package: xserver-xorg- video-ati. Changing "quiet splash" with "nomodeset" into /etc/default/grub makes the wakeup working, but the pc is really slow (can't be used), also after the normal start up. Best regards and have a good work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 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: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 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 x
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
The bug was already fixed in 12.04, now the same problems resurface again. I'm holding back several computers from upgrading to 14.04 and looking for an alternate distribution because of this, amongst other issues. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Fedora: Unknown Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - holding left shift, press and release ctrl -> the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t -> gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) * Please add ability to set keyboard shortcuts to unity-control-center launched from
[Desktop-packages] [Bug 1283938] Re: Ubuntu 14.04 blank screen after wakeup from sleep
Same problem on a Lenovo X60 laptop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: Ubuntu 14.04 blank screen after wakeup from sleep Status in “linux-lts-trusty” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Hardware: Samsung Serie 5 AMD notebook (find in attachment the hardware profile). OS: Ubuntu 14.04 (updated today). After wakeup the notebook from the sleep mode, the screen goes blank while the OS and the hardware is awake. (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system). This problem is not happening with the AMD property drivers (but they have another bug, i can't set up the brighness of the monitor). The problem in my opinion is related to this package: xserver-xorg- video-ati. Changing "quiet splash" with "nomodeset" into /etc/default/grub makes the wakeup working, but the pc is really slow (can't be used), also after the normal start up. Best regards and have a good work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 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: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 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: Mon Feb 24 12:54:54 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1283938/+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 1015240] Re: EOG window doen't raise when opening an image that's already open
This bug is still in 14.04. There is no progress in Ubuntu it seems. Same bugs for years... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1015240 Title: EOG window doen't raise when opening an image that's already open Status in “eog” package in Ubuntu: Confirmed Bug description: 1. Open a folder in Nautilus with images in it 2. Double click an image to open it in EOG 3. Put another window on top of the EOG window 4. In Nautilus, double-click the same image file Note that EOG did not raise. This is contrast to most (all?) apps in Ubuntu -- for example, if you try the corresponding steps in Firefox or Gedit, both will raise the corresponding window. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: eog 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jun 19 11:50:35 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1015240/+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 1320872] [NEW] Firefox doesn't play h264/MP4 videos
Public bug reported: Linux ubuntu 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Firefox 29 Tried with a new profile, same result. Works in Chromium. You can test it here: http://www.quirksmode.org/html5/tests/video.html ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1320872 Title: Firefox doesn't play h264/MP4 videos Status in “firefox” package in Ubuntu: New Bug description: Linux ubuntu 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Firefox 29 Tried with a new profile, same result. Works in Chromium. You can test it here: http://www.quirksmode.org/html5/tests/video.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1320872/+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 1280905] Re: firefox on ubuntu 14.04 does not play mp4 files
Three months now. HTML5 video support is not exactly unimportant and this should be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1280905 Title: firefox on ubuntu 14.04 does not play mp4 files Status in “firefox” package in Ubuntu: Confirmed Bug description: On xubuntu 14.04 the package gstreamer0.10-ffmpeg_0.10.13-5_amd64.deb is not available, so I could not use mp4 h264 files in html5 tags. I used the .deb package from ubuntu 13.10 and after an apt-get -f install everything works fine. I don't know why the gstreamer0.10-ffmpeg package is not available anymore, it looks like firefox could use gstreamer1.0-libav. I don't know if the h264 decoder is enabled in gstreamer1.0-libav package. I hope that this bug report will help people get html5 video working. Tested with firefox 25 and 29. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1280905/+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 1323212] [NEW] sFTP very slow to connect and causes Nautilus to randomly freeze
Public bug reported: Linux ubuntu 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 14.04 Problems with Nautilus and smbd. Nautilus takes minutes to connect to sFTP servers and once connected, it randomly freezes (window turns dark and doesn't respond for 30-60 seconds). This happens often, but not only, after a time of inactivity. Other software using sFTP, like text editors with sFTP support, are also affected. The auth log is spammed with May 23 18:17:52 ubuntu smbd[20649]: pam_unix(samba:session): session closed for user nobody May 23 18:18:34 ubuntu smbd[20677]: pam_unix(samba:session): session closed for user nobody May 23 18:18:51 ubuntu smbd[20686]: pam_unix(samba:session): session closed for user nobody May 23 18:18:51 ubuntu smbd[20688]: pam_unix(samba:session): session closed for user nobody May 23 18:18:56 ubuntu smbd[20703]: pam_unix(samba:session): session closed for user nobody May 23 18:19:34 ubuntu smbd[20724]: pam_unix(samba:session): session closed for user nobody May 23 18:19:39 ubuntu smbd[20766]: pam_unix(samba:session): session closed for user nobody May 23 18:19:55 ubuntu smbd[20823]: pam_unix(samba:session): session closed for user nobody May 23 18:20:20 ubuntu smbd[20853]: pam_unix(samba:session): session closed for user nobody May 23 18:21:33 ubuntu smbd[20878]: pam_unix(samba:session): session closed for user nobody May 23 18:21:50 ubuntu smbd[20883]: pam_unix(samba:session): session closed for user nobody May 23 18:21:51 ubuntu smbd[20885]: pam_unix(samba:session): session closed for user nobody May 23 18:21:56 ubuntu smbd[20887]: pam_unix(samba:session): session closed for user nobody May 23 18:21:57 ubuntu smbd[20888]: pam_unix(samba:session): session closed for user nobody May 23 18:22:34 ubuntu smbd[20930]: pam_unix(samba:session): session closed for user nobody May 23 18:22:36 ubuntu smbd[20932]: pam_unix(samba:session): session closed for user nobody May 23 18:23:18 ubuntu smbd[20942]: pam_unix(samba:session): session closed for user nobody May 23 18:23:19 ubuntu smbd[20943]: pam_unix(samba:session): session closed for user nobody May 23 18:23:19 ubuntu smbd[20944]: pam_unix(samba:session): session closed for user nobody May 23 18:23:19 ubuntu smbd[20945]: pam_unix(samba:session): session closed for user nobody May 23 18:23:38 ubuntu smbd[20970]: pam_unix(samba:session): session closed for user nobody so I guess at least part of the problem are the frequent disconnects, which are not network related. It's both a problem with smbd and Nautilus however, because Nautilus should handle the disconnects better and not freeze all the time. Connecting via SSH through CLI is instant and doesn't cause any problems whatsoever, so again, it's not a network problem. I have installed Ubuntu 14.04 on several machines and they all have the same problems. If the problems persist, I will have to look for an alternative, as it's impossible to work like this. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Description changed: Linux ubuntu 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 14.04 Problems with Nautilus and smbd. Nautilus takes minutes to connect to sFTP servers and once connected, it randomly freezes (window turns dark and doesn't respond for 30-60 seconds). This happens often, but not only, after a time of inactivity. Other software using sFTP, like text editors with sFTP support, are also affected. The auth log is spammed with May 23 18:17:52 ubuntu smbd[20649]: pam_unix(samba:session): session closed for user nobody May 23 18:18:34 ubuntu smbd[20677]: pam_unix(samba:session): session closed for user nobody May 23 18:18:51 ubuntu smbd[20686]: pam_unix(samba:session): session closed for user nobody May 23 18:18:51 ubuntu smbd[20688]: pam_unix(samba:session): session closed for user nobody May 23 18:18:56 ubuntu smbd[20703]: pam_unix(samba:session): session closed for user nobody May 23 18:19:34 ubuntu smbd[20724]: pam_unix(samba:session): session closed for user nobody May 23 18:19:39 ubuntu smbd[20766]: pam_unix(samba:session): session closed for user nobody May 23 18:19:55 ubuntu smbd[20823]: pam_unix(samba:session): session closed for user nobody May 23 18:20:20 ubuntu smbd[20853]: pam_unix(samba:session): session closed for user nobody May 23 18:21:33 ubuntu smbd[20878]: pam_unix(samba:session): session closed for user nobody May 23 18:21:50 ubuntu smbd[20883]: pam_unix(samba:session): session closed for user nobody May 23 18:21:51 ubuntu smbd[20885]: pam_unix(samba:session): session closed for user nobody May 23 18:21:56 ubuntu smbd[20887]: pam_unix(samba:session): session closed for user nobody May 23 18:21:57 ubuntu smbd[20888]: pam_unix(samba:session): session closed for user nobody May 23 18:22:34 ubuntu smbd[20930]: pam_unix(samba
[Desktop-packages] [Bug 1323212] Re: sFTP very slow to connect and causes Nautilus to randomly freeze
I just installed the Dolphin file manager and everything works fine, so it looks like Nautilus really is causing the problems. -- 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/1323212 Title: sFTP very slow to connect and causes Nautilus to randomly freeze Status in “nautilus” package in Ubuntu: New Bug description: Linux ubuntu 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 14.04 Problems with Nautilus and smbd. Nautilus takes minutes to connect to sFTP servers and once connected, it randomly freezes (window turns dark and doesn't respond for 30-60 seconds). This happens often, but not only, after a time of inactivity. Other software using sFTP, like text editors with sFTP support, are also affected. The auth log is spammed with May 23 18:17:52 ubuntu smbd[20649]: pam_unix(samba:session): session closed for user nobody May 23 18:18:34 ubuntu smbd[20677]: pam_unix(samba:session): session closed for user nobody May 23 18:18:51 ubuntu smbd[20686]: pam_unix(samba:session): session closed for user nobody May 23 18:18:51 ubuntu smbd[20688]: pam_unix(samba:session): session closed for user nobody May 23 18:18:56 ubuntu smbd[20703]: pam_unix(samba:session): session closed for user nobody May 23 18:19:34 ubuntu smbd[20724]: pam_unix(samba:session): session closed for user nobody May 23 18:19:39 ubuntu smbd[20766]: pam_unix(samba:session): session closed for user nobody May 23 18:19:55 ubuntu smbd[20823]: pam_unix(samba:session): session closed for user nobody May 23 18:20:20 ubuntu smbd[20853]: pam_unix(samba:session): session closed for user nobody May 23 18:21:33 ubuntu smbd[20878]: pam_unix(samba:session): session closed for user nobody May 23 18:21:50 ubuntu smbd[20883]: pam_unix(samba:session): session closed for user nobody May 23 18:21:51 ubuntu smbd[20885]: pam_unix(samba:session): session closed for user nobody May 23 18:21:56 ubuntu smbd[20887]: pam_unix(samba:session): session closed for user nobody May 23 18:21:57 ubuntu smbd[20888]: pam_unix(samba:session): session closed for user nobody May 23 18:22:34 ubuntu smbd[20930]: pam_unix(samba:session): session closed for user nobody May 23 18:22:36 ubuntu smbd[20932]: pam_unix(samba:session): session closed for user nobody May 23 18:23:18 ubuntu smbd[20942]: pam_unix(samba:session): session closed for user nobody May 23 18:23:19 ubuntu smbd[20943]: pam_unix(samba:session): session closed for user nobody May 23 18:23:19 ubuntu smbd[20944]: pam_unix(samba:session): session closed for user nobody May 23 18:23:19 ubuntu smbd[20945]: pam_unix(samba:session): session closed for user nobody May 23 18:23:38 ubuntu smbd[20970]: pam_unix(samba:session): session closed for user nobody so I guess at least part of the problem are the frequent disconnects, which are not network related. It's both a problem with smbd and Nautilus however, because Nautilus should handle the disconnects better and not freeze all the time. Connecting via SSH through CLI is instant and doesn't cause any problems whatsoever, so again, it's not a network problem. I have installed Ubuntu 14.04 on several machines and they all have the same problems. If the problems persist, I will have to look for an alternative, as it's impossible to work like this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1323212/+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 1581535] Re: libnl upgrade breaks Network Manager
*** This bug is a duplicate of bug 1511735 *** https://bugs.launchpad.net/bugs/1511735 As Jon B mentions in comment #9 above, even I DO NOT have trusty- proposed enabled on my 14.04.1 with kernel 3.19.0-59-generic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1581535 Title: libnl upgrade breaks Network Manager Status in libnl3 package in Ubuntu: Invalid Status in libnl3 source package in Trusty: Confirmed Bug description: I appear to have been hit by a regression problem in the libnl update described here: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735 After running a regular software update this morning and rebooting, I've completely lost networking access. Network Manager is down. I'm running Trusty 14.04. I tried this workaround: http://askubuntu.com/questions/727127/last-upgrade-crashes-network- manager-no-internet-connection-no-applet ... and step 1 didn't work. I'll be trying step 2 tonight when I've got more time. I'm filing this as a new bug with a regression-update, as indicated in the above-linked bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581535/+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 1511735] Re: libnl: fail to bind() netlink sockets
It affect my 14.04.1 system WITHOUT trusty-proposed enabled. FYI: kernel 3.19.0-59-generic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: In Progress Status in libnl3 package in Debian: Fix Released Bug description: [Triage Notes] The proposed fix for this bug in libnl3 caused a regression in trusty- proposed, tracked in bug 1539634. The regression is caused by a latent bug in Network Manager. We expect to fix this by landing a fix for the bug in Network Manager in trusty-updates at the same time as this fix. [Impact] * Applications in Trusty using libnl-3-200 which frequently open and close netlink sockets can easily fail when attempting to bind the local socket. The problem happens when libnl choose a port id already used by another application and subsequently libnl fails instead of trying another port id. The original bug was discovered when attempting to start a virtual machine under libvirt, which is a user of this library. * Backporting fixes from upstream release fixes a real bug in the current version of the library in Trusty. The alternative is for all applications to manually manage their local port allocation, or as upstream has accepted allowing libnl to attempt to try for other local ports. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. [Test Case] * On a Trusty 14.04 system 1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \ libnl-genl-3-dev libnl-route-3-200 \ make gcc build-essential libnl1 2. download and unpack attachment: lp_1511735_test.tar 3. Run testcases: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 6975 (pid: 6974) local port has been set by the libnl to 6975 (pid: 6975) ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975) libnl FAILED % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=6978 TEST (a)... Traceback (most recent call last): File "libnl3-test-rh1249158.py", line 226, in locals()["TEST_" + arg]() File "libnl3-test-rh1249158.py", line 140, in TEST_a sk = nl_get_socket() File "libnl3-test-rh1249158.py", line 115, in nl_get_socket raise IOError(-err, _nl_geterror()) OSError: [Errno 6] b'Unspecific failure' 4. After applying the updated packages: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 11295 (pid: 11294) local port has been set by the libnl to 2894081055 (pid: 11295) libnl OK % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=11296 TEST (a)... ...done TEST (b)... ...done TEST (c)... ...done TEST (d)... ...done [Regression Potential] * There are quite a few high profile packages that depend on this package, notably libvirt and network-manager. The complete list is here: # on Trusty % apt-rdepends -r libnl-3-200 | head -n 33 libnl-3-200 Reverse Depends: batctl (>= 2013.4.0-2) Reverse Depends: bmon (>= 1:3.1-1) Reverse Depends: crda (>= 1.1.2-1ubuntu2) Reverse Depends: hostapd (>= 1:2.1-0ubuntu1) Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1) Reverse Depends: iw (>= 3.4-1) Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1) Reverse Depends: kismet (>= 2013.03.R1b-3) Reverse Depends: knemo (>= 0.7.6-2) Reverse Depends: libfsobasics3 (>= 0.12.0-4) Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1) Reverse Depends: libnl-3-200-dbg (= 3.2.21-1) Reverse Depends: libnl-3-dev (= 3.2.21-1) Reverse Depends: libnl-cli-3-200 (= 3.2.21-1) Reverse Depends: libnl-genl-3-200 (= 3.2.21-1) Reverse Depends: libnl-nf-3-200 (= 3.2.21-1) Reverse Depends: libnl-route-3-200 (= 3.2.21-1) Reverse Depends: libnl-utils (>= 3.2.21-1) Reverse Depends: libnss-gw-name (>= 0.3-2) Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13) Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13) Reverse Depends: lowpan-test-tools (>= 0.3-1) Reverse Depends: lowpan-tools (>= 0.3-1) Reverse Depends: neard (>= 0.11-1) Reverse Depends: neard-tools (>= 0.11-1) Reverse Depends:
[Desktop-packages] [Bug 2029173] Re: fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': No such file or directory
The error is unchanged with Kubuntu 23.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2029173 Title: fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa- mesa3d.bc': No such file or directory Status in mesa package in Ubuntu: New Bug description: Programs using OpenCL report the following bug: fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': No such file or directory This bug is encountered when trying to run github.com/ggerganov/llama.cpp build with CLBlast or just using clinfo. The hardware is an AMD Radeon RX 6700 XT lsb_release -rd: No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 apt-cache policy mesa-opencl-icd #although I am not sure that this is the offending package mesa-opencl-icd: Installed: 23.0.4-0ubuntu1~23.04.1 Candidate: 23.0.4-0ubuntu1~23.04.1 Version table: *** 23.0.4-0ubuntu1~23.04.1 500 500 http://de.archive.ubuntu.com/ubuntu lunar-updates/universe amd64 Packages 100 /var/lib/dpkg/status 23.0.2-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages pc@pc-MS-7C02:~/ML/llama.cpp$ clinfo output: Number of platforms 2 Platform Name Clover Platform Vendor Mesa Platform VersionOpenCL 1.1 Mesa 23.0.4-0ubuntu1~23.04.1 Platform ProfileFULL_PROFILE Platform Extensions cl_khr_icd Platform Extensions function suffix MESA Platform Name rusticl Platform Vendor Mesa/X.org Platform VersionOpenCL 3.0 Platform ProfileFULL_PROFILE Platform Extensions cl_khr_icd Platform Extensions with Versioncl_khr_icd 0x40 (1.0.0) Platform Numeric Version0xc0 (3.0.0) Platform Extensions function suffix MESA Platform Host timer resolution 0ns Platform Name Clover Number of devices 1 Device Name AMD Radeon RX 6700 XT (navi22, LLVM 15.0.7, DRM 3.49, 6.2.0-26-generic) Device Vendor AMD Device Vendor ID0x1002 Device Version OpenCL 1.1 Mesa 23.0.4-0ubuntu1~23.04.1 Device Numeric Version 0x401000 (1.1.0) Driver Version 23.0.4-0ubuntu1~23.04.1 Device OpenCL C Version OpenCL C 1.1 Device OpenCL C Numeric Version 0x401000 (1.1.0) Device Type GPU Device Profile FULL_PROFILE Device AvailableYes Compiler Available Yes Max compute units 40 Max clock frequency 2855MHz Max work item dimensions3 Max work item sizes 256x256x256 Max work group size 256 === CL_PROGRAM_BUILD_LOG === fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': No such file or directory Preferred work group size multiple (kernel) Preferred / native vector sizes char16 / 16 short8 / 8 int 4 / 4 long 2 / 2 half 0 / 0(n/a) float4 / 4 double 2 / 2 (cl_khr_fp64) Half-precision Floating-point support (n/a) Single-precision Floating-point support (core) Denormals No Infinity and NANs Yes Round to nearest Yes Round to zero No Round to infinity No IEEE754-2008 fused multiply-add No Support is emulated in software No Correctly-rounded divide and sqrt operations N
[Desktop-packages] [Bug 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system
https://news.ycombinator.com/item?id=18711970 The sad state of being able to use Ubuntu on touch devices (hint: you can't) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807250 So, apparently support for an entire bus class has been missing since ubuntu bionic (18.04 LTS) was released in april. Using kernels from other distros or ubuntus old xenial 4.4.0-134 all provide access to sensor data, suggesting the issue is with current (and shipped) kernels. Three weeks into this not much is happening even though the issue also affect canonical-specific 4,18 kernels. This all suggests that pretty much no one has been using ubuntu on touch devices otherwise i wouldn't be the first one to notice this. Now that the devs know this they have no time for it... ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1807250 Title: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I have a Yoga 900-13ISK and a Thinkpad T470s. Both have had working screen rotation in the past. However, I noticed today while supporting a user in #ubuntu, neither do now. No icon in the Gnome menu and: # G_MESSAGES_DEBUG=all iio-sensor-proxy ** (process:14877): DEBUG: 12:31:21.603: Could not find any supported sensors Indeed, /sys/bus/iio does not exist! I believe this is distinct from LP: #1792813, as I have just tested mainline 4.19 and it also does not work. I am working on getting more data, including testing older kernels from 18.04, but it might take me some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1807250/+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
