- User Since
- Sep 3 2017, 3:21 PM (106 w, 4 d)
Aug 2 2019
May 17 2019
Upgraded (from unstable) and no change. BTW, here's my language settings:
May 15 2019
I also checked on another system and I have the same problem (with an HP printer so I don't think it's related to the driver).
May 14 2019
No broken package on my system.
May 13 2019
May 6 2019
On kernel 5.0.7 bluetooth mouse works fine after reboot and no errors logged (still must have /usr/lib/udev/rules.d/97-hid2hci.rules /etc/udev/rules.d/hid2hci.rules modified as described).
Apr 30 2019
By refresh I meant recompile against 19.04 libs if this makes sense...
Apr 29 2019
Mar 15 2019
Working great. Thanks for the quick fix.
Mar 5 2019
Try to reboot after running usysconf. Also, make sure Solus is updated (eopkg up) and rebooted.
Jan 8 2019
No offence, I was not trying to be condescending, I just wanted to make sure you took notice of their (rather long) thread as they took years to fix this ;)
I was already a member of lpadmin and I couldn't delete the print jobs. Please take the time to read the Ubuntu bug and you'll understand what's going on. Their solution is to create a cups-pk-helper user member of lpadmin group plus:
Jan 6 2019
Jan 2 2019
Confirmed. Rolling back to osinfo-db-20161026-1-1-x86_64.eopkg as a temporary workaround.
Nov 21 2018
Nov 17 2018
Nov 16 2018
Nov 13 2018
kde-gtk-config was effectively pulled after last update. Thanks!
Nov 9 2018
Not sure if it's the same problem but here's what I have tested:
Nov 4 2018
Oct 31 2018
Problem still present on another workstation. Solution proposed still valid (systemctl enable NetworkManager-wait-online.service)
Oct 19 2018
Well, it's solved with xorg 1.20!
Oct 18 2018
I did some more tests with a Solus installation on a USB disk: on my home computer, I have the problem but gnome-shushi works fine on another computer so it looks like a display driver problem.
Oct 17 2018
On my system, I have a file named 'test' with the following content:
#!/bin/bash cd ~/.google pwd drive $1 $2 $3 $4 $5 $6 $7 $8 $9
When I view this file with Sushi, all characters are blurry.
Sep 1 2018
Solved here also. Thanks for the quick fix!
Same problem here with a Dell studio XPS. Was able to rollback with 'eopkg history -t <transaction number>'.
Jul 29 2018
Jul 16 2018
My mistake : I confused the samba service and the smb service :(
I made browsing work again by creating /etc/samba/smb.conf and adding those lines:
Jul 14 2018
May 7 2018
FYI, I tested bluez 5.48-22 (and disabled my previous workaround) : log is filled with those errors :
May 6 2018
yes: no change.
May 2 2018
I would like to reopen this request as I work with many repositories that don't support ssh (only https) so I have to use username/password for those repos.
One interesting note: the ssd drive appears in Budgie file manager applet. Digging more into this, I also found the drive appears in Nautilus under "Other places" so it's kind of hidden. As this is a camera sdcard, it might just be a "feature" of Nautilus.
Apr 28 2018
Apr 24 2018
Have a look here : https://dev.solus-project.com/T6252
Apr 22 2018
Ran usysconf to recompile apparmor profiles and now it works fine:
Apr 14 2018
I think when someone installs nautilus-share, it's because he wants to share directories and expects it works out of the box (as there's no option to enable smb in nautilus-share). At least, there should be a mention in the package description.
Apr 13 2018
I wonder if it would be a good idea to enable the smb service when nautilus-share is installed?
Apr 12 2018
Mar 2 2018
Feb 21 2018
I don't have any plugin installed other than those coming from the package.
Feb 18 2018
I tried to apply the patch to the file /usr/lib64/dracut/modules.d/90crypt/parse-crypt.sh but the file is different than the one from RH. I also tried adding 'luksname="$(str_replace "$luksname" '\' '\\')' at line 66 in the file and reboot but the boot error is still displayed. I guess the fix must be applied somewhere else or differently.
Feb 13 2018
Jan 10 2018
In my case, the error message is gone after changing rd.luks.uuid to luks.uuid. I used grub-customizer but it won't survive kernel updates.
Dec 16 2017
Problem also reported on Manjaro with kernel 4.14 and 4.15.
Dec 12 2017
Dec 10 2017
I created an automated workaround but still don't understand why it fails in udev :
Dec 4 2017
According to RedHat, the service NetworkManager-wait-online.service must be enabled :
Dec 2 2017
Upgraded to v0.7-11 of Avahi. The patch doesn't work on my system:
Nov 26 2017
You're patching faster than I can register bugs! Do you ever rest? ;)
Here's some interesting infos about the latests versions of Windows (I know, it's a Solus issue):
Nov 22 2017
@JoshStrobl I did some testing with your config and here's some observations (tested on Samba server v3.6.25):
Personally, I got same results with the latest build of gvfs against Samba 4.6 : no Windows network browsing but browsing the server for shares is ok.
@JoshStrobl I'm curious to know the config of your Samba server and what was not working with 4.7.
Nov 21 2017
Correct me if I'm wrong but I see two issues related to SMB1:
Nov 11 2017
One more thing : in my Samba server config, I had 'max protocol = SMB2'. Browsing was ok with WinXP, Win7 and old version of Ubuntu and Solus. Getting rid of this parameter in Samba, now browsing with Solus works fine.
I found this thread and it might explain why I can't browse Windows network but still be able to browse a share when I specify the server location (ex. smb://server/smb-share) in Nautilus : https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1697817
Nov 4 2017
On my Solus install, I can't display Windows networks in Nautilus (works ok in Ubuntu however) : when opening nautilus -> other locations -> windows network, I get an empty list. When I use the IP address of my Samba share, it works fine however (smb://192.168.0.1).
Actually, I had a bridge configuration with LXD (snap installation) witch might have been the cause of my problem. I now start manually my LXD bridge and my virt-manager default bridge starts fine at boot time.
Sep 3 2017
I have the same problem. Dnsmasq throws an error at boot time. Manually starting virbr0 works as a workaround. Here's some more info: