[SOLVED]? pop up explained?

stevengarland · Post by **stevengarland** » Sun May 05, 2019 10:25 am

At least several times while I am on my computer this message pops up:

"Error creating directory /media/steven/2064a504-67d0-45da-b848-0278f89fb65c: Permission denied"

I suspect that it has to do with my second hard drive /dev/sdb-1.

Part of the mystery here is that I already do use this drive for storage and manual backup.

Ideas?

Thanks

rene · Post by **rene** » Sun May 05, 2019 10:48 am

Is is correlated with the external drive going into / coming out of sleep (i.e., it spinning down/up)? Correlated with stuff appearing in dmesg concerning the drive? As to latter. keep a terminal on screen that's running sudo journalctl -b -f and see which messages appear when the popup does.

stevengarland · Post by **stevengarland** » Mon May 06, 2019 9:19 am

Good idea. I am watching and I see two main things. One is CLAM, running, updates, etc. Then there is a error message (in red) "failed to create /var/spool/cups/tmp/.hplip"

I have a Canon printer running on CUPS. I leave it turned off unless I want to print something. When I installed it I downloaded some Canon set up files that were supposedly compatible with Linux. They never really worked but I still had the files in download. I have gotten rid of those files now and will see what happens with the popup message. Most of what I see on terminal involves CUPS.

stevengarland · Post by **stevengarland** » Tue May 07, 2019 8:53 am

Taking out the Canon downloads seems to cut the pop up incidents way down. Now I am seeing a message on the running terminal saying something about "NKDomain potential DNS violation" that seems to cause a pop up.

Ideas please. Thanks

rene · Post by **rene** » Tue May 07, 2019 9:13 am

NX- rather than NKDomain I suppose; I've seen that message from systemd-resolved. It might be due to having /etc/resolv.conf be --- or conversely not be --- a link to /run/systemd/resolve/resolv.conf; check if it is now with ls -l /etc/resolv.conf.

However, the standard setup there seems to have changed again recently or I am remembering things wrong. On what I believe is a vanilla 19.1 install here I see /etc/resolv.conf being a regular file (managed by NetworkManager) although I distinctly remember that the OOTB situation on Mint 18.3 was it being a link to under /run.

Checking what's in fact OOTB at the moment will need to wait for me to install a 19.1 system from scratch into a VM; can't be sure whether or not I changed something myself. Can't do that right now though...

stevengarland · Post by **stevengarland** » Wed May 08, 2019 9:24 am

This is what I get

wxrwxrwx 1 root root 39 Mar 4 14:55 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
steven@steven-Studio-1747:~$

I also noted another item causing a pop up. Gnome blue tooth had a problem. O just got rid of it as I don't need it.

rene · Post by **rene** » Wed May 08, 2019 10:48 am

Okay. And just so as to confirm I suppose that

Code: Select all

cat /run/systemd/resolve/stub-resolv.conf

has "nameserver 127.0.0.53" listed as its only server. Even though on my expected vanilla 19.1 system here /etc/resolv.conf is as mentioned a NetworkManager-managed actual file rather than link, that would be content-wise same as here. In one sense that means that I can't say there's anything actually wrong there, but it does leave room for an attempt. You can try

Code: Select all

sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

A repeat of the above cat should then show (an) upstream server(s) only (possibly your router, possibly ISP servers). Reboot and doublecheck with again that ls -l that the link is still set to /run/systemd/resolve/resolv.conf rather than the stub-resolv.conf one and see if anything has improved. If not, feel free to restore it to previous state with

Code: Select all

sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

and reboot once more.

As mentioned, and/but although details escape me, I remember the "Potential DNS Violation" error from going through the systemd-resolved stub resolverat some point and this may as such be a direct reply to that actual NXDomain thingy --- but I do of course note that we're now all of a sudden doing something completely different than how this thread started, and that the gnome-bluetooth is a different one again. As such it might not in fact be a very good idea to slap random fixes on random issues, if you have an underlying bigger issue. Identifying such would require more structure in the issues/question though.

stevengarland · Post by **stevengarland** » Thu May 09, 2019 8:56 am

OK.
I did the first terminal command and indeed saw the address you expected. I did the second one and the address did not change. If you want the output I will send it.

Things are much better than they were regarding pop-up frequency, but I am still curious as to the cause.

stevengarland · Post by **stevengarland** » Thu May 09, 2019 8:58 am

Output of ls-l

steven@steven-Studio-1747:~$ ls -l
total 44
drwx------ 2 steven steven 4096 Mar 5 08:41 BRF
drwxr-xr-x 2 steven steven 4096 Mar 8 11:14 Desktop
drwxr-xr-x 3 steven steven 4096 Apr 25 09:59 Documents
drwxr-xr-x 2 steven steven 4096 May 7 08:49 Downloads
drwxrwxr-x 2 steven steven 4096 Mar 15 09:38 history
drwxr-xr-x 2 steven steven 4096 Mar 4 15:05 Music
drwx------ 2 steven steven 4096 Mar 16 09:00 PDF
drwxr-xr-x 2 steven steven 4096 Mar 4 15:05 Pictures
drwxr-xr-x 2 steven steven 4096 Mar 4 15:05 Public
drwxr-xr-x 2 steven steven 4096 Mar 4 15:05 Templates
-rw-r--r-- 1 steven steven 0 Mar 8 18:07 troubleshoot-logs.txt
drwxr-xr-x 2 steven steven 4096 Mar 4 15:05 Videos

rene · Post by **rene** » Thu May 09, 2019 12:34 pm

That's an ls -l of your home directory; I was referring to the previously mentioned ls -l /etc/resolv.conf so as to doublecheck that the mentioned ln -sf command had updated it to now point to /run/systemd/resolve/resolv.conf rather than /run/systemd/resolve/stub-resolv.conf. If "the address did not change" in the sense of cat /etc/resolv.conf still showing 127.0.0.53 after the mentioned ln -sf command then this would be unexpected.

stevengarland · Post by **stevengarland** » Thu May 09, 2019 2:29 pm

I did the things that you suggest in your post of 5/8 10:48.

I get 127.0.0.53 before and after the terminal commands and after rebooting.. Perhaps I am not understanding what is supposed to happen?

rene · Post by **rene** » Thu May 09, 2019 2:52 pm

Please paste the result of ls -l /etc/resolv.conf.

stevengarland · Post by **stevengarland** » Fri May 10, 2019 9:26 am

steven@steven-Studio-1747:~$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 32 May 9 14:18 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

rene · Post by **rene** » Fri May 10, 2019 10:47 am

Okay, so the ln command worked... but you say that cat /etc/resolv.conf still lists (only) 127.0.0.53?

That seems impossible: /run/systemd/resolve/resolv.conf should list upstream server(s) --- such as for example 192.168.0.1 if your router is a DNS server/forwarder, or your ISP's DNS servers --- with only the /run/systemd/resolve/stub-resolv.com one listing the 127.0.0.53 address (it's an address on your own machine).

What we are doing is: I remembered seeing the NXDomain issue at some point when using the systemd-resolved stub resolver, i.e., 127.0.0.53. As such, I wanted to provide you with a possible quick fix to or test of that particular issue by having you use the upstream server(s) directly (and as said, even though that's of course rather different than what started this thread, meaning this might not be all that applicable in the first place).

You still seeing 127.0.0.53 from the command in the first line just seems impossible. If indeed it doesn't, goal achieved, with you needing to be the judge on whether or not it actually helped anything. If not, see above for how to restore the original situation if you want.

stevengarland · Post by **stevengarland** » Fri May 10, 2019 7:07 pm

This last command is not the same as before. It yields:
teven@steven-Studio-1747:~$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 75.75.75.75
# Too many DNS servers configured, the following entries may be ignored.
nameserver 2001:558:feed::1
nameserver 2001:558:feed::2
search hsd1.mi.comcast.net

So indeed something changed. We shall see what happens. Also I found that org.blueszwas till a problem so I went to Synaptic and found more to delete..

Many thanks!

stevengarland · Post by **stevengarland** » Sat May 11, 2019 9:20 am

I kept a close eye on terminal today in order to see the very instant when the pop-up popped. Here's what I saw:

May 11 09:15:06 steven-Studio-1747 gnome-terminal-[15245]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
May 11 09:15:43 steven-Studio-1747 gnome-terminal-[15245]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
May 11 09:16:01 steven-Studio-1747 gnome-terminal-[15245]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed

Ideas?

stevengarland · Post by **stevengarland** » Sat May 11, 2019 1:34 pm

Heres another item that seems to cause a popup:

May 11 13:12:55 steven-Studio-1747 gnome-keyring-daemon[1232]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
May 11 13:14:55 steven-Studio-1747 PackageKit[2342]: resolve transaction /57_dedcbbda from uid 1000 finished with success after 2003ms

rene · Post by **rene** » Sun May 12, 2019 5:25 am

Both those would not cause a graphical "Error creating directory" popup. What I thought we'd maybe see is your external drive (disconnecting and, but not in a orderly fashion) reconnecting, causing a file-manager automount attempt even though the system believed it to in fact still be mounted already. If you are not seeing something like:

Code: Select all

mei 12 11:18:46 hp8k kernel: usb 2-6: New USB device found, idVendor=054c, idProduct=0243
mei 12 11:18:46 hp8k kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
mei 12 11:18:46 hp8k kernel: usb 2-6: Product: Storage Media
mei 12 11:18:46 hp8k kernel: usb 2-6: Manufacturer: Sony
mei 12 11:18:46 hp8k kernel: usb 2-6: SerialNumber: 8F11083001618
mei 12 11:18:46 hp8k mtp-probe[4165]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6"
mei 12 11:18:46 hp8k mtp-probe[4165]: bus: 2, device: 2 was not an MTP device
mei 12 11:18:46 hp8k kernel: usb-storage 2-6:1.0: USB Mass Storage device detected
mei 12 11:18:46 hp8k kernel: scsi host6: usb-storage 2-6:1.0
mei 12 11:18:46 hp8k kernel: usbcore: registered new interface driver usb-storage
mei 12 11:18:46 hp8k kernel: usbcore: registered new interface driver uas
mei 12 11:18:46 hp8k upowerd[1088]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6
mei 12 11:18:46 hp8k upowerd[1088]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0
mei 12 11:18:48 hp8k kernel: scsi 6:0:0:0: Direct-Access     Sony     Storage Media    0100 PQ: 0 ANSI: 0 CCS
mei 12 11:18:48 hp8k kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
mei 12 11:18:48 hp8k kernel: sd 6:0:0:0: [sdb] 7831552 512-byte logical blocks: (4.01 GB/3.73 GiB)
mei 12 11:18:48 hp8k kernel: sd 6:0:0:0: [sdb] Write Protect is off
mei 12 11:18:48 hp8k kernel: sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
mei 12 11:18:48 hp8k kernel: sd 6:0:0:0: [sdb] No Caching mode page found
mei 12 11:18:48 hp8k kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
mei 12 11:18:49 hp8k kernel:  sdb: sdb1
mei 12 11:18:49 hp8k kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
mei 12 11:18:59 hp8k systemd[1]: Created slice system-clean\x2dmount\x2dpoint.slice.
mei 12 11:18:59 hp8k systemd[1]: Started Clean the /media/rene/USM4GLX mount point.

then my suspicion would seem not relevant.

Still. Is is USB2 or USB3 drive? In a USB2 or USB3 port? With its own or just any USB cable? And possibly most relevant, with its own external power supply or bus-powered? As in, USB3 ports provide for more power; if you have a USB3 drive in a USB2 port you may see issues. Or when using a USB2 cable...

stevengarland · Post by **stevengarland** » Sun May 12, 2019 8:55 am

Since I am still getting a pop up at least once a session I did revert back to the original address.

I am not using any usb port other than the ports my printer and mouse are plugged into. That's the same port I have used these same ports for for 10+ years..

The most frequent item I see with a pop up is the gnome keyring message cited earlier. I am using a password and it seems to work just fine.

For a time after I dumped windows for Mint I did not have popups. They started after (with help in this forum) I got my second hard drive (sdb-1) active so as to use it for storage space.

Just fishing here for ideas.

rene · Post by **rene** » Sun May 12, 2019 9:48 am

Oh. So the second hard drive is not in fact a USB drive I gather. If it's related to the "cannot create" directory pop-up it seems something thinks it is (well, thinks it's a removable drive). Never seen that for an internal SATA drive. Something weird going on with adapters? I suppose the output of blkid and/or mount wil at least let us compare the UUID.

Linux Mint Forums

[SOLVED]? pop up explained?

[SOLVED]? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?

Re: ? pop up explained?