Re: bug in Solaar 1.1.5
I see no reason to hold up any Ubuntu release for Solaar. I'm not even sure that there is a problem with Solaar in Ubuntu. All that I have is a single report from a user - I have not looked at the distribution at all. peter On 10/17/22 18:47, Steve Langasek wrote: Hi Peter, On Tue, Oct 11, 2022 at 05:45:33AM -0400, Peter F. Patel-Schneider wrote: Hi: I'm the maintainer of Solaar. It appears that Solaar for Ubuntu was recently upgraded from version 1.1.1 to version 1.1.5. I have a report that something went wrong when he ran Solaar 1.1.5 - https://github.com/pwr-Solaar/Solaar/issues/1785 I'm not sure why he ended up with an empty ~/.config/solaar/config.yaml file. I don't see a path in the code that would make this file empty. I'm going to patch the file to handle this issue though. Unfortunately, we are now 3 days away from the Ubuntu 22.10 release. It's unclear to me if any Ubuntu Developers will step up and have an opportunity to upload a fix to this for inclusion in the 22.10 release before then. (As a member of the Release Team, I personally would definitely not!) Given that you say it's unclear how this broken config file ever happened, unless there are more users reporting the same breakage we might just have to accept this defect for 22.10. If you think it's important enough to warrant a post-release update of the package, the Ubuntu process is here: https://wiki.ubuntu.com/StableReleaseUpdates -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
bug in Solaar 1.1.5
Hi: I'm the maintainer of Solaar. It appears that Solaar for Ubuntu was recently upgraded from version 1.1.1 to version 1.1.5. I have a report that something went wrong when he ran Solaar 1.1.5 - https://github.com/pwr-Solaar/Solaar/issues/1785 I'm not sure why he ended up with an empty ~/.config/solaar/config.yaml file. I don't see a path in the code that would make this file empty. I'm going to patch the file to handle this issue though. peter -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
[Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
I have a Yoga C940, which is the precursor to the 9i. It has the soundbar and two speakers under the body of the laptop. Out of the box the body speakers did't work but there is a special BIOS for the C940 (only) that activates an amplifier for these speakers. I think that the C940 only has two-channel sound, with something (alsa?, pulse?) mixing the five channels down to two and the sound chip distributing sound to the speakers. When I look at the built-in sound card with alsamixer I see a Bass Speaker double toggle, that may be the result of the special BIOS. This toggle controls the two speakers under the laptop body. The laptop's sound is much better with the body speakers turned on, but I have heard that the sound is even better using the Windows drivers. Is the intent of the shell script to turn on the amplifier for the body speakers? If this is the case it should be possible to ditch the special BIOS, which would be nice. I'm sure that there are users who don't want to run an unofficial BIOS. The C930 has a similar setup. Should this patch fix its speaker problems? It would be nice to get some documentation on the verbs in the shell script and what they do to the sound chip. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210898]
No action yet that I can see. Does anyone know how to get this patch looked at? The current setup with its 5 second delay is getting annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210898 Title: Removable drives and media not automatically mounted/listed To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1210898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312641]
No action yet that I can see. Does anyone know how to get this patch looked at? The current setup with its 5 second delay is getting annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312641 Title: Removable drives and media do not automatically mounted at boot To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1312641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312641]
OK, done. Hopefully this will get picked up faster than your patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312641 Title: Removable drives and media do not automatically mounted at boot To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1312641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312641]
Created attachment 6191 Try to get GVolume right away and only if that fails wait for 1 second This should change the total delay from 5 seconds per partition to at most 1 second for an entire physical device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312641 Title: Removable drives and media do not automatically mounted at boot To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1312641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312641]
I see that 0.8.1 has your patch. I think that better than waiting 1 second would be to try immediately and only then wait for a bit. I modified the code accordingly, ending up with static gboolean tvm_block_device_mount_volume (TvmContext *context, GVolume *volume) { GMountOperation *mount_operation; /* check if we have a volume */ if (volume != NULL) { /* check if we can mount the volume */ if (g_volume_can_mount (volume)) { /* try to mount the volume asynchronously */ mount_operation = gtk_mount_operation_new (NULL); g_volume_mount (volume, G_MOUNT_MOUNT_NONE, mount_operation, NULL, (GAsyncReadyCallback) tvm_block_device_mount_finish, context); g_object_unref (mount_operation); } else { g_set_error (context-error, G_FILE_ERROR, G_FILE_ERROR_FAILED, _(Unable to mount the device)); /* finish processing the device */ tvm_device_handler_finished (context); } } else { g_set_error (context-error, G_FILE_ERROR, G_FILE_ERROR_FAILED, _(Could not detect the volume corresponding to the device)); /* finish processing the device */ tvm_device_handler_finished (context); } return FALSE; } static gboolean tvm_block_device_mount_retry (TvmContext *context) { GVolume *volume; volume = tvm_g_volume_monitor_get_volume_for_kind (context-monitor, G_VOLUME_IDENTIFIER_KIND_UNIX_DEVICE, g_udev_device_get_device_file (context-device)); /* if no volume then call anyway to do not-found processing */ tvm_block_device_mount_volume (context,volume); return FALSE; } static gboolean tvm_block_device_mount (TvmContext *context) { GVolume *volume; g_return_if_fail (context != NULL); /* determine the GVolume corresponding to the udev device */ volume = tvm_g_volume_monitor_get_volume_for_kind (context-monitor, G_VOLUME_IDENTIFIER_KIND_UNIX_DEVICE, g_udev_device_get_device_file (context-device)); if (volume != NULL) { tvm_block_device_mount_volume(context,volume); } else { /* clean up and try again in one second */ g_object_unref (context-monitor); context-monitor = g_volume_monitor_get (); g_timeout_add_seconds(1, (GSourceFunc) tvm_block_device_mount_retry, context); } return FALSE; } What's the best way to get this put into thunar-volman? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312641 Title: Removable drives and media do not automatically mounted at boot To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1312641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210898]
Created attachment 6191 Try to get GVolume right away and only if that fails wait for 1 second This should change the total delay from 5 seconds per partition to at most 1 second for an entire physical device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210898 Title: Removable drives and media not automatically mounted/listed To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1210898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210898]
OK, done. Hopefully this will get picked up faster than your patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210898 Title: Removable drives and media not automatically mounted/listed To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1210898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210898]
My patch that tries to get the volume up to three times, with a 1-second delay between each time, hides the problem successfully. However, a better solution would be to have thunar-volman only called when the volume has been set up. This is known, as the volume has to be set up for the icon to appear on the desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210898 Title: Removable drives and media not automatically mounted/listed To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1210898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210898]
https://bugzilla.xfce.org/show_bug.cgi?id=9193#c14 doesn't work reliably for me. It may be that it doesn't help at all, except to cause the race condition to sometimes come out the right way. The problem is still active with Thunar 1.6.6 and thunar-volman 0.8.0. I'm going to try to add some patches to the current versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210898 Title: Removable drives and media not automatically mounted/listed To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1210898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210898]
I see that 0.8.1 has your patch. I think that better than waiting 1 second would be to try immediately and only then wait for a bit. I modified the code accordingly, ending up with static gboolean tvm_block_device_mount_volume (TvmContext *context, GVolume *volume) { GMountOperation *mount_operation; /* check if we have a volume */ if (volume != NULL) { /* check if we can mount the volume */ if (g_volume_can_mount (volume)) { /* try to mount the volume asynchronously */ mount_operation = gtk_mount_operation_new (NULL); g_volume_mount (volume, G_MOUNT_MOUNT_NONE, mount_operation, NULL, (GAsyncReadyCallback) tvm_block_device_mount_finish, context); g_object_unref (mount_operation); } else { g_set_error (context-error, G_FILE_ERROR, G_FILE_ERROR_FAILED, _(Unable to mount the device)); /* finish processing the device */ tvm_device_handler_finished (context); } } else { g_set_error (context-error, G_FILE_ERROR, G_FILE_ERROR_FAILED, _(Could not detect the volume corresponding to the device)); /* finish processing the device */ tvm_device_handler_finished (context); } return FALSE; } static gboolean tvm_block_device_mount_retry (TvmContext *context) { GVolume *volume; volume = tvm_g_volume_monitor_get_volume_for_kind (context-monitor, G_VOLUME_IDENTIFIER_KIND_UNIX_DEVICE, g_udev_device_get_device_file (context-device)); /* if no volume then call anyway to do not-found processing */ tvm_block_device_mount_volume (context,volume); return FALSE; } static gboolean tvm_block_device_mount (TvmContext *context) { GVolume *volume; g_return_if_fail (context != NULL); /* determine the GVolume corresponding to the udev device */ volume = tvm_g_volume_monitor_get_volume_for_kind (context-monitor, G_VOLUME_IDENTIFIER_KIND_UNIX_DEVICE, g_udev_device_get_device_file (context-device)); if (volume != NULL) { tvm_block_device_mount_volume(context,volume); } else { /* clean up and try again in one second */ g_object_unref (context-monitor); context-monitor = g_volume_monitor_get (); g_timeout_add_seconds(1, (GSourceFunc) tvm_block_device_mount_retry, context); } return FALSE; } What's the best way to get this put into thunar-volman? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210898 Title: Removable drives and media not automatically mounted/listed To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1210898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312641]
My patch that tries to get the volume up to three times, with a 1-second delay between each time, hides the problem successfully. However, a better solution would be to have thunar-volman only called when the volume has been set up. This is known, as the volume has to be set up for the icon to appear on the desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312641 Title: Removable drives and media do not automatically mounted at boot To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1312641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312641]
https://bugzilla.xfce.org/show_bug.cgi?id=9193#c14 doesn't work reliably for me. It may be that it doesn't help at all, except to cause the race condition to sometimes come out the right way. The problem is still active with Thunar 1.6.6 and thunar-volman 0.8.0. I'm going to try to add some patches to the current versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312641 Title: Removable drives and media do not automatically mounted at boot To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1312641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210898] Re: Thunar does not automatically mount removable drives and media
This sounds very much like https://bugzilla.xfce.org/show_bug.cgi?id=9193 which has a proposed workaround. The crux of the problem is that thunar-volman tries to access information about the volume before the information is available. Adding a delay solves the problem, but not in a pleasant way. ** Bug watch added: Xfce Bugzilla #9193 https://bugzilla.xfce.org/show_bug.cgi?id=9193 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210898 Title: Thunar does not automatically mount removable drives and media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1210898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs