[Bug 1886113] Re: snap-store Does Not Run with XAUTHORITY error
If I understand things, the path /home/$USER is not valid if /home is a symlink or when home directories are not on root. For example most corporate set-ups uses something like: /export/home/$USER Sounds like that will foil the 'dumb smart software too. I refute the proposition that ... "symlinking an alternate home directory location" This is not an alternate. The semantics are straightforward: "/home/$USER/", it is a regular Unix path name. The flaw here lies in the over-reach to resolve perfectly legitimate human use file paths into machnine talk. When in truth use of the given (legitimate) path of "/home/$USER" will or should work in all cases. For comparison; I do not expect a compile error when the expression "i +=2;" isn't written as "i = i+2;" And that is more or less what has happened here. A correct file path is rejected because of some internal scruples that have not bearing on usability or function. I'm not sure which part of the stack is dissatisfied with the "/home/$USER" pattern. If you know please post the module(s) if you'd like. It looks like snap-s can not be used at with this limitation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886113 Title: snap-store Does Not Run with XAUTHORITY error To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1886113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888452] Re: Unreadable text Terminator on Ubuntu 20.04
* This has been found that this error was caused by a MISSING FONT * Someplace during the Ubuntu 19.10 to Ubuntu 20.04 upgrade process the font Courier New was completely removed. * It is not clear what the use-case would be to removea font in the first place. * Nothing in the removed packages list indicates that this font was removed. It would be useful for the terminal to report an error on a missing font file. unfortunately there is no installer for me to reinstall terminator for 20.04 :-( Hoping tha tcomes along soon. ** Changed in: terminator (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888452 Title: Unreadable text Terminator on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1888452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888458] Re: text not displaying ubuntu 20.04
* It has been found that this error was caused by a MISSING FONT * Someplace during the Ubuntu 19.10 to Ubuntu 20.04 upgrade process the font Courier New was completely removed. * It is not clear what the use-case would be to removea font in the first place. * Nothing in the removed packages list indicates that this font was removed. It would be useful for the terminal to report an error on a missing font file. ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888458 Title: text not displaying ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1888458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888458] [NEW] text not displaying ubuntu 20.04
Public bug reported: * Have upgraded from Ubuntu 10.10 to Ubuntu 20.04 * Rebooted PC * After reboot, and login * Opened gnome-terminal * something displays, but it is NOT Text * completely unreadable (screen shot attached) * with no terminal, I'm restricted in what I may do to trouble shoot this problem. * Nvidia graphics -- Updating to latest available: nvidia-driver-440, did not help GNOME-TERMINAL not working for this Ubuntu 20.04 installation ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: character-set display font unreadable ** Attachment added: "BUG__Gnome-Terminal_window_Ubuntu-20-04.png" https://bugs.launchpad.net/bugs/1888458/+attachment/5394767/+files/BUG__Gnome-Terminal_window_Ubuntu-20-04.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888458 Title: text not displaying ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1888458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888452] [NEW] Unreadable text Terminator on Ubuntu 20.04
Public bug reported: * I have upgraded from Ubuntu 19.10 to Ubuntu 20.04 * When I start the terminator terminal emulator it comes up with unreadble text * I have attached a screen shot. * There is NO 20.04 package in launchpad for Terminator. IMPACT Terminator cannot urrently be used on Ubuntu 20.04 ** Affects: terminator (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04 characterset text ** Attachment added: "BUG__Terminator_window_Ubuntu-20-04.png" https://bugs.launchpad.net/bugs/1888452/+attachment/5394764/+files/BUG__Terminator_window_Ubuntu-20-04.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888452 Title: Unreadable text Terminator on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1888452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886113] Re: snap-store Does Not Run with XAUTHORITY error
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886113 Title: snap-store Does Not Run with XAUTHORITY error To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1886113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712520] Re: [17.04][gnome] screen hanged after meld launched via terminal was put to sleep by C-z: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
I am getting this message very very frequently.
Ubuntu 19.10
from the command line. The most intersting thing is that I may have 5
or 6 bash windows open. Aftetr executiong Meld from one terminal
window. If I subsequently use meld from a Different teminal session,
these errors spray-out on that first terminal's window:
:
2020-03-18 11:52:47,201 CRITICAL Gtk: gtk_widget_get_scale_factor: assertion
'GTK_IS_WIDGET (widget)' failed
2020-03-18 11:52:47,201 CRITICAL Gtk: gtk_widget_get_scale_factor: assertion
'GTK_IS_WIDGET (widget)' failed
2020-03-18 11:52:47,201 CRITICAL Gtk: gtk_widget_get_scale_factor: assertion
'GTK_IS_WIDGET (widget)' failed
2020-03-18 11:52:47,201 CRITICAL Gtk: gtk_widget_get_scale_factor: assertion
'GTK_IS_WIDGET (widget)' failed
I execute meld with the following command
nohup meld "${@}" > /dev/null 2>&1 &
Which sends output to dev/null. I am very surprised to see these
messages coming on any screen since the output is sent to null.
It looks to me like there's some kind of service involved not the
actuall meld background process
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712520
Title:
[17.04][gnome] screen hanged after meld launched via terminal was put
to sleep by C-z: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET
(widget)' failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1712520/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865936] [NEW] gnome-calculator (snap) fails on 19.10
Public bug reported: Hello -- This is a clean Ubuntu 10.10 install onto a new disk. For many days now I've been clicking on the calculator. It just doesn't work. No message or error report. I am looking for an alternative caclulator to install. Today I tried to run the calculator from the command line --It failed but at least it displayed some information about the error that stops it working. See below: $ gnome-calculator 2020/03/04 07:34:57.038784 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/Moort/home/william/.Xauthority" cannot create user data directory: /home/william/snap/gnome-calculator/544: Not a directory $ whereis gnome-calculator gnome-calculator: /snap/bin/gnome-calculator $ ll /home/william/snap/gnome-calculator/ total 20 drwxr-xr-x 5 william william 4096 Feb 6 03:07 ./ drwxr-xr-x 9 william william 4096 Dec 14 00:25 ../ drwxr-xr-x 2 william william 4096 Aug 29 2019 536/ drwxr-xr-x 2 william william 4096 Aug 29 2019 544/ drwxr-xr-x 2 william william 4096 Aug 29 2019 common/ lrwxrwxrwx 1 william william3 Feb 6 03:07 current -> 544/ As you can see the requisite directory is There! I am sad to report that this kind of error has been seen before on 19.04 I had hoped eventually someone would correct this -- There is a systemic failure here makins snaps. None of them appear to work with my install. My home directory is on Another disk. This is pretty much standard practice in my work place. I recommend this problem be fixed for ALL snaps. ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865936 Title: gnome-calculator (snap) fails on 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1865936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859105] [NEW] Upgrade upgrade 19.04 to 19.10 Fails on nvidia-dkms-418 post-installation
Public bug reported: The Upgrader process stopped and recommended reporting this error: installed nvidia-dkms-418 package post-installation script subprocess returned error exit status 10 That nvidia driver package seems strange too. I had thought I was using: nvidia-driver-430 I have run a reconfigure command as advised by the upgrade script: sudo dpkg --configure -a I get errors here to for much the same reason I believe. Output: Setting up nvidia-dkms-418 (418.56-0ubuntu1) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Removing old nvidia-418.56 DKMS files... -- Deleting module version: 418.56 completely from the DKMS tree. -- Done. Loading new nvidia-418.56 DKMS files... Building for 5.4.10-050410-generic Building for architecture x86_64 Building initial module for 5.4.10-050410-generic ERROR (dkms apport): kernel package linux-headers-5.4.10-050410-generic is not supported Error! Bad return status for module build on kernel: 5.4.10-050410-generic (x86_64) Consult /var/lib/dkms/nvidia/418.56/build/make.log for more information. dpkg: error processing package nvidia-dkms-418 (--configure): installed nvidia-dkms-418 package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of nvidia-driver-418: nvidia-driver-418 depends on nvidia-dkms-418 (= 418.56-0ubuntu1); however: Package nvidia-dkms-418 is not configured yet. dpkg: error processing package nvidia-driver-418 (--configure): dependency problems - leaving unconfigured Processing triggers for initramfs-tools (0.131ubuntu19.2) ... update-initramfs: Generating /boot/initrd.img-5.4.10-050410-generic W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 Errors were encountered while processing: nvidia-dkms-418 nvidia-driver-418 The current system information is as shown below. My next step is to attempt to explicitly uninstall this nvidia-driver-418 and move to one of the drivers shown for the custom drivers on software update. The Upgrade to 19.10 reports as incomplete. Unfortunately the terminal just closed itself at the end and I can't show you the output it gave me. It would be an essential thing for the Upgrader itef to save the output some place and Tell Me where to find the file so I may attach it or paste it into the bug report. Please? OK rebooting now. Thank you for your wonderful work. This is the first time I've had an upgrade problme. And it seems to be a nvidia issue not an Ubuntu one. $ inxi -Fxzd System:Host: 4TELLT70 Kernel: 5.4.10-050410-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Cinnamon 3.8.8 Distro: Ubuntu 19.04 (Disco Dingo) Machine: Type: Laptop System: IT Channel Pty product: N95TP6 v: N/A serial: Mobo: IT Channel Pty model: N95TP6 serial: UEFI: American Megatrends v: 1.05.06 date: 03/26/2018 Battery: ID-1: BAT0 charge: 60.3 Wh condition: 60.3/62.1 Wh (97%) model: Notebook BAT status: Full CPU: Topology: 6-Core model: Intel Core i5-8400 bits: 64 type: MCP arch: Kaby Lake rev: A L2 cache: 9216 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33599 Speed: 900 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 900 2: 900 3: 900 4: 900 5: 900 6: 900 Graphics: Device-1: Intel UHD Graphics 630 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 Device-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] vendor: CLEVO/KAPOK driver: N/A bus ID: 01:00.0 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) v: 4.5 Mesa 19.0.8 direct render: Yes Audio: Device-1: Intel 200 Series PCH HD Audio vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: NVIDIA GP106 High Definition Audio vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus ID: 01:00.1 Sound Server: ALSA v: k5.4.10-050410-generic Network: Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: e000 bus ID: 03:00.0 IF: wlp3s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK driver: r8169 v: kernel port: d000 bus ID: 04:00.1 IF: enp4s0f1 state: up speed: 1000 Mbps duplex: full mac: IF-ID-1: docker0 state: down mac: Drives:Local Storage: total: 1.14 TiB used: 225.05 GiB (19.2%) ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKKW256G8 size: 238.47 GiB ID-2: /dev/sda vendor
[Bug 1826460] Re: Every snap gives "create user data directory" after upgrade to 19.04
Greetings ... Yes I'm seeing this as well. It has become annoying since I decided I'd rather like to be using LXD. BUT lxd defaults to install as a snap. *crunch* point. Now I see this nonsense all the time: aplatypys one $ ll /home/aplatypys/snap/lxd/ total 16 drwxr-xr-x 4 aplatypys aplatypys 4096 Aug 1 01:24 ./ drwxr-xr-x 7 aplatypys aplatypys 4096 Jul 31 01:10 ../ drwxr-xr-x 2 aplatypys aplatypys 4096 Aug 1 01:24 11405/ drwxr-xr-x 2 aplatypys aplatypys 4096 Aug 1 01:24 common/ lrwxrwxrwx 1 aplatypys aplatypys5 Jul 31 01:10 current -> 11405/ aplatypys one $ ll -d /home/aplatypys/snap/lxd/ drwxr-xr-x 4 aplatypys aplatypys 4096 Aug 1 01:24 /home/aplatypys/snap/lxd// aplatypys one $ chmod g+w /home/aplatypys/snap/lxd/ aplatypys one $ lxd help 2019/08/01 02:17:04.434343 cmd_run.go:884: WARNING: cannot create user data directory: failed to verify SELinux context of /home/aplatypys/snap: exec: "matchpathcon": executable file not found in $PATH 2019/08/01 02:17:04.434427 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/Moort/home/aplatypys/.Xauthority" cannot create user data directory: /home/aplatypys/snap/lxd/11405: Not a directory May I install lxd as a PPA or a 'normal' package? Anyway however things are currently set -- Does not server quite a few people it seems. Until now I found I can live life without snaps. Does it also mean I will need to decide to live without lxd(???) Am I mistaken to consider that this is a backward step? Sincerely, aplatypus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826460 Title: Every snap gives "create user data directory" after upgrade to 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1826460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640297] Re: 16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 4.4.0-42-generic and older
I am getting this with 4.4.0-59-generic, I'm booted off a thumb drive using 4.4 and this systems update manager is prompting to upgrade the kernel to 4.4.0-59. Which I'm obviously NOT doing. However my point is why is this still in circulation -- Shouldn't it be pulled off the list of packages? I am not sure how other people managed to get command output, my system hangs just after it says Loading Virtual Drive or RAM-disk. And "Console not available" which sucks, since it is just dead. Also I am not sure about numbering scheme here. Is v4.10-rc5, 0.6 increments away from 4.4.0-59? Is that the right way to read this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640297 Title: 16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 4.4.0-42-generic and older To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290217] Re: The overwriting error message was: Key file does not have group 'connectivity'
@delt - Yes I've been having this problem come and go for at least 4 months now. There's a thread on the Linux Mint forums but i can't give a reference tonight because the site is down for maintenance. I don't know that that would be helpful though. Until I found this error in my log file, I was thinking there was a problem with the DNS because it happens on "popular" URLs like Google.com, Yahoo.com, GitHub and dl.google.com just yesterday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290217 Title: The overwriting error message was: Key file does not have group 'connectivity' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1290217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290217] Re: The overwriting error message was: Key file does not have group 'connectivity'
Hi - I'm seeing this problem on an up-to-date Linux Mint 17.2, Rafaela installed. And as current as update manager and apt-get network access allow it. Most concerning is that he $ apt-get update Command is failing on some URL-s. I've put a description on StackOverflow if someone has ideas on how to resolve this before there's a permanent fix. * http://unix.stackexchange.com/posts/243583 The problem I'm seeing eventually clears, so I thought it was dns cache related. After finding this error in the network-manager log I don't wonder if it might go deeper. (Thanks for listening) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290217 Title: The overwriting error message was: Key file does not have group 'connectivity' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1290217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
