[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
I see that impish got 1.20.13 of xserver-xorg-core recently. Is it fixed there? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Committed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+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 1938096] [NEW] touchpad lagging after resume from suspend
Public bug reported: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. Very strange. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well and the issue do present itself. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and even tried bumping the libinput10 to 1.18.0 from the impish repos today to no avail I'm afraid. ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Description changed: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 - - Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. Very strange. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. + Right after a clean reboot, the touchpad works fine. No issues + whatsoever. But after resuming from even its first suspend after a clean + boot, the touchpad feels less responsive, choppy or even laggy. Very + strange. I have tried removing and re-inserting some HID kernel modules, + "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found + anything that fixes it yet. The trackpoint works flawlessly all the + time, so that is the current backup when I don't have an external mouse + connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well and the issue do present itself. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and even tried bumping the libinput10 to 1.18.0 from the impish repos today to no avail I'm afraid. + + The journal has a lot of these errors after resuming: + + juli 27 00:17:41 machine touchegg[1003]: libinput error: event11 - + SYNA8009:00 06CB:CE57 Touchpad: kernel bug: Touch jump detected and + discarded. ** Description changed: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. Very strange. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well and the issue do present itself. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and even tried bumping the libinput10 to 1.18.0 from the impish repos today to no avail I'm afraid. - - The journal has a lot of these errors after resuming: - - juli 27 00:17:41 machine touchegg[1003]: libinput error: event11 - - SYNA8009:00 06CB:CE57 Touchpad: kernel bug: Touch jump detected and - discarded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: touchpad lagging after resume from suspend Status in libinput package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. Very strange. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well and the issue do present itself. I have also tried upgrading to the
[Desktop-packages] [Bug 1552040] Re: [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external monitor
Tried the first workaround, the X.org conf.d snippet, and this has helped a great deal. Although, sometimes the lock screen acts up and shows my windows, toolbars and is weirdly unresponsive after resuming from suspend. I suppose that could be a different bug, perhaps with Gnome or Gnome Shell? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1552040 Title: [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external monitor Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Usually a reboot fixes the problem. I see stuff like this in dmesg. [15294.887642] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15295.568309] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15295.587193] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15296.267547] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15296.286426] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15296.886015] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15296.886264] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* failed to train DP, aborting [15296.898472] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* Timed out waiting for DP idle patterns [15296.899688] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15297.579305] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15297.598328] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15298.279238] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15298.298275] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15298.965500] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15298.984539] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15299.665619] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15299.684522] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15300.367119] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15300.386173] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15301.067203] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15301.086097] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15301.768998] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15301.769703] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* failed to train DP, aborting [15301.781947] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* Timed out waiting for DP idle patterns ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. 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: Tue Mar 1 20:58:27 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2016-02-26 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType: LENOVO 20AQS00500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=bb8da1f1-8970-435e-aeaf-d7e1d9aa8a4e ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET85WW (2.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQS00500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information
[Desktop-packages] [Bug 1552040] Re: [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external monitor
Strange though, I did not have this problem at all in 18.04. Only occurred now after upgrading to 18.10. What changed? The kernel patch linked to is from 2016, and a lot of the other bug reports are older as well. Is it a regression of a sort? I have a Thinkpad X270 (latest BiOS - 1.33) and this is driving me nuts. Luckily I came across this bug report so I'll at least have a couple of workarounds to try out :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1552040 Title: [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external monitor Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Usually a reboot fixes the problem. I see stuff like this in dmesg. [15294.887642] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15295.568309] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15295.587193] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15296.267547] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15296.286426] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15296.886015] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15296.886264] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* failed to train DP, aborting [15296.898472] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* Timed out waiting for DP idle patterns [15296.899688] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15297.579305] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15297.598328] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15298.279238] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15298.298275] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15298.965500] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15298.984539] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15299.665619] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15299.684522] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15300.367119] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15300.386173] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15301.067203] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15301.086097] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit [15301.768998] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [15301.769703] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* failed to train DP, aborting [15301.781947] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* Timed out waiting for DP idle patterns ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. 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: Tue Mar 1 20:58:27 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2016-02-26 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType: LENOVO 20AQS00500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=bb8da1f1-8970-435e-aeaf-d7e1d9aa8a4e ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET85WW (2.35 ) dmi.board.asset.tag: Not Available dmi.board.name:
[Desktop-packages] [Bug 1788659] Re: network manager assigns ethernet default route metric of 20100
I have seen this for quite some time as well. Usually connected to both wifi and cabled network at work (while laptop is docked), which is quite handy for when I go to meetings and undock my laptop, but will stay online since I am also on wifi. After a while though, and after re-docking the laptop, the metric for the connections change and the wifi takes priority (eth0 gets 20100 metric, wifi stays on 600). I am still online though, but the wifi is quite a bit slower at times. Solution for now is to manually re-click my wired connection in nm- applet, or just disable auto-connect of the wifi altogether at work. -- 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/1788659 Title: network manager assigns ethernet default route metric of 20100 Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 18.04, when I boot with an ethernet cable connected, Ubuntu prefers to use the wifi interface over the ethernet interface. Wifi is assigned the normal metric of 600 for both of its routing table entries. However ethernet is assigned a metric of 20100. I edited the connection details via nmcli to manually set the ethernet metric to 100. After a reboot, the link route (for the LAN subnet) correctly has a metric of 100. But the default route for eth0 is still 20100. nm-applet shows the wifi icon, correctly indicating that the default route is over wifi rather than ethernet. The only fix is to manually set the route after every reboot, or turn off wifi. This is a regression from 16.04. network-manager 1.10.6-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788659/+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 1586528] Re: Avahi-daemon withdraws address record
This has been happening to me lately. I am using 17.04. I have a feeling it might be IPv6 related since we just started using that at work, so it's only affecting me there. Usually I see the following in my syslog: > Sep 5 15:40:46 laptop avahi-daemon[1158]: Withdrawing address record for > 1234:5678:4556::99 on eth0. > Sep 5 15:40:46 laptop avahi-daemon[1158]: Leaving mDNS multicast group on > interface eth0.IPv6 with address 1234:5678:4556::99. -- 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/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1374841] Re: gstreamer crashes when opening WMA files
Have the same problem, only with WMV. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1374841 Title: gstreamer crashes when opening WMA files Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Totem, Rhythmbox and VLC all crash immediately upon trying to load any WMA audio file. On the command line, Totem throws the following error: (totem:7461): GStreamer-CRITICAL **: gst_structure_new_empty: assertion 'gst_structure_validate_name (name)' failed Segmentation fault (core dumped) Ubuntu release: 14.04 gstreamer version: apt-cache policy ubuntu-restricted-extras ubuntu-restricted-extras: Installed: 60 Candidate: 60 Version table: *** 60 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: The WMA audio files should play. What happened instead: Every media player that uses gstreamer crashes immediately upon trying to open a WMA audio file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1374841/+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 1320557] Re: mobile broadband passwords and pin not stored in keyring
Same here on my T430 and my Ericsson H5321 module. -- 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/1320557 Title: mobile broadband passwords and pin not stored in keyring Status in “network-manager” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04: creating a new mobile broadband connection works fine. When connecting a usb stick to access the mobile network a PIN is requested. There is the option to store the PIN permanently. However, the key is not stored (queried after each insert) and seahorse does not show any entries. In the configuration dialog I can enter a PIN as well but this is not stored either. (This incident happened on a different machine so do not take machine information from the upload) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 17 23:49:25 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (365 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.154 metric 9 192.168.97.0/24 dev vmnet8 proto kernel scope link src 192.168.97.1 192.168.204.0/24 dev vmnet1 proto kernel scope link src 192.168.204.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-04-20 (27 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1320557/+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 1247468] Re: Network-manager is disabled after suspend
I'm having the same problem. Does networking work if suspending the computer with the following command: sudo sh -c sync echo 1 /sys/power/pm_trace pm-suspend ? For me, networking works when suspending with that command, but the screen isn't locked when resuming. -- 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/1247468 Title: Network-manager is disabled after suspend Status in “network-manager” package in Ubuntu: Confirmed Bug description: Upgraded recently to 13.10 (saucy). After the upgrade I could not connect to a wireless network after resuming from suspend. (It worked before the upgrade.) Eventually I figured out that I could kill network manager and restart it to fix the problem. Steps to Reproduce: 1. suspend 2. resume. nm-applet show networking is disabled. Checking Enable Networking has no effect. Workaround: After resume: sudo stop network-manager sudo start network-manager ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sat Nov 2 16:12:01 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2010-04-30 (1282 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) IpRoute: default via 10.0.0.1 dev wlan0 proto static 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.7 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-10-18 (15 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1247468/+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 1040885] Re: gnome-terminal auto-restores its size
Has the fix been pushed to quantal? Do I need to add quantal-proposed? I'm still having issues with this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1040885 Title: gnome-terminal auto-restores its size Status in GNOME Terminal: Fix Released Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: Occurs on Quantal TEST CASE 1. Press CTRL+ALT+T to launch a terminal 2. Press CTRL+SHIFT+T to open a new tab 3. Make sure the second tab is active and resize the window (Alt+Middle mouse button or Windows handles) 4. Click on the desktop ACTUAL RESULT Size of the terminal is restored to its initial size. It doesn't occur if the window is resized while first tab is active. EXPECTED RESULT The terminal doesn't autoresize with the user clicks on the desktop ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-terminal 3.5.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 Date: Thu Aug 23 23:21:07 2012 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to quantal on 2012-01-31 (204 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1040885/+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 1074528] Re: Global Menu Disappears When Using LibreOffice Calc
Same here. It doesn't hapen ALL the time, but mainly when editing files that are not .od*. Sometimes it helps to switch to another window and back again. -- 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/1074528 Title: Global Menu Disappears When Using LibreOffice Calc Status in “libreoffice” package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 12.10 When working with LibreOffice Calc, the global menu and hud sometimes disappears. I cannot reproduce this consistently. It happens often. Expected: See attached Expected.png Actual: See attached Actual.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1074528/+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 1060844] Re: vino-server crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 987287 *** https://bugs.launchpad.net/bugs/987287 Bug #987287 is'nt found. Why is that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1060844 Title: vino-server crashed with SIGABRT in raise() Status in “vino” package in Ubuntu: New Bug description: If I change the settings for the vino-server while running, it crashes again and again and again. Until I reboot and don't change any settings. This is the output from the terminal when running /usr/lib /vino-server (it crashes a couple of seconds after it starts): (vino-server:19761): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed 03/10/2012 11:49:28 AM Autoprobing TCP port in (all) network interface 03/10/2012 11:49:28 AM Listening IPv6://[::]:5900 03/10/2012 11:49:28 AM Listening IPv4://0.0.0.0:5900 03/10/2012 11:49:28 AM Autoprobing selected port 5900 03/10/2012 11:49:28 AM Advertising security type: 'TLS' (18) 03/10/2012 11:49:28 AM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 03/10/2012 11:49:28 AM Listening IPv6://[::]:5900 03/10/2012 11:49:28 AM Listening IPv4://0.0.0.0:5900 03/10/2012 11:49:28 AM Clearing securityTypes 03/10/2012 11:49:28 AM Advertising security type: 'TLS' (18) 03/10/2012 11:49:28 AM Clearing securityTypes 03/10/2012 11:49:28 AM Advertising security type: 'TLS' (18) 03/10/2012 11:49:28 AM Advertising authentication type: 'No Authentication' (1) 03/10/2012 11:49:28 AM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 03/10/2012 11:49:28 AM Listening IPv6://[::]:5900 03/10/2012 11:49:28 AM Listening IPv4://0.0.0.0:5900 03/10/2012 11:49:28 AM Clearing securityTypes 03/10/2012 11:49:28 AM Clearing authTypes 03/10/2012 11:49:28 AM Advertising security type: 'TLS' (18) 03/10/2012 11:49:28 AM Advertising authentication type: 'VNC Authentication' (2) 03/10/2012 11:49:28 AM Clearing securityTypes 03/10/2012 11:49:28 AM Clearing authTypes 03/10/2012 11:49:28 AM Advertising security type: 'TLS' (18) 03/10/2012 11:49:28 AM Advertising authentication type: 'VNC Authentication' (2) 03/10/2012 11:49:28 AM Advertising security type: 'VNC Authentication' (2) (vino-server:19761): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. *** glibc detected *** /usr/lib/vino/vino-server: free(): invalid pointer: 0x7fa3cd9d1798 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7e506)[0x7fa3cd699506] /usr/lib/libminiupnpc.so.8(FreeUPNPUrls+0x11)[0x7fa3d024b6d1] /usr/lib/vino/vino-server[0x4164b5] /usr/lib/vino/vino-server[0x41653d] /usr/lib/vino/vino-server[0x416ad0] /usr/lib/vino/vino-server[0x416c7e] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4863b)[0x7fa3cda2063b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7fa3cda1fab5] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x47de8)[0x7fa3cda1fde8] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x72)[0x7fa3cda201e2] /usr/lib/vino/vino-server[0x40bcc2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fa3cd63c76d] /usr/lib/vino/vino-server[0x40bda9] === Memory map: 0040-00446000 r-xp 08:08 392472 /usr/lib/vino/vino-server 00645000-00646000 r--p 00045000 08:08 392472 /usr/lib/vino/vino-server 00646000-00648000 rw-p 00046000 08:08 392472 /usr/lib/vino/vino-server 00648000-00655000 rw-p 00:00 0 00bb9000-00dc7000 rw-p 00:00 0 [heap] 7fa3b000-7fa3b0022000 rw-p 00:00 0 7fa3b0022000-7fa3b400 ---p 00:00 0 7fa3b800-7fa3b8022000 rw-p 00:00 0 7fa3b8022000-7fa3bc00 ---p 00:00 0 7fa3beffe000-7fa3befff000 ---p 00:00 0 7fa3befff000-7fa3bf7ff000 rw-p 00:00 0 [stack:19764] 7fa3bf7ff000-7fa3bf80 ---p 00:00 0 7fa3bf80-7fa3c000 rw-p 00:00 0 [stack:19763] 7fa3c000-7fa3c0021000 rw-p 00:00 0 7fa3c0021000-7fa3c400 ---p 00:00 0 7fa3c41ca000-7fa3c41df000 r-xp 08:08 652937 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fa3c41df000-7fa3c43de000 ---p 00015000 08:08 652937 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fa3c43de000-7fa3c43df000 r--p 00014000 08:08 652937 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fa3c43df000-7fa3c43e rw-p 00015000 08:08 652937 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fa3c43e-7fa3c43e5000 r-xp 08:08 393056
[Desktop-packages] [Bug 566812] Re: USB Modem wont connect after modem hangup
It doesn't seem to be fixed in Oneiric either. I've looked into the source code in oneiric, and it doesn't look like the patch has been submitted. I would very much like to test this and get it fixed somehow. -- 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/566812 Title: USB Modem wont connect after modem hangup Status in ModemManager (with NetworkManager support): New Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager Running my Huawei USB modem (Bus 002 Device 007: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem) in Lucid Beta 2 amd64 (uname -a = Linux laptop-hostname 2.6.32-19-generic #28-Ubuntu SMP Thu Apr 1 10:39:41 UTC 2010 x86_64 GNU/Linux) and, after the same usb_modeswitch used in Intrepid, connection is fine. If signal is lost causing modem hangup, reconnection is not possible without unplugging modem, replugging, usb_modeswitch and then reconnect. Logs: Apr 19 18:03:42 laptop-hostname pppd[1751]: Sent 91110 bytes, received 298361 bytes. Apr 19 18:03:42 laptop-hostname pppd[1751]: Modem hangup Apr 19 18:03:42 laptop-hostname pppd[1751]: Connection terminated. Apr 19 18:03:42 laptop-hostname NetworkManager: info (ttyUSB0): device state change: 8 - 9 (reason 13) Apr 19 18:03:42 laptop-hostname NetworkManager: info Activation (ttyUSB0) failed. Apr 19 18:03:42 laptop-hostname NetworkManager: info (ttyUSB0): device state change: 9 - 3 (reason 0) Apr 19 18:03:42 laptop-hostname NetworkManager: info (ttyUSB0): deactivating device (reason: 0). Apr 19 18:03:42 laptop-hostname modem-manager: (ttyUSB0) closing serial device... Apr 19 18:03:42 laptop-hostname modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected - disconnecting) Apr 19 18:03:42 laptop-hostname modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting - connected) Apr 19 18:03:42 laptop-hostname NetworkManager:SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Apr 19 18:03:44 laptop-hostname NetworkManager: debug [1271696624.001843] ensure_killed(): waiting for ppp pid 1751 to exit Apr 19 18:03:44 laptop-hostname NetworkManager: debug [1271696624.003285] ensure_killed(): ppp pid 1751 cleaned up Apr 19 18:04:19 laptop-hostname NetworkManager: info Activation (ttyUSB0) starting connection '3 Internet' Apr 19 18:04:19 laptop-hostname NetworkManager: info (ttyUSB0): device state change: 3 - 4 (reason 0) Apr 19 18:04:19 laptop-hostname NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Apr 19 18:04:19 laptop-hostname NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Apr 19 18:04:19 laptop-hostname NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Apr 19 18:04:19 laptop-hostname NetworkManager: WARN stage1_prepare_done(): GSM modem connection failed: (32) Sending command failed: device is not enabled Apr 19 18:04:19 laptop-hostname NetworkManager: info (ttyUSB0): device state change: 4 - 9 (reason 1) Apr 19 18:04:19 laptop-hostname NetworkManager: info Marking connection '3 Internet' invalid. Apr 19 18:04:19 laptop-hostname modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected - disconnecting) Apr 19 18:04:19 laptop-hostname modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting - connected) Apr 19 18:04:19 laptop-hostname NetworkManager: info Activation (ttyUSB0) failed. Apr 19 18:04:19 laptop-hostname NetworkManager: info (ttyUSB0): device state change: 9 - 3 (reason 0) Apr 19 18:04:19 laptop-hostname NetworkManager: info (ttyUSB0): deactivating device (reason: 0). Apr 19 18:04:31 laptop-hostname NetworkManager: info Activation (ttyUSB0) starting connection '3 Internet' Apr 19 18:04:31 laptop-hostname NetworkManager: info (ttyUSB0): device state change: 3 - 4 (reason 0) Apr 19 18:04:31 laptop-hostname NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Apr 19 18:04:31 laptop-hostname NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Apr 19 18:04:31 laptop-hostname NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Apr 19 18:04:31 laptop-hostname NetworkManager: WARN stage1_prepare_done(): GSM modem connection failed: (32) Sending command failed: device is not enabled Apr 19 18:04:31 laptop-hostname NetworkManager: info (ttyUSB0): device state change: 4 - 9 (reason 1) Apr 19 18:04:31 laptop-hostname NetworkManager: info Marking connection '3 Internet' invalid. Apr 19 18:04:31 laptop-hostname NetworkManager: info Activation (ttyUSB0)
