users August 2019

users@lists.fedoraproject.org

95 participants
100 discussions

OT: mounting/accessing a cheap smartwatch
by Ranjan Maitra 17 Aug '19

17 Aug '19

Dear friends, Apologies for the OT, but I have a cheap smartwatch that is conceptually bluetooth accessible and also charges via a USB dongle. I would like to access it from my Fedora 30 system and see if I can change settings, get information from my desktop. I use blueman-manager to pair the device. The device is paired fine in the sense that it shows up on the blueman-manager and also the connected icon is visible on the device, however what do I do to access the files? Also, when I go away and come back, the manager says that it is connected, but the connected icon on the device is not visible anymore so I can not make anything out of this connection, or if it was even legit in the first place. Secondly, when I plugin through USB, the battery starts charging as it should, but lsusb shows up nothing beyond what it does when it is not plugged in. Is it possible to access this smartwatch through USB? I am totally new to playing with this so would like some advice/suggestions if possible. Many thanks and best wishes, Ranjan

1 1

Boot timeout on non-existent device
by Patrick O'Callaghan 17 Aug '19

17 Aug '19

On booting, I get a pause of around 90 seconds, and the following messages in the journal: Aug 17 13:40:58 bree systemd[1]: dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.device: Job dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.device/start timed out. Aug 17 13:40:58 bree systemd[1]: Timed out waiting for device /dev/disk/by-uuid/1431e6d2-531e-46cd-8633-1cf878c6b2a1. Aug 17 13:40:58 bree systemd[1]: Dependency failed for Resume from hibernation using device /dev/disk/by-uuid/1431e6d2-531e-46cd-8633-1cf878c6b2a1. Aug 17 13:40:58 bree systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.service: Job systemd-hibernate-resume@dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd> Aug 17 13:40:58 bree systemd[1]: dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.device: Job dev-disk-by\x2duuid-1431e6d2\x2d531e\x2d46cd\x2d8633\x2d1cf878c6b2a1.device/start failed with r> However the UUID being flagged is not one of the devices I have: $ ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 10 Aug 17 13:40 15d273c5-488c-48d6-a864-e11968ee970e -> ../../sda4 lrwxrwxrwx 1 root root 10 Aug 17 13:41 1C36E53036E50B98 -> ../../sdc5 lrwxrwxrwx 1 root root 10 Aug 17 13:41 2224823A248210C9 -> ../../sdc4 lrwxrwxrwx 1 root root 10 Aug 17 13:40 4a81c9ba-d8b0-48ab-af60-714a53842c48 -> ../../sda2 lrwxrwxrwx 1 root root 10 Aug 17 13:40 6496d6da-6b7a-4cdd-9bb8-767c08d1c84e -> ../../sdb1 lrwxrwxrwx 1 root root 10 Aug 17 13:40 6881-A320 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Aug 17 13:40 6a9a800c-309b-4b69-b269-884ad495e7b9 -> ../../sda3 lrwxrwxrwx 1 root root 10 Aug 17 13:41 6d5929d8-fd35-49e6-a8bf-aab5309dad77 -> ../../sda1 lrwxrwxrwx 1 root root 10 Aug 17 13:40 DEC47E01C47DDBE9 -> ../../sdc1 So where is this coming from? The mention of "hibernation" in the third message above is curious, as I'm not using hibernation. poc

2 3

[f30] Latest wine breaks Adobe Digital Editions 2
by Marco Guazzone 17 Aug '19

17 Aug '19

Hello, I am running Fedora 30 x86_64. After upgrading wine from v. 4.5.1 to v. 4.13.5 (and wine-mono from v. 4.8.0 to v. 4.9.0), from the Fedora's updates repo, the Adobe Digital Editions 2.0.1 stopped working. Does anyone else experienced this problem (and found a workaround)? Thanks, Marco

1 0

F30 GNOME Shell not usable anymore / OsLookupColor(): Segmentation fault
by Michael Schwendt 16 Aug '19

16 Aug '19

Dunno when and why this started recently, but I'm hit hard by segfaults taking down GNOME Shell. Bugzilla knows tons of duplicate bug reports about it, dating back to F29 apparently: https://apps.fedoraproject.org/packages/xorg-x11-server/bugs/all OsLookupColor(): Segmentation fault at address 0x... Has anyone seen this earlier and knows a workaround perhaps? F30 isn't usable anymore due to those crashes.

1 1

Not built in rawhide/f31 Antimicro
by Fast OS 15 Aug '19

15 Aug '19

has been discontinued?

2 1

WiFi keeps locking up
by SternData 15 Aug '19

15 Aug '19

I still seem to be connected, but nothing works. To recover, I have to shut off WiFi then re-enable it Aug 15 13:01:03 sds-desk wpa_supplicant[1244]: wlp3s0: SME: Trying to authenticate with b0:39:56:89:67:70 (SSID='bandit' freq=5200 MHz) Aug 15 13:01:03 sds-desk kernel: wlp3s0: disconnect from AP 9c:3d:cf:7f:dc:9b for new auth to b0:39:56:89:67:70 Aug 15 13:01:04 sds-desk kernel: wlp3s0: authenticate with b0:39:56:89:67:70 Aug 15 13:01:04 sds-desk kernel: wlp3s0: send auth to b0:39:56:89:67:70 (try 1/3) Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.0138] device (wlp3s0): supplicant interface state: completed -> authenticating Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.0139] device (p2p-dev-wlp3s0): supplicant management interface state: completed -> authenticating Aug 15 13:01:04 sds-desk kernel: wlp3s0: authenticated Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: wlp3s0: Trying to associate with b0:39:56:89:67:70 (SSID='bandit' freq=5200 MHz) Aug 15 13:01:04 sds-desk kernel: wlp3s0: associate with b0:39:56:89:67:70 (try 1/3) Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.0413] device (wlp3s0): supplicant interface state: authenticating -> associating Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.0414] device (p2p-dev-wlp3s0): supplicant management interface state: authenticating -> associating Aug 15 13:01:04 sds-desk kernel: wlp3s0: RX ReassocResp from b0:39:56:89:67:70 (capab=0x1511 status=0 aid=3) Aug 15 13:01:04 sds-desk kernel: wlp3s0: associated Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/2 Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: wlp3s0: Associated with b0:39:56:89:67:70 Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.1250] device (wlp3s0): supplicant interface state: associating -> associated Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.1250] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> associated Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.1356] device (wlp3s0): supplicant interface state: associated -> 4-way handshake Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.1357] device (p2p-dev-wlp3s0): supplicant management interface state: associated -> 4-way handshake Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: wlp3s0: WPA: Key negotiation completed with b0:39:56:89:67:70 [PTK=CCMP GTK=CCMP] Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/2 Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/2 Aug 15 13:01:04 sds-desk wpa_supplicant[1244]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to b0:39:56:89:67:70 completed [id=0 id_str=] Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.1487] device (wlp3s0): supplicant interface state: 4-way handshake -> completed Aug 15 13:01:04 sds-desk NetworkManager[1088]: <info> [1565892064.1494] device (p2p-dev-wlp3s0): supplicant management interface state: 4-way handshake -> completed Aug 15 13:01:09 sds-desk org.kde.amarok.desktop[2612]: Calling appendChild() on a null node does nothing. Aug 15 13:01:13 sds-desk wpa_supplicant[1244]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-49 noise=-94 txrate=6000 Aug 15 13:02:07 sds-desk journal[1878]: Failed to query location: Connection terminated unexpectedly -- -- Steve

1 0

OSS Community Innovation Capability Research Invitation based in University of Leeds
by Sophy Guo 14 Aug '19

14 Aug '19

Dear Fedora Community Members, I am a master student based in the University of Leeds (UK), currently conducting a research in regards to investigating how open source software community culture, governance and structure, motivation of participation influence the innovation capability of OSS community. I found Fedora community is very active and supportive with members around the world, which makes it perfect for this research. I am writing to ask if you could help to take part in this research for more accurate results. This research data is to be collected via questionnaire with the anonymous link below: https://leedsubs.eu.qualtrics.com/jfe/form/SV_cUPSObEbxQqEX1b The questionnaire should take you 5-10 minutes to complete. Your participation is very important to disclose the relationship between community culture, governance structure, motivation of participation and the innovation capability of OSS community. I would very much appreciate if you could help to participate this research, and if you have any questions about the research, I am happy to answer, just e-mail me on bn18xg(a)leeds.ac.uk. Thanks a lot! Best Regards, Sophy Guo

1 0

Unable to bring up Vagrant guest after upgrade to Fedora 30
by Sudheer S 14 Aug '19

14 Aug '19

Hello, I recently upgraded from Fedora 29 to Fedora 30. I am unable to bring up a Vagrant guest. vagrant up Bringing machine 'default' up with 'libvirt' provider... Name `centos7_default` of domain about to create is already taken. Please try to run `vagrant up` command again. I launched the Virtual Machine Manager GUI and the guest is not listed there. I try to find it via virsh: virsh list --all the guest is not listed. I try to remove it by using virsh: virsh undefine centos7_default error: failed to get domain 'centos7_default' The machine is not there. How can I bring the guest OS up? Where is Vagrant looking up the names? Here's the status of the machine: vagrant status Current machine states: default not created (libvirt) The Libvirt domain is not created. Run `vagrant up` to create it. - Sudheer S

1 1

Nouveau crashes
by Javier Perez 13 Aug '19

13 Aug '19

Hi. I have been a long life fan of Nvidia cards. A few years ago I decided to skip the nvidia drivers and go with the nouveau drivers. So far so good, but they tend to freeze the desktop every few days. Lately after upgrading to F30, the desktop freezes daily or more. It is more annoying than anything else. I can ssh from another computer usually and restart display-manager, but I lose whatever I am working at at the moment. I have opened up a couple of bug reports on bugzilla with extracts from the log. My question is this. If I change to Radeon, how is the experience with those cards? Is the linux driver for these cards fine? I am not a heavy game player, mostly web browsing, and lately FreeCAD, Meshmixer though wine, PlayonLinux, user. Probably will get into Blender, therefore I might need a good video card, but not something top notch, I think. Thx -- ------------------------------ /\_/\ |O O| pepebuho(a)gmail.com ~~~~ Javier Perez ~~~~ While the night runs ~~~~ toward the day... m m Pepebuho watches from his high perch.

4 3

Viewing videos in Chrome crashes gnome shell
by SternData 13 Aug '19

13 Aug '19

I'm totally unable to track this down and when I try to report the gnome-shell crash, I get an error that ureport is unable to read the crash file. Am I the only one with this error? Any tips on how to debug this? -- -- Steve

1 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →