nvidia galaxy Geforce 210 (driver problem)

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
importford
Level 1
Level 1
Posts: 20
Joined: Sun Sep 10, 2017 9:51 pm

nvidia galaxy Geforce 210 (driver problem)

Post by importford » Thu Nov 30, 2017 5:01 am

hello guys,
I am using Linux Mint 18 "Sarah"
My PC has the Nvivia galaxy Geforce 210 video card installed.
I Installed and uninstalled the following drivers nvidia -387, -384, -381, and now I am using the nvidia-378 driver, but my PC keeps on crashing or freezing.
What can I do?
What driver should I install? Any advice? Or do I change my Linux OS?
I already tried the installation CD that comes with the video card but this driver also makes that the browser freezes. Any help?
here are the details of my installation at the moment:

I noticed that when I use the inxi-F command there is marked that I have the following graphics card: "Graphics: Card: NVIDIA Device 128b"
But this is wrong, I have the galaxy geforce 210 installed.
perhaps is this the origin of the problem.???????
Again thanks for your help guys,.... :wink:

System: Host: steve-GQ574AA-AB3-a6285l Kernel: 4.4.0-101-generic x86_64 (64 bit)
Desktop: Cinnamon 3.0.7 Distro: Linux Mint 18 Sarah
Machine: System: HP-Pavilion product: GQ574AA-AB3 a6285l serial: CNX7352FC1
Mobo: ASUSTeK model: Berkeley v: 1.xx serial: MS1C78S21905631
Bios: American Megatrends v: 5.07 date: 08/08/2007
CPU: Dual core Intel Core2 Duo E4500 (-MCP-) cache: 2048 KB
clock speeds: max: 2200 MHz 1: 1600 MHz 2: 1200 MHz
Graphics: Card: NVIDIA Device 128b
Display Server: X.org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
tty size: 80x24 Advanced Data: N/A for root
Audio: Card-1 NVIDIA GK208 HDMI/DP Audio Controller driver: snd_hda_intel
Card-2 Intel 82801I (ICH9 Family) HD Audio Controller
driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.4.0-101-generic
Network: Card: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
IF: enp0s25 state: up speed: 100 Mbps duplex: full
mac: 00:1d:60:32:5e:1c
Drives: HDD Total Size: 1015.7GB (23.3% used)
ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
ID-2: USB /dev/sdb model: DataTraveler_2.0 size: 15.5GB
Partition: ID-1: / size: 48G used: 29G (63%) fs: ext4 dev: /dev/sda3
ID-2: swap-1 size: 8.39GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 58.0C mobo: N/A gpu: 47C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 190 Uptime: 4 min Memory: 1367.6/7983.1MB
Client: Shell (sudo) inxi: 2.2.35

Citizen229
Level 5
Level 5
Posts: 811
Joined: Fri Nov 04, 2016 12:09 pm
Location: NW Ohio

Re: nvidia galaxy Geforce 210 (driver problem)

Post by Citizen229 » Thu Nov 30, 2017 5:26 am

Your 200 series card is in Legacy. I believe in the driver manager, one of the driver should be labeled legacy. If not then the driver labeled open source.
Folding@home Project
Team Linux Mint-76140
PM for info on how you can help. Or visit viewtopic.php?f=58&t=243792
Seeking GPU's, i5/7/9's , Ryzens.

User avatar
prestonR
Level 5
Level 5
Posts: 844
Joined: Wed Jan 07, 2015 12:24 pm
Location: Harare

Re: nvidia galaxy Geforce 210 (driver problem)

Post by prestonR » Fri Dec 01, 2017 3:30 pm

Citizen's correct, the 210 needs the 340.xxx legacy driver, it's a separate driver series from the 'modern' ones you're using now. Fully supported and updated but the '340.' number does not change, only the 3 trailing digits will.

More here: http://www.nvidia.com/object/IO_32667.html

importford
Level 1
Level 1
Posts: 20
Joined: Sun Sep 10, 2017 9:51 pm

Re: nvidia galaxy Geforce 210 (driver problem)

Post by importford » Sat Dec 02, 2017 3:05 am

ok, thank you.

I looked for this 340.xxx driver for Linux and
I found and downloaded this driver from nvidia:
NVIDIA-Linux-x86_64-340.104.run
but I don't know how to install this driver.
I tried to run this with several different applications, but nothing works.
can somebody explain me how I have to install this driver in Linux mint? Thanks :wink:

User avatar
prestonR
Level 5
Level 5
Posts: 844
Joined: Wed Jan 07, 2015 12:24 pm
Location: Harare

Re: nvidia galaxy Geforce 210 (driver problem)

Post by prestonR » Sat Dec 02, 2017 3:29 am

No, you shouldn't need to use external drivers, just go:
Menu >> Control Center >> Driver Manager
tick the 340.xxx option and install.

If all fails I'd also try the 304.xxx which is a more basic 'Legacy' driver for even older cards. My 9400GT should use 340.xxx but works fine on the 304.xxx too. It's unstable on the 3XX.xxx, freezes, reboot and suspend issues, some you can fix with later kernels but it's not really usable.

importford
Level 1
Level 1
Posts: 20
Joined: Sun Sep 10, 2017 9:51 pm

Re: nvidia galaxy Geforce 210 (driver problem)

Post by importford » Sat Dec 02, 2017 5:35 am

hey preston,
when I open driver manager,
the 340.xx option is not there.
I have only two options:
- nvidia 384 which is recommended
or - the nouveau display driver option.

These are the only two driver options that I receive in the driver manager.
at the moment I am using the nouveau driver option,
but linux also crashes, but less than when I use the nvidia 384.90 driver.

User avatar
prestonR
Level 5
Level 5
Posts: 844
Joined: Wed Jan 07, 2015 12:24 pm
Location: Harare

Re: nvidia galaxy Geforce 210 (driver problem)

Post by prestonR » Sat Dec 02, 2017 5:47 am

That's odd. Might be a bug.

Open synaptic and look for 'nvidia-340'.

importford
Level 1
Level 1
Posts: 20
Joined: Sun Sep 10, 2017 9:51 pm

Re: nvidia galaxy Geforce 210 (driver problem)

Post by importford » Sat Dec 02, 2017 6:18 am

yes, you were right,
I found in the synaptic that the 340 nvidia driver is installed.
nvidia-340
NVIDIA binary driver - version 340.104
I will now try to install the 304 driver that you mentioned before.
Perhaps will this driver stop the freezing of the browsers.
Thanks again for your help :wink: :wink:

User avatar
prestonR
Level 5
Level 5
Posts: 844
Joined: Wed Jan 07, 2015 12:24 pm
Location: Harare

Re: nvidia galaxy Geforce 210 (driver problem)

Post by prestonR » Sat Dec 02, 2017 7:02 am

Ok, do that. If it doesn't work best go back to 340.xxx. Also check in synaptic for other 340 packages, I've got nvidia-utils, lib32-nvidia-340-utils, lib32-opencl-nvidia-340-utils, and the kernel specific linux-headers packages installed.

If nothing helps try different kernels, mainly bring installed kernels to the latest of the respective series, so e.g. if you have 4.4. and 4.10 installed update from 4.4-53 to 4.4.-94 and 4.10.-08 to 4.10.-12, update grub, then boot the 4.10. If the problems persist use grub advanced options to boot 4.4..

JosephM
Level 5
Level 5
Posts: 963
Joined: Sun May 26, 2013 6:25 pm

Re: nvidia galaxy Geforce 210 (driver problem)

Post by JosephM » Sat Dec 02, 2017 3:32 pm

I've seen lots of reports of people having issues with some of these legacy drivers. I have a desktop with a gtx260. I haven't tested lately but after a lot of testing in the past I can say that my system is far more stable using the open source driver than these legacy drivers.
When I give opinions, they are my own. Not necessarily those of any other Linux Mint developer or the Linux Mint project as a whole.

importford
Level 1
Level 1
Posts: 20
Joined: Sun Sep 10, 2017 9:51 pm

Re: nvidia galaxy Geforce 210 (driver problem)

Post by importford » Sun Dec 03, 2017 4:29 pm

ok Preston,
I tried driver 304, but this made cinnamon crash from the boot start.
I went back to the nouveau driver because I don't know any more what to do.
here is the full list of my system,
perhaps you can see what is wrong, otherwise I will try to change the kernel.
System: Host: steve-GQ574AA-AB3-a6285l Kernel: 4.4.0-98-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.0.7 (Gtk 3.18.9-1ubuntu3.3)
Distro: Linux Mint 18 Sarah
Machine: System: HP-Pavilion product: GQ574AA-AB3 a6285l
Mobo: ASUSTeK model: Berkeley v: 1.xx
Bios: American Megatrends v: 5.07 date: 08/08/2007
CPU: Dual core Intel Core2 Duo E4500 (-MCP-) cache: 2048 KB
flags: (lm nx sse sse2 sse3 ssse3) bmips: 8777
clock speeds: max: 2200 MHz 1: 2200 MHz 2: 2200 MHz
Graphics: Card: NVIDIA Device 128b bus-ID: 02:00.0
Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa)
Resolution: 1920x1080@60.00hz
GLX Renderer: Gallium 0.4 on NV106
GLX Version: 3.0 Mesa 17.0.7 Direct Rendering: Yes
Audio: Card-1 NVIDIA GK208 HDMI/DP Audio Controller
driver: snd_hda_intel bus-ID: 02:00.1
Card-2 Intel 82801I (ICH9 Family) HD Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.4.0-98-generic
Network: Card: Intel 82566DC-2 Gigabit Network Connection
driver: e1000e v: 3.2.6-k port: b000 bus-ID: 00:19.0
IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 1000.2GB (10.5% used)
ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
Partition: ID-1: / size: 48G used: 26G (55%) fs: ext4 dev: /dev/sda3
ID-2: swap-1 size: 8.39GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 56.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 183 Uptime: 11 min Memory: 2007.6/7983.1MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35

User avatar
prestonR
Level 5
Level 5
Posts: 844
Joined: Wed Jan 07, 2015 12:24 pm
Location: Harare

Re: nvidia galaxy Geforce 210 (driver problem)

Post by prestonR » Mon Dec 04, 2017 5:58 am

That's weird,
NVIDIA Device 128b
is an Asus-made Geforce 710 from 2013 (non-legacy driver). Your processor specs fit much better the 2009 Geforce 210. Ram must be maxed for a 2009 mobo, maybe someone refurbished the box and changed the graphics? Better make sure...

Yes, try different kernels, my 2009 gt9400 has had no problems with 4.9 and 4.14. And maybe consider Mint Mate or XFCE, they'll be less demanding and should work with nouveau if the trouble with the proprietary driver persist.

importford
Level 1
Level 1
Posts: 20
Joined: Sun Sep 10, 2017 9:51 pm

Re: nvidia galaxy Geforce 210 (driver problem)

Post by importford » Mon Dec 04, 2017 10:45 pm

NVIDIA Device 128b
is an Asus-made Geforce 710 from 2013 (non-legacy driver)
yes, this is my second video driver in this PC
I upgraded to linux mint 18.3, but still freezes, 2 times in the last 20 minutes.
But now I have system log, perhaps this will help to find why my linux keeps on freezing and crashing.
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l systemd[1]: Started LSB: Start NTP daemon.
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l systemd[1]: Reached target Multi-User System.
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l systemd[1]: Reached target Graphical Interface.
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: proto: precision = 0.110 usec (-23)
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: Listen and drop on 0 v6wildcard [::]:123
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l systemd[1]: Starting Update UTMP about System Runlevel Changes...
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l systemd[1]: Started Stop ureadahead data collection 45s after completed startup.
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: Listen normally on 2 lo 127.0.0.1:123
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: Listen normally on 3 enp0s25 192.168.1.6:123
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: Listen normally on 4 lo [::1]:123
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: Listen normally on 5 enp0s25 [2403:6200:8820:fab8:34d0:c067:52a0:75b8]:123
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: Listen normally on 6 enp0s25 [2403:6200:8820:fab8:90e4:3631:8ff9:f46c]:123
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: Listen normally on 7 enp0s25 [fe80::5ef9:b93:e5be:8d0f%2]:123
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l ntpd[1786]: Listening on routing socket on fd #24 for interface updates
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l systemd[1]: Started Update UTMP about System Runlevel Changes.
Dec 5 09:29:25 steve-GQ574AA-AB3-a6285l systemd[1]: Startup finished in 9.408s (kernel) + 36.449s (userspace) = 45.857s.
Dec 5 09:29:26 steve-GQ574AA-AB3-a6285l dhclient[1310]: XMT: Info-Request on enp0s25, interval 14480ms.
Dec 5 09:29:26 steve-GQ574AA-AB3-a6285l kernel: [ 46.706915] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=188.166.26.63 DST=192.168.1.6 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=25193 DF PROTO=TCP SPT=443 DPT=58488 WINDOW=57 RES=0x00 ACK FIN URGP=0
Dec 5 09:29:26 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 203.158.247.150
Dec 5 09:29:27 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 203.158.118.2
Dec 5 09:29:27 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 45.127.113.2
Dec 5 09:29:27 steve-GQ574AA-AB3-a6285l kernel: [ 48.148471] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.137.173 DST=192.168.1.6 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=55432 DF PROTO=TCP SPT=443 DPT=44470 WINDOW=57 RES=0x00 ACK FIN URGP=0
Dec 5 09:29:28 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 144.76.14.132
Dec 5 09:29:28 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 2401:5700:100:503::1813
Dec 5 09:29:29 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 2001:3c8:e10e:399f::20
Dec 5 09:29:29 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 185.103.216.7
Dec 5 09:29:29 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 27.124.125.251
Dec 5 09:29:30 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 85.30.248.106
Dec 5 09:29:30 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 203.159.70.33
Dec 5 09:29:30 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 195.186.1.101
Dec 5 09:29:30 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 2001:67c:1560:8003::c7
Dec 5 09:29:31 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 2001:67c:1560:8003::c8
Dec 5 09:29:31 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 80.190.97.205
Dec 5 09:29:31 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 203.158.118.2
Dec 5 09:29:32 steve-GQ574AA-AB3-a6285l ntpd[1786]: Soliciting pool server 120.25.108.11
Dec 5 09:29:33 steve-GQ574AA-AB3-a6285l systemd[1354]: Time has been changed
Dec 5 09:29:33 steve-GQ574AA-AB3-a6285l systemd[1]: Time has been changed
Dec 5 09:29:33 steve-GQ574AA-AB3-a6285l ntpd[1786]: receive: Unexpected origin timestamp from 45.127.113.2
Dec 5 09:29:33 steve-GQ574AA-AB3-a6285l ntpd[1786]: receive: Unexpected origin timestamp from 195.186.1.101
Dec 5 09:29:34 steve-GQ574AA-AB3-a6285l kernel: [ 55.209809] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=188.166.87.191 DST=192.168.1.6 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=49306 DF PROTO=TCP SPT=443 DPT=42436 WINDOW=57 RES=0x00 ACK FIN URGP=0
Dec 5 09:29:34 steve-GQ574AA-AB3-a6285l kernel: [ 55.493347] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=136 TOS=0x00 PREC=0x00 TTL=41 ID=25803 DF PROTO=TCP SPT=443 DPT=59002 WINDOW=96 RES=0x00 ACK PSH URGP=0
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l org.gnome.keyring.SystemPrompter[1505]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Dec 5 09:29:36 steve-GQ574AA-AB3-a6285l kernel: [ 56.983437] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=136 TOS=0x00 PREC=0x00 TTL=46 ID=39252 DF PROTO=TCP SPT=443 DPT=59146 WINDOW=74 RES=0x00 ACK PSH URGP=0
Dec 5 09:29:36 steve-GQ574AA-AB3-a6285l kernel: [ 56.983472] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=83 TOS=0x00 PREC=0x00 TTL=46 ID=39253 DF PROTO=TCP SPT=443 DPT=59146 WINDOW=74 RES=0x00 ACK PSH URGP=0
Dec 5 09:29:36 steve-GQ574AA-AB3-a6285l kernel: [ 57.589850] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=136 TOS=0x00 PREC=0x00 TTL=46 ID=39255 DF PROTO=TCP SPT=443 DPT=59146 WINDOW=74 RES=0x00 ACK PSH URGP=0
Dec 5 09:29:37 steve-GQ574AA-AB3-a6285l kernel: [ 58.235893] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=136 TOS=0x00 PREC=0x00 TTL=46 ID=53237 DF PROTO=TCP SPT=443 DPT=59152 WINDOW=89 RES=0x00 ACK PSH URGP=0
Dec 5 09:29:37 steve-GQ574AA-AB3-a6285l kernel: [ 58.235926] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=83 TOS=0x00 PREC=0x00 TTL=46 ID=53238 DF PROTO=TCP SPT=443 DPT=59152 WINDOW=89 RES=0x00 ACK PSH URGP=0
Dec 5 09:29:37 steve-GQ574AA-AB3-a6285l kernel: [ 58.809880] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=136 TOS=0x00 PREC=0x00 TTL=46 ID=39256 DF PROTO=TCP SPT=443 DPT=59146 WINDOW=74 RES=0x00 ACK PSH URGP=0
Dec 5 09:29:38 steve-GQ574AA-AB3-a6285l kernel: [ 58.846385] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=136 TOS=0x00 PREC=0x00 TTL=46 ID=53240 DF PROTO=TCP SPT=443 DPT=59152 WINDOW=89 RES=0x00 ACK PSH URGP=0
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l dhclient[1310]: XMT: Info-Request on enp0s25, interval 29550ms.
Dec 5 09:29:42 steve-GQ574AA-AB3-a6285l pulseaudio[1554]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Dec 5 09:29:42 steve-GQ574AA-AB3-a6285l dbus[870]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service'
Dec 5 09:29:42 steve-GQ574AA-AB3-a6285l systemd[1]: Starting flatpak system helper...
Dec 5 09:29:43 steve-GQ574AA-AB3-a6285l dbus[870]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper'
Dec 5 09:29:43 steve-GQ574AA-AB3-a6285l systemd[1]: Started flatpak system helper.
Dec 5 09:29:52 steve-GQ574AA-AB3-a6285l kernel: [ 73.319134] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=188.226.226.40 DST=192.168.1.6 LEN=1492 TOS=0x00 PREC=0x00 TTL=46 ID=34731 DF PROTO=TCP SPT=443 DPT=39068 WINDOW=61 RES=0x00 ACK URGP=0
Dec 5 09:29:57 steve-GQ574AA-AB3-a6285l NetworkManager[907]: <warn> [1512440997.1956] dhcp6 (enp0s25): request timed out
Dec 5 09:29:57 steve-GQ574AA-AB3-a6285l NetworkManager[907]: <info> [1512440997.1956] dhcp6 (enp0s25): state changed unknown -> timeout
Dec 5 09:29:57 steve-GQ574AA-AB3-a6285l NetworkManager[907]: <info> [1512440997.1964] dhcp6 (enp0s25): canceled DHCP transaction, DHCP client pid 1310
Dec 5 09:29:57 steve-GQ574AA-AB3-a6285l NetworkManager[907]: <info> [1512440997.1964] dhcp6 (enp0s25): state changed timeout -> done
Dec 5 09:30:09 steve-GQ574AA-AB3-a6285l kernel: [ 90.691725] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=136 TOS=0x00 PREC=0x00 TTL=41 ID=25804 DF PROTO=TCP SPT=443 DPT=59002 WINDOW=96 RES=0x00 ACK PSH URGP=0
Dec 5 09:30:10 steve-GQ574AA-AB3-a6285l systemd[1]: Starting Stop ureadahead data collection...
Dec 5 09:30:10 steve-GQ574AA-AB3-a6285l systemd[1]: Stopped Read required files in advance.
Dec 5 09:30:10 steve-GQ574AA-AB3-a6285l systemd[1]: Started Stop ureadahead data collection.
Dec 5 09:30:53 steve-GQ574AA-AB3-a6285l kernel: [ 134.328113] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=136 TOS=0x00 PREC=0x00 TTL=46 ID=39261 DF PROTO=TCP SPT=443 DPT=59146 WINDOW=74 RES=0x00 ACK PSH URGP=0
Dec 5 09:30:55 steve-GQ574AA-AB3-a6285l kernel: [ 136.120660] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=136 TOS=0x00 PREC=0x00 TTL=46 ID=53246 DF PROTO=TCP SPT=443 DPT=59152 WINDOW=89 RES=0x00 ACK PSH URGP=0
Dec 5 09:32:19 steve-GQ574AA-AB3-a6285l kernel: [ 220.224162] [UFW BLOCK] IN=enp0s25 OUT= MAC=00:1d:60:32:5e:1c:64:13:6c:2e:bd:ec:08:00 SRC=178.62.230.201 DST=192.168.1.6 LEN=132 TOS=0x00 PREC=0x00 TTL=46 ID=11678 DF PROTO=TCP SPT=443 DPT=57394 WINDOW=105 RES=0x00 ACK PSH URGP=0
Dec 5 09:32:38 steve-GQ574AA-AB3-a6285l kernel: [ 239.632873] perf interrupt took too long (2520 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Dec 5 09:34:59 steve-GQ574AA-AB3-a6285l kernel: [ 379.947388] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Dec 5 09:38:37 steve-GQ574AA-AB3-a6285l ntpd[1786]: 195.186.1.101 local addr 192.168.1.6 -> <null>
Dec 5 09:38:39 steve-GQ574AA-AB3-a6285l ntpd[1786]: 85.30.248.106 local addr 192.168.1.6 -> <null>

importford
Level 1
Level 1
Posts: 20
Joined: Sun Sep 10, 2017 9:51 pm

Re: nvidia galaxy Geforce 210 (driver problem)

Post by importford » Mon Dec 04, 2017 10:48 pm

this is the auth.log of 2 crahes:
Dec 5 09:29:01 steve-GQ574AA-AB3-a6285l systemd-logind[910]: New seat seat0.
Dec 5 09:29:03 steve-GQ574AA-AB3-a6285l CRON[985]: pam_unix(cron:session): session opened for user root by (uid=0)
Dec 5 09:29:13 steve-GQ574AA-AB3-a6285l mdm[1328]: pam_unix(mdm-autologin:session): session opened for user steve by (uid=0)
Dec 5 09:29:13 steve-GQ574AA-AB3-a6285l systemd-logind[910]: New session c1 of user steve.
Dec 5 09:29:13 steve-GQ574AA-AB3-a6285l systemd: pam_unix(systemd-user:session): session opened for user steve by (uid=0)
Dec 5 09:29:13 steve-GQ574AA-AB3-a6285l mdm[1328]: pam_ck_connector(mdm-autologin:session): nox11 mode, ignoring PAM_TTY :0
Dec 5 09:29:15 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1549]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Dec 5 09:29:15 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1548]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Dec 5 09:29:15 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1550]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Dec 5 09:29:19 steve-GQ574AA-AB3-a6285l polkitd(authority=local): Registered Authentication Agent for unix-session:c1 (system bus name :1.46 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: bus acquired: org.gnome.keyring.SystemPrompter
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: registering prompter
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: bus acquired: org.gnome.keyring.PrivatePrompter
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: creating new GcrPromptDialog prompt
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: automatically selecting secret exchange protocol
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: generating public key
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: beginning the secret exchange: [sx-aes-1]\npublic=VwqRYmsBoWSYgCeF9WL+KedKuuzUelvgC7whjeoWm9kQXMSDWgiT+p+zPfwmp/JTpoca9/C1SDn4fqovYOlPzdih/EkBpi7c8pVmCbDOYBsrFjYH1w1Dqa0OKpWR0+aJPf1sEEzH5w6bTbLR+pVcbQDv5rHD9bKtHiLmJ1t4eHUVW8jn0pdC9uxdxfQqRExDk13WsTBMznDM3lE6r0M4kKA42w1tkIQg2F0z7Ytkdy9gTjeMJLss8K4Cfdqop8D1\n
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: acquired name: org.gnome.keyring.SystemPrompter
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: acquired name: org.gnome.keyring.PrivatePrompter
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: receiving secret exchange: [sx-aes-1]\npublic=WkfYeI2YPPPTP35KwovGWtlhGkbKYzOseXH6+mTfxa5iItY1a0UkqX9n6eUo6Z3sHcFsnDbkwWf+RrNe6tK7wwqubuhg5yrK6JDGb7z9ZYxNKbxoEgg4sADgBrDLfDuB2SxxmZDmx3+88NGwT9C0anCuv1e1C6e2AvKmgpZ4YwbXTOClF2aWGJKp6aa3s1+ohJOwxDHfZ6hRRnkgLLYebruwtHHaPMBi6uGwufkdqdCgTh138YKnxgmoRtqZ6v0H\n
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: deriving shared transport key
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: deriving transport key
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: starting password prompt for callback /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:35 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gtk: GtkDialog mapped without a transient parent. This is discouraged.
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: completed password prompt for callback :1.6@/org/gnome/keyring/Prompt/p2
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: encrypting data
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: sending the secret exchange: [sx-aes-1]\npublic=VwqRYmsBoWSYgCeF9WL+KedKuuzUelvgC7whjeoWm9kQXMSDWgiT+p+zPfwmp/JTpoca9/C1SDn4fqovYOlPzdih/EkBpi7c8pVmCbDOYBsrFjYH1w1Dqa0OKpWR0+aJPf1sEEzH5w6bTbLR+pVcbQDv5rHD9bKtHiLmJ1t4eHUVW8jn0pdC9uxdxfQqRExDk13WsTBMznDM3lE6r0M4kKA42w1tkIQg2F0z7Ytkdy9gTjeMJLss8K4Cfdqop8D1\nsecret=rm7YEWrpKA0HAZySuX9VpQ==\niv=y0qj/Xm5xIBT/I/YWOk/hQ==\n
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1550]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: closing the prompt
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p2@:1.6
Dec 5 09:29:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: calling the PromptDone method on /org/gnome/keyring/Prompt/p2@:1.6, and ignoring reply
Dec 5 09:29:41 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1550]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered
Dec 5 09:29:41 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1550]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered
Dec 5 09:29:42 steve-GQ574AA-AB3-a6285l dbus[870]: [system] Failed to activate service 'org.bluez': timed out
Dec 5 09:29:51 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: 10 second inactivity timeout, quitting
Dec 5 09:29:51 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: unregistering prompter
Dec 5 09:29:51 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: disposing prompter
Dec 5 09:29:51 steve-GQ574AA-AB3-a6285l gcr-prompter[2080]: Gcr: finalizing prompter
Dec 5 09:41:01 steve-GQ574AA-AB3-a6285l systemd-logind[948]: New seat seat0.
Dec 5 09:41:03 steve-GQ574AA-AB3-a6285l CRON[998]: pam_unix(cron:session): session opened for user root by (uid=0)
Dec 5 09:41:13 steve-GQ574AA-AB3-a6285l mdm[1341]: pam_unix(mdm-autologin:session): session opened for user steve by (uid=0)
Dec 5 09:41:13 steve-GQ574AA-AB3-a6285l systemd-logind[948]: New session c1 of user steve.
Dec 5 09:41:13 steve-GQ574AA-AB3-a6285l systemd: pam_unix(systemd-user:session): session opened for user steve by (uid=0)
Dec 5 09:41:13 steve-GQ574AA-AB3-a6285l mdm[1341]: pam_ck_connector(mdm-autologin:session): nox11 mode, ignoring PAM_TTY :0
Dec 5 09:41:14 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1555]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Dec 5 09:41:14 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1554]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Dec 5 09:41:14 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1553]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Dec 5 09:41:18 steve-GQ574AA-AB3-a6285l polkitd(authority=local): Registered Authentication Agent for unix-session:c1 (system bus name :1.47 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: bus acquired: org.gnome.keyring.SystemPrompter
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: registering prompter
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: bus acquired: org.gnome.keyring.PrivatePrompter
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: creating new GcrPromptDialog prompt
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: automatically selecting secret exchange protocol
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: generating public key
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: beginning the secret exchange: [sx-aes-1]\npublic=cmFFoomlkorJ8puayQcTxeTfwb/jLUDAbM2toGRRGY27qeWUfSUrWb6o9sH5mvgZiqH+sC7EzeOPZ3m0t8qemAsrBtPmCbwNtjCW+SCnXOerxbbsWCeteHlIpitJFUxUaB7M6yWLRJpoIQxl5VfFRDMVxBwu6vYKGedJhkhbfcMbMbO6MKltlzZTAP3o8/49hEI3Pa6kV+TbZLO2c8SD8xn3B+5UI1VWzQoZtyBgGZGNO1VEDROXpCLvw8pY7LPy\n
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: acquired name: org.gnome.keyring.SystemPrompter
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: acquired name: org.gnome.keyring.PrivatePrompter
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: receiving secret exchange: [sx-aes-1]\npublic=iwBzU52a692s/GFgfUIQlSVMeTs73C3CxrlLUCAiKsE4qL2zc69vOqIGHvbdD3UE+CGoT4ns7Byj60itVBmznnQJQFBRWTaUdzE1sOVybIk5DsCqpV9e/KVHa6pbosx1+x3pYeMy59yP7/cntiXGUbaXFY2WOGo6BNwkPgnxiw/y39iu04R2P8yTOpKG7D9ZZW+1W6FC/usKAJ8uaQejd7XLchU6hzxuNzUDh6CbzZW3KvhhzgH/KoUkzCTzQE+p\n
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: deriving shared transport key
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: deriving transport key
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: starting password prompt for callback /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:40 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gtk: GtkDialog mapped without a transient parent. This is discouraged.
Dec 5 09:41:41 steve-GQ574AA-AB3-a6285l dbus[914]: [system] Failed to activate service 'org.bluez': timed out
Dec 5 09:41:45 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: completed password prompt for callback :1.5@/org/gnome/keyring/Prompt/p2
Dec 5 09:41:45 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: encrypting data
Dec 5 09:41:45 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: sending the secret exchange: [sx-aes-1]\npublic=cmFFoomlkorJ8puayQcTxeTfwb/jLUDAbM2toGRRGY27qeWUfSUrWb6o9sH5mvgZiqH+sC7EzeOPZ3m0t8qemAsrBtPmCbwNtjCW+SCnXOerxbbsWCeteHlIpitJFUxUaB7M6yWLRJpoIQxl5VfFRDMVxBwu6vYKGedJhkhbfcMbMbO6MKltlzZTAP3o8/49hEI3Pa6kV+TbZLO2c8SD8xn3B+5UI1VWzQoZtyBgGZGNO1VEDROXpCLvw8pY7LPy\nsecret=MkAwWavl0xCiv5LzuL3pLA==\niv=ljDDvUOP7CKvVAG2RASmyg==\n
Dec 5 09:41:45 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:45 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1555]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: closing the prompt
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p2@:1.5
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: calling the PromptDone method on /org/gnome/keyring/Prompt/p2@:1.5, and ignoring reply
Dec 5 09:41:46 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1555]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered
Dec 5 09:41:47 steve-GQ574AA-AB3-a6285l gnome-keyring-daemon[1555]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered
Dec 5 09:41:56 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: 10 second inactivity timeout, quitting
Dec 5 09:41:56 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: unregistering prompter
Dec 5 09:41:56 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: disposing prompter
Dec 5 09:41:56 steve-GQ574AA-AB3-a6285l gcr-prompter[2071]: Gcr: finalizing prompter

Post Reply

Return to “Hardware Support”