[opensuse-gnome] Some observations on Gnome 3.14 in Factory

newer
[opensuse-gnome] Problem with some...

older
[opensuse-gnome] Ancient startup...

Gerald Pfeifer

7 Oct 2014 7 Oct '14

05:06

Now that I switched towards using Factory for a fair amount of my time again (How's that for being brave? ;-) I made a couple of observations around the recent GNOME 3.14 update which I figured I'd share to hopefully make the experience a bit smoother for others and hopefully some improvements for openSUSE 13.2. The good: - Things generally work just fine! Performance is fine, the UI fresh, some improvements such as sorting timezones in the Clocks applet (thanks Michael Gorse!), nm-connection-editor no longer referring to FirewallD (thanks Dominique),... have been integrated. And, do not let this mail mislead you, please: I am not meaning to rant, and generally a happy user. Where things work, it's kind of hard to write a lot about it, though. That is why this section is the shortest of the three. ;-) The bad: - As in Gnome 3.12 already, every time I connect to a new wireless network, I have to enter the root password. This is a regression from openSUSE 13.1. Do you want a formal bug report? - Configuration loss: Going from 3.12 to 3.14 lost a number of settings, including the fact that I had "minimize window" and "maximize window" buttons configured via TweakTool. Setting these in TweakTool again under "Windows" fixed it for me, but why did this get lost? Do you want a formal bug report? - Configuration loss: Similarly, gnome-terminal which had been showing black text on white background forever, including the update from openSUSE 13.1 to Gnome 3.12, suddenly appear yellow on black or something after upgrading to Gnome 3.14. What happened there? Do you want a formal bug report? - Most of my Gnome Shell extensions stopped working, including "Media player indicator" and "Openweather". Trying to update these via TweakTool resulted in the button turning "Error". That makes three issues here: 1. Gnome version update breaks extensions. 2. "Update" of Extensions in TweakTool does not work. 3. No useful error messages or other feedback for the above. (Removing the two extensions and then reinstalling them by pointing Firefox to extensions.gnome.org worked just fine.) The ugly: - Being behind a slow and unreliable network for some days, I had to udate the system piecemeal and ran into missing dependencies on a package / package base ( http://bugzilla.suse.com/show_bug.cgi?id=899776 "gnome-clocks lacks dependencies: undefined symbol: gtk_application_get_menu_by_id" ). Luckily it was only this, or I might not have had a running desktop environment for a day or two. - Design: The upstream Gnome designers still force title bars that consume 10% of my screen height (yes, I'm exaggerating, only midly though) upon me. Is there a better way to fix that than hacking title_vertical_pad in /usr/share/themes/Adwaita/metacity-1/metacity-theme-3.xml after every update? Gerald -- Dr. Gerald Pfeifer Sr. Director Product Management and Operations, SUSE -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Show replies by date

Dimstar / Dominique Leuenberger

7 Oct 7 Oct

12:04

Hi Gerald, On Tue, 2014-10-07 at 07:06 +0200, Gerald Pfeifer wrote:

...

Now that I switched towards using Factory for a fair amount of my time again (How's that for being brave? ;-) I made a couple of observations around the recent GNOME 3.14 update which I figured I'd share to hopefully make the experience a bit smoother for others and hopefully some improvements for openSUSE 13.2.

Observations are always welcome... but no promises given.

...

The good:

- Things generally work just fine!

Performance is fine, the UI fresh, some improvements such as sorting timezones in the Clocks applet (thanks Michael Gorse!), nm-connection-editor no longer referring to FirewallD (thanks Dominique),... have been integrated.

And, do not let this mail mislead you, please: I am not meaning to rant, and generally a happy user. Where things work, it's kind of hard to write a lot about it, though. That is why this section is the shortest of the three. ;-)

Right you are. Finding the positive things is more difficult, because that's usually 'what you expect it to be'. Nevertheless, I thank you for taking the time to still take the time to mention a few things before going to the negatives (I'm sure you had some manager's feedback training :P )

...

The bad:

- As in Gnome 3.12 already, every time I connect to a new wireless network, I have to enter the root password. This is a regression from openSUSE 13.1. Do you want a formal bug report?

Was an error on my side: updating the packages to 3.12, I lost a patch on the way (which, funnily enough, was about 6 months ago.. and only last week somebody reported it. gnome-shell 3.14, as is currently in Factory, has the patch re-enabled and functioning.

...

- Configuration loss: Going from 3.12 to 3.14 lost a number of settings, including the fact that I had "minimize window" and "maximize window" buttons configured via TweakTool. Setting these in TweakTool again under "Windows" fixed it for me, but why did this get lost? Do you want a formal bug report?

I'll have to check that one out.. probably some schema changes, moving them around.. not the nicest thing to happen.

...

- Configuration loss: Similarly, gnome-terminal which had been showing black text on white background forever, including the update from openSUSE 13.1 to Gnome 3.12, suddenly appear yellow on black or something after upgrading to Gnome 3.14. What happened there? Do you want a formal bug report.

gnome-terminal indeed switch to the dark-theme by default for itself. I myself, probably due to my age, have been using 'Green on black' for like EVER :) Gives me the nostalgic feeling of my first PC/Screen (which, as an anecdote, had a switch under the screen to toggle between 'green on black' and 'amber on black'.)

...

- Most of my Gnome Shell extensions stopped working, including "Media player indicator" and "Openweather". Trying to update these via TweakTool resulted in the button turning "Error".

That makes three issues here:

1. Gnome version update breaks extensions. 2. "Update" of Extensions in TweakTool does not work. 3. No useful error messages or other feedback for the above.

As extensions are not maintained by the package manager, updating gnome-shell will (unfortunately) always cause this to happen. GNOME Upstream is fully aware of that and is working out an update mechanism for user-installed extensions. For now, there is not much more I can say.

...

(Removing the two extensions and then reinstalling them by pointing Firefox to extensions.gnome.org worked just fine.)

The ugly:

- Being behind a slow and unreliable network for some days, I had to udate the system piecemeal and ran into missing dependencies on a package / package base ( http://bugzilla.suse.com/show_bug.cgi?id=899776 "gnome-clocks lacks dependencies: undefined symbol: gtk_application_get_menu_by_id" ). Luckily it was only this, or I might not have had a running desktop environment for a day or two.

As stated on the bug: rpm detects the library dependencies. The packager generally gives build dependencies (GNOME Team even versions the ones that are also checked on a version by the configure scripts). If it were up to the packager to add all libraries, a package depends on, manually and statically into the .spec file, I can basically only guarantee mess and disaster. A common practice on rolling distributions: only full updates are supportable (this is also valid for Arch for example). The bug is still open, and maybe somebody comes up with smart ideas (symbol versioning in the libs comes to mind.. for GTK, this is even in the talks (the main issue is the maintenance effort to ensure it is always true).

...

- Design: The upstream Gnome designers still force title bars that consume 10% of my screen height (yes, I'm exaggerating, only midly though) upon me.

Start a crowd-funding campaign to get funds for a proper screen!

...

Is there a better way to fix that than hacking title_vertical_pad in /usr/share/themes/Adwaita/metacity-1/metacity-theme-3.xml after every update?

You can install a custom theme in ~ and use this.. then at least it won't be overwritten every two days. Best regards, Dominique -- Dimstar / Dominique Leuenberger -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Gerald Pfeifer

8 Oct 8 Oct

06:59

On Tue 2014-10-07, Dimstar / Dominique Leuenberger wrote:

...

...
- As in Gnome 3.12 already, every time I connect to a new wireless network, I have to enter the root password. This is a regression from openSUSE 13.1. Do you want a formal bug report? Was an error on my side: updating the packages to 3.12, I lost a patch on the way (which, funnily enough, was about 6 months ago.. and only last week somebody reported it. gnome-shell 3.14, as is currently in Factory, has the patch re-enabled and functioning.

Hmm, I still observe this behavior. Is this still syncing? On a related(?) note, every time I wake up my system from suspend-to-RAM, I now get "System policy prevents unlocking... the mobile broadbind device" and a request for the root password. This is before I can enter my own password. Is this the same thing as you mention above, or a different one that I should report? Gerald -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Dimstar / Dominique Leuenberger

07:06

On Wed, 2014-10-08 at 08:59 +0200, Gerald Pfeifer wrote:

...

On Tue 2014-10-07, Dimstar / Dominique Leuenberger wrote:

...
...
- As in Gnome 3.12 already, every time I connect to a new wireless network, I have to enter the root password. This is a regression from openSUSE 13.1. Do you want a formal bug report? Was an error on my side: updating the packages to 3.12, I lost a patch on the way (which, funnily enough, was about 6 months ago.. and only last week somebody reported it. gnome-shell 3.14, as is currently in Factory, has the patch re-enabled and functioning.

Hmm, I still observe this behavior. Is this still syncing?

Can you check the latest changelog entry in gnome-shell? rpm -q --changelog gnome-shell | head -n 3 If fully synced, you would get * Sun Oct 05 2014 dimstar@opensuse.org - Rebase and re-enable gnome-shell-private-connection.patch (boo#899789). But as far as I know there was no Factory publish in between; look out for the 'New Factory snapshot' announcements on openSUSE-Factory mailing list.

...

On a related(?) note, every time I wake up my system from suspend-to-RAM, I now get "System policy prevents unlocking... the mobile broadbind device" and a request for the root password.

This is before I can enter my own password.

Is this the same thing as you mention above, or a different one that I should report?

Should be a different report.. Dominique -- Dimstar / Dominique Leuenberger -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Gerald Pfeifer

14 Oct 14 Oct

14:17

On Wed 2014-10-08, Dimstar / Dominique Leuenberger wrote:

...

Can you check the latest changelog entry in gnome-shell? rpm -q --changelog gnome-shell | head -n 3

If fully synced, you would get * Sun Oct 05 2014 dimstar@opensuse.org - Rebase and re-enable gnome-shell-private-connection.patch (boo#899789).

Over the weekend Factory synced again, and I got gnome-shell with your patch. First tests indicate everything is fine again. :-) Thanks!

...

...
On a related(?) note, every time I wake up my system from suspend-to-RAM, I now get "System policy prevents unlocking... the mobile broadbind device" and a request for the root password. Should be a different report..

Make sense. For those interested to follow, this is the report: http://bugzilla.suse.com/show_bug.cgi?id=900813 "System policy prevents unlocking or controlling the mobile broadband device" always appears after suspend-to-RAM Plus a related one: http://bugzilla.suse.com/show_bug.cgi?id=901041 "SIM Pin Unlock Required" with every system start and after suspend-to-RAM Plus another one which may not be a GNOME one: http://bugzilla.suse.com/show_bug.cgi?id=901122 "Need to restart ModemManager after suspend-to-RAM for 3G/UMTS" Gerald PS: And http://bugzilla.suse.com/show_bug.cgi?id=901125 "Need to set options cdc_ncm prefer_mbim=N for Ericsson 3G/UMTS broadband card to work" which is not a GNOME issue for sure ;-), but for the sake of completeness. -- Dr. Gerald Pfeifer Sr. Director Product Management and Operations, SUSE -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Dimstar / Dominique Leuenberger

14:34

Gerald, Much appreciate your feedback. On Tue, 2014-10-14 at 16:17 +0200, Gerald Pfeifer wrote:

...

On Wed 2014-10-08, Dimstar / Dominique Leuenberger wrote:

...
Can you check the latest changelog entry in gnome-shell? rpm -q --changelog gnome-shell | head -n 3

If fully synced, you would get * Sun Oct 05 2014 dimstar@opensuse.org - Rebase and re-enable gnome-shell-private-connection.patch (boo#899789).

Over the weekend Factory synced again, and I got gnome-shell with your patch. First tests indicate everything is fine again. :-) Thanks!

...
...
On a related(?) note, every time I wake up my system from suspend-to-RAM, I now get "System policy prevents unlocking... the mobile broadbind device" and a request for the root password. Should be a different report..

Make sense. For those interested to follow, this is the report:

http://bugzilla.suse.com/show_bug.cgi?id=900813 "System policy prevents unlocking or controlling the mobile broadband device" always appears after suspend-to-RAM

Assigned to the 'security team', who manages polkit authorizations. so not exactly 'gnome' issue.

...

Plus a related one:

http://bugzilla.suse.com/show_bug.cgi?id=901041 "SIM Pin Unlock Required" with every system start and after suspend-to-RAM

Strange one.. I think I have somewhere a model with a SIM slot around, so I might at least be able to reproduce that one. Might make it easier to even find out what questions to ask, which logs to receive. The driver option is 'out of scope' of ModemManager; this would be a kernel change (any output in dmesg regarding the module might give indications as to why it would be needed); but anyway, there is a sep. bug for that one already.

...

Plus another one which may not be a GNOME one:

http://bugzilla.suse.com/show_bug.cgi?id=901122 "Need to restart ModemManager after suspend-to-RAM for 3G/UMTS"

Gerald

That one is certainly not nice. do you see anything in particular in systemctl status ModemManager prior to restarting it? -- Dimstar / Dominique Leuenberger -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Gerald Pfeifer

20 Oct 20 Oct

07:25

On Tue 2014-10-14, Dimstar / Dominique Leuenberger wrote:

...

...
http://bugzilla.suse.com/show_bug.cgi?id=901122 "Need to restart ModemManager after suspend-to-RAM for 3G/UMTS" That one is certainly not nice. do you see anything in particular in systemctl status ModemManager prior to restarting it?

This does not show anything significant, though it seems the signal strength update is still working? ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled) Active: active (running) since Son 2014-10-19 12:30:33 CEST; 20h ago Main PID: 5271 (ModemManager) CGroup: /system.slice/ModemManager.service └─5271 /usr/sbin/ModemManager Okt 20 09:13:56 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP location updated (MCC: '262'...D: '0') Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: access technology changed (umts -> hspa) Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP location updated (MCC: '0', ...D: '0') Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP Registration state changed (...> home) Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: state changed (searching -> registered) Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP location updated (MCC: '0', ...F5E8A') Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: signal quality updated (40) Okt 20 09:14:27 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: signal quality updated (40) Okt 20 09:14:32 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP location updated (MCC: '0', ...F5E8E') Okt 20 09:14:32 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: access technology changed (hspa -> umts) dmesg, on the other hand may be interesting. Watch out for lines with "cdc": [53018.247928] PM: resume of devices complete after 2738.881 msecs [53018.248241] PM: Finishing wakeup. [53018.248243] Restarting tasks ... done. [53018.257593] usb 1-4: USB disconnect, device number 6 [53018.257810] cdc_acm 1-4:1.1: failed to set dtr/rts [53018.261261] cdc_acm 1-4:1.3: failed to set dtr/rts [53018.261764] cdc_ncm 1-4:1.6 wwp0s20u4i6: unregister 'cdc_ncm' usb-0000:00:14.0-4, Mobile Broadband Network Device [53018.303615] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801b3a46a00 [53018.303619] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801b3a46a48 [53018.303621] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88019ae5b4c0 [53018.303622] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88019ae5b508 [53018.303624] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801ecbe14c0 [53018.303626] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801ecbe1508 [53018.303628] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c9c2b140 [53018.303630] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801b3a461c0 [53018.303631] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801b3a46208 [53018.303633] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880211cbcac0 [53018.303635] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c9c2aac0 [53018.303636] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c9c2bb40 [53018.303638] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88003739aac0 [53018.303640] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880210930b40 [53019.027171] usb 1-4: new high-speed USB device number 7 using xhci_hcd [53019.157294] usb 1-4: New USB device found, idVendor=0bdb, idProduct=1926 [53019.157311] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [53019.157314] usb 1-4: Product: H5321 gw [53019.157317] usb 1-4: Manufacturer: Lenovo [53019.157319] usb 1-4: SerialNumber: AB74AECE5318A2M0 [53019.189976] cdc_acm 1-4:1.1: ttyACM2: USB ACM device [53019.190668] cdc_acm 1-4:1.3: ttyACM3: USB ACM device [53019.194115] cdc_wdm 1-4:1.5: cdc-wdm0: USB WDM device [53019.209553] cdc_ncm 1-4:1.6: MAC-Address: 02:15:e0:ec:01:00 [53019.209950] cdc_ncm 1-4:1.6 wwan0: register 'cdc_ncm' at usb-0000:00:14.0-4, Mobile Broadband Network Device, 02:15:e0:ec:01:00 [53019.210593] cdc_wdm 1-4:1.8: cdc-wdm1: USB WDM device [53019.210845] cdc_acm 1-4:1.9: ttyACM4: USB ACM device [53021.585924] e1000e: enp0s25 NIC Link is Down [53021.903759] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X [53022.005098] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X [53022.005381] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [53022.020760] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S [53022.027378] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [53022.116213] IPv6: ADDRCONF(NETDEV_UP): wl: link is not ready [53028.715929] VFS: busy inodes on changed media or resized disk sr0 Is it possible cdc_* is reset, but ModemManager not reconnecting properly? When I then systemctl restart ModemManager, I see the following: 2014-10-20T09:20:56.682387+02:00 tuna sudo: ... COMMAND=/usr/bin/systemctl restart ModemManager 2014-10-20T09:20:56.688264+02:00 tuna ModemManager[5271]: <info> Caught signal, shutting down... 2014-10-20T09:20:56.841386+02:00 tuna ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: state changed (registered -> disabling) 2014-10-20T09:20:56.841709+02:00 tuna ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: signal quality updated (0) 2014-10-20T09:20:56.841907+02:00 tuna ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: access technology changed (umts -> unknown) 2014-10-20T09:20:56.960329+02:00 tuna ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP Registration state changed (home -> unknown) 2014-10-20T09:20:56.962966+02:00 tuna ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: state changed (disabling -> disabled) 2014-10-20T09:20:57.150619+02:00 tuna ModemManager[5271]: <info> ModemManager is shut down 2014-10-20T09:20:57.292214+02:00 tuna ModemManager[26061]: <info> ModemManager (version 1.0.0) starting... 2014-10-20T09:20:57.302456+02:00 tuna sudo: pam_unix(sudo:session): session closed for user root 2014-10-20T09:20:58.445400+02:00 tuna org.freedesktop.Tracker1[1428]: (tracker-store:1735): GLib-CRITICAL **: Source ID 6754 was not found when attempting to remove it 2014-10-20T09:20:58.445665+02:00 tuna org.freedesktop.Tracker1[1428]: (tracker-store:1735): GLib-CRITICAL **: Source ID 6757 was not found when attempting to remove it 2014-10-20T09:20:59.799423+02:00 tuna ModemManager[26061]: <info> Creating modem with plugin 'Ericsson MBM' and '6' ports 2014-10-20T09:20:59.799739+02:00 tuna ModemManager[26061]: <warn> Could not grab port (usbmisc/cdc-wdm1): 'Cannot add port 'usbmisc/cdc-wdm1', unsupported' 2014-10-20T09:20:59.799944+02:00 tuna ModemManager[26061]: <warn> Could not grab port (usbmisc/cdc-wdm0): 'Cannot add port 'usbmisc/cdc-wdm0', unsupported' 2014-10-20T09:20:59.800138+02:00 tuna ModemManager[26061]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4' successfully created 2014-10-20T09:20:59.800342+02:00 tuna ModemManager[26061]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin 2014-10-20T09:20:59.800559+02:00 tuna ModemManager[26061]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0': not supported by any plugin 2014-10-20T09:20:59.957358+02:00 tuna ModemManager[26061]: <warn> couldn't load Supported Modes: 'Couldn't retrieve supported modes' 2014-10-20T09:21:01.050152+02:00 tuna ModemManager[26061]: <info> Modem: state changed (unknown -> disabled) 2014-10-20T09:21:01.057351+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling) 2014-10-20T09:21:01.090688+02:00 tuna gnome-session[1379]: ** (gnome-shell:1532): CRITICAL **: nma_mobile_providers_database_lookup_cdma_sid: assertion 'sid > 0' failed 2014-10-20T09:21:08.544383+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering) 2014-10-20T09:21:08.544654+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> umts) 2014-10-20T09:21:08.580373+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa) 2014-10-20T09:21:08.623842+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home) 2014-10-20T09:21:08.735018+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (hspa -> umts) 2014-10-20T09:21:08.735270+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '3BB', Cell ID: 'EAF5E8E') 2014-10-20T09:21:08.735471+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '262', MNC: '2', Location area code: '3BB', Cell ID: 'EAF5E8E') 2014-10-20T09:21:08.735613+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa) 2014-10-20T09:21:08.939190+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered) 2014-10-20T09:21:08.952566+02:00 tuna ModemManager[26061]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (40) 2014-10-20T09:21:15.798389+02:00 tuna ModemManager[26061]: <info> Creating modem with plugin 'Generic' and '1' ports 2014-10-20T09:21:15.798662+02:00 tuna ModemManager[26061]: <warn> Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' 2014-10-20T09:21:15.798885+02:00 tuna ModemManager[26061]: <warn> Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port 2014-10-20T09:21:22.456719+02:00 tuna org.freedesktop.Tracker1[1428]: (tracker-store:1735): GLib-CRITICAL **: Source ID 6766 was not found when attempting to remove it Does this trigger any idea? Any then it works again when I choose the connection via the system panel. (Before it would not even show the three "trying to establish connection" dots; simply no visual reaction at all.) Gerald

Dimstar / Dominique Leuenberger

07:49

On Mon, 2014-10-20 at 09:25 +0200, Gerald Pfeifer wrote:

...

On Tue 2014-10-14, Dimstar / Dominique Leuenberger wrote:

...
...
http://bugzilla.suse.com/show_bug.cgi?id=901122 "Need to restart ModemManager after suspend-to-RAM for 3G/UMTS" That one is certainly not nice. do you see anything in particular in systemctl status ModemManager prior to restarting it?

This does not show anything significant, though it seems the signal strength update is still working?

ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled) Active: active (running) since Son 2014-10-19 12:30:33 CEST; 20h ago Main PID: 5271 (ModemManager) CGroup: /system.slice/ModemManager.service └─5271 /usr/sbin/ModemManager

Okt 20 09:13:56 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP location updated (MCC: '262'...D: '0') Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: access technology changed (umts -> hspa) Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP location updated (MCC: '0', ...D: '0') Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP Registration state changed (...> home) Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: state changed (searching -> registered) Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP location updated (MCC: '0', ...F5E8A') Okt 20 09:13:57 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: signal quality updated (40) Okt 20 09:14:27 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: signal quality updated (40) Okt 20 09:14:32 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: 3GPP location updated (MCC: '0', ...F5E8E') Okt 20 09:14:32 tuna.site ModemManager[5271]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: access technology changed (hspa -> umts)

dmesg, on the other hand may be interesting. Watch out for lines with "cdc":

[53018.247928] PM: resume of devices complete after 2738.881 msecs [53018.248241] PM: Finishing wakeup. [53018.248243] Restarting tasks ... done. [53018.257593] usb 1-4: USB disconnect, device number 6 [53018.257810] cdc_acm 1-4:1.1: failed to set dtr/rts [53018.261261] cdc_acm 1-4:1.3: failed to set dtr/rts [53018.261764] cdc_ncm 1-4:1.6 wwp0s20u4i6: unregister 'cdc_ncm' usb-0000:00:14.0-4, Mobile Broadband Network Device [53018.303615] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801b3a46a00 [53018.303619] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801b3a46a48 [53018.303621] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88019ae5b4c0 [53018.303622] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88019ae5b508 [53018.303624] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801ecbe14c0 [53018.303626] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801ecbe1508 [53018.303628] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c9c2b140 [53018.303630] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801b3a461c0 [53018.303631] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801b3a46208 [53018.303633] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880211cbcac0 [53018.303635] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c9c2aac0 [53018.303636] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c9c2bb40 [53018.303638] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88003739aac0 [53018.303640] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880210930b40 [53019.027171] usb 1-4: new high-speed USB device number 7 using xhci_hcd [53019.157294] usb 1-4: New USB device found, idVendor=0bdb, idProduct=1926 [53019.157311] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [53019.157314] usb 1-4: Product: H5321 gw [53019.157317] usb 1-4: Manufacturer: Lenovo [53019.157319] usb 1-4: SerialNumber: AB74AECE5318A2M0 [53019.189976] cdc_acm 1-4:1.1: ttyACM2: USB ACM device [53019.190668] cdc_acm 1-4:1.3: ttyACM3: USB ACM device [53019.194115] cdc_wdm 1-4:1.5: cdc-wdm0: USB WDM device [53019.209553] cdc_ncm 1-4:1.6: MAC-Address: 02:15:e0:ec:01:00 [53019.209950] cdc_ncm 1-4:1.6 wwan0: register 'cdc_ncm' at usb-0000:00:14.0-4, Mobile Broadband Network Device, 02:15:e0:ec:01:00 [53019.210593] cdc_wdm 1-4:1.8: cdc-wdm1: USB WDM device [53019.210845] cdc_acm 1-4:1.9: ttyACM4: USB ACM device [53021.585924] e1000e: enp0s25 NIC Link is Down [53021.903759] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X [53022.005098] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X [53022.005381] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [53022.020760] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S [53022.027378] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [53022.116213] IPv6: ADDRCONF(NETDEV_UP): wl: link is not ready [53028.715929] VFS: busy inodes on changed media or resized disk sr0

Is it possible cdc_* is reset, but ModemManager not reconnecting properly?

Thanks! The CDC got me on track of a current work-in-progress bug report with ModemManager; there was a firmware issue identified which is currently attempted to be worked around. But then, it also seems we missed a few updates of ModemManager; shame on us. An update for 13.2 is certainly not realistic at this moment. We can try to add a restart-script in /usr/lib/systemd/system-sleep 50-restart_MM

...

...
...
- SNIP HERE - <<< #!/bin/sh case $1 in resume|thaw|post) /usr/bin/systemctl restart ModemManager.service > /dev/null ;; esac - SNIP HERE - <<<

This would probably work around your issue with the cdc firmware, until MM integrates a workaround in the code (WIP) -- Dimstar / Dominique Leuenberger -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Michael Hill

11:24

Hi Dominique, On Mon, Oct 20, 2014 at 3:49 AM, Dimstar / Dominique Leuenberger wrote:

...

Thanks! The CDC got me on track of a current work-in-progress bug report with ModemManager; there was a firmware issue identified which is currently attempted to be worked around.

Would this also explain the lack of response from ModemManager when I plug in my N9? Mike -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Dimstar / Dominique Leuenberger

18:37

On Mon, 2014-10-20 at 07:24 -0400, Michael Hill wrote:

...

Hi Dominique,

On Mon, Oct 20, 2014 at 3:49 AM, Dimstar / Dominique Leuenberger wrote:

...
Thanks! The CDC got me on track of a current work-in-progress bug report with ModemManager; there was a firmware issue identified which is currently attempted to be worked around.

Would this also explain the lack of response from ModemManager when I plug in my N9?

Mike

Mike, I guess the N9 is a different story (as Gerald's problem is really only after resuming the system). For both cases, I published a new ModemManager package in home:dimstar:boo901122 [1]; you can test it, but there is close to no realistic way to get this into 13.2 at this stage (considering that libmbim comes with an ABI change). With sufficient analysis and testing, I might do a online update though (first tests here seem fine, and it appears as nothing besides ModemManager actually USES libmbim.. so we might be able to push it; but for this it better fix your issues :) ) [1] http://download.opensuse.org/repositories/home:/dimstar:/boo901122/openSUSE_... -- Dimstar / Dominique Leuenberger -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Michael Hill

18:48

Thanks, Dominique. I'll keep you posted! Mike On Mon, Oct 20, 2014 at 2:37 PM, Dimstar / Dominique Leuenberger wrote:

...

On Mon, 2014-10-20 at 07:24 -0400, Michael Hill wrote:

...
Hi Dominique,

On Mon, Oct 20, 2014 at 3:49 AM, Dimstar / Dominique Leuenberger wrote:

...
Thanks! The CDC got me on track of a current work-in-progress bug report with ModemManager; there was a firmware issue identified which is currently attempted to be worked around.

Would this also explain the lack of response from ModemManager when I plug in my N9?

Mike

Mike, I guess the N9 is a different story (as Gerald's problem is really only after resuming the system).

For both cases, I published a new ModemManager package in home:dimstar:boo901122 [1]; you can test it, but there is close to no realistic way to get this into 13.2 at this stage (considering that libmbim comes with an ABI change). With sufficient analysis and testing, I might do a online update though (first tests here seem fine, and it appears as nothing besides ModemManager actually USES libmbim.. so we might be able to push it; but for this it better fix your issues :) )

[1] http://download.opensuse.org/repositories/home:/dimstar:/boo901122/openSUSE_...

-- Dimstar / Dominique Leuenberger

-- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Michael Hill

21 Oct 21 Oct

23:51

On Mon, Oct 20, 2014 at 2:37 PM, Dimstar / Dominique Leuenberger wrote:

...

For both cases, I published a new ModemManager package in home:dimstar:boo901122 [1]; you can test it, but there is close to no realistic way to get this into 13.2 at this stage (considering that libmbim comes with an ABI change). With sufficient analysis and testing, I might do a online update though (first tests here seem fine, and it appears as nothing besides ModemManager actually USES libmbim.. so we might be able to push it; but for this it better fix your issues :) )

So far so good... ModemManager starts up, recognizes the phone, and offers Mobile Broadband in the system status menu. I'll try connecting when I can document it. Thanks, Mike -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Roger Luedecke

22 Oct 22 Oct

21:59

On Mon, 2014-10-20 at 20:37 +0200, Dimstar / Dominique Leuenberger wrote:

...

On Mon, 2014-10-20 at 07:24 -0400, Michael Hill wrote:

...
Hi Dominique,

On Mon, Oct 20, 2014 at 3:49 AM, Dimstar / Dominique Leuenberger wrote:

...
Thanks! The CDC got me on track of a current work-in-progress bug report with ModemManager; there was a firmware issue identified which is currently attempted to be worked around.

Would this also explain the lack of response from ModemManager when I plug in my N9?

Mike

Mike, I guess the N9 is a different story (as Gerald's problem is really only after resuming the system).

For both cases, I published a new ModemManager package in home:dimstar:boo901122 [1]; you can test it, but there is close to no realistic way to get this into 13.2 at this stage (considering that libmbim comes with an ABI change). With sufficient analysis and testing, I might do a online update though (first tests here seem fine, and it appears as nothing besides ModemManager actually USES libmbim.. so we might be able to push it; but for this it better fix your issues :) )

[1] http://download.opensuse.org/repositories/home:/dimstar:/boo901122/openSUSE_...

-- Dimstar / Dominique Leuenberger

If it wouldn't break anything else, I'd push it. When users start putting these systems on metal, nearly every conceivable thing that can go wrong will for someone. Each bug can lead to one less user. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

Gerald Pfeifer

14:19

On Mon 2014-10-20, Dimstar / Dominique Leuenberger wrote:

...

Thanks! The CDC got me on track of a current work-in-progress bug report with ModemManager; there was a firmware issue identified which is currently attempted to be worked around.

Cool, happy I reported this here. :)

...

We can try to add a restart-script in /usr/lib/systemd/system-sleep

50-restart_MM

...
...
...
- SNIP HERE - <<< #!/bin/sh case $1 in resume|thaw|post) /usr/bin/systemctl restart ModemManager.service > /dev/null ;; esac - SNIP HERE - <<<

Something interesting is going on here: I put that script in place, and indeed after waking up from suspend-to-RAM now there always is a new instance of ModemManager running. However, when selecting the Mobile Broadband connection from the system menu, nothing happens visually, and /var/log/NetworkManager only has NetworkManager[897]: <warn> Failed to activate 'Vodafone': Connection 'Vodafone' is not available on the device ttyACM0 at this time. NetworkManager[897]: <info> NetworkManager state is now DISCONNECTING NetworkManager[897]: <info> NetworkManager state is now DISCONNECTED When I invoke /usr/bin/systemctl restart ModemManager.service manually, however, I can then establish the connection after a second or two usually. Adding a `sleep 10` to the script did not change the picture, that is, it still does not work after suspend, and still works (not surprisingly, a sleep would not change that) when invoked directly. Gerald -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org

3484

Age (days ago)

3499

Last active (days ago)

List overview

Download

13 comments

4 participants

participants (4)

Dimstar / Dominique Leuenberger
Gerald Pfeifer
Michael Hill
Roger Luedecke

[opensuse-gnome] Some observations on Gnome 3.14 in Factory

tags

participants (4)