[Bug 2065630] Re: fail2ban install error on noble
*** This bug is a duplicate of bug 2063833 *** https://bugs.launchpad.net/bugs/2063833 ** This bug has been marked a duplicate of bug 2063833 "SyntaxWarning: invalid escape sequence" during fail2ban install in Ubuntu 24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065630 Title: fail2ban install error on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2065630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062420] Re: rmlint required dependency libelf1 is not available in noble
That library is replaced in noble by libelf1t64. It's strange that it causes a problem since apt and dpkg should detect this replacement and install it. What's the error you get? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062420 Title: rmlint required dependency libelf1 is not available in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rmlint/+bug/2062420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
@ahasenack thank you very much. In the meantime as a workaround for noble you can install the oracular- proposed deb file "fail2ban_1.1.0-1_all.deb". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062177] Re: Remmina crashes after RDP connection
I just tested remmina 1.4.35+dfsg-0ubuntu5 from proposed repo: RDP connections works as expected so problem is solved. NOTE: I've tested amd64 and arm64 versions connecting one against the other. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062177 Title: Remmina crashes after RDP connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2062177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: cifs: Copying file to same directory results in page fault
Test done. Kernel 6.5.0-35-generic works as expected and solved the problem: root@fpgmsi:~# uname -rv 6.5.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 26 11:23:57 UTC 2024 root@fpgmsi:~# mount -t cifs -o username=fprietog //192.168.1.10/FPGNAS/ /mnt/share Password for fprietog@//192.168.1.10/FPGNAS/: root@fpgmsi:~# cd /mnt/share/tmp root@fpgmsi:/mnt/share/tmp# touch file1.txt root@fpgmsi:/mnt/share/tmp# cp file1.txt file2.txt Thank you very much! ** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: cifs: Copying file to same directory results in page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063833] Re: "SyntaxWarning: invalid escape sequence" during fail2ban install in Ubuntu 24.04
I saw the same bug reported for Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063870 ** Bug watch added: Debian Bug tracker #1063870 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063870 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063833 Title: "SyntaxWarning: invalid escape sequence" during fail2ban install in Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2063833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063887] [NEW] debsums warning after upgrade to Ubuntu 24.04 (noble): changed file /etc/X11/xorg.conf.d/99-v3d.conf (from ubuntu-raspi-settings-desktop package)
Public bug reported:
System: Raspberry Pi 4 Model B Rev 1.4
After upgrade to Ubuntu 24.04 (noble) I'm getting this debsums warning:
# debsums -sa ubuntu-raspi-settings-desktop
debsums: changed file /etc/X11/xorg.conf.d/99-v3d.conf (from
ubuntu-raspi-settings-desktop package)
The difference between the file installed and the file from the ubuntu-
raspi-settings-desktop package is just the indentation:
- The file installed is indented with two spaces:
Section "OutputClass"
Identifier "vc4"
MatchDriver "vc4"
Driver "modesetting"
Option "PrimaryGPU" "true"
EndSection
- The file from the package is indented with one tabulator:
Section "OutputClass"
Identifier "vc4"
MatchDriver "vc4"
Driver "modesetting"
Option "PrimaryGPU" "true"
EndSection
If I replace the file installed with the one from the package in order
to avoid the debsums warning, the file is auto-replaced again during
boot by the systemd update-v3d-config.service.
This service runs the script /usr/bin/update-v3d-config; when the system
is a Raspberry Pi 5 this script replaces "Identify" and "MatchDriver"
but for the rest of Raspberry Pi models it should leave the file as
originally was. The problem is that the script always replaces the file
with two spaces indentation instead of one tabulator causing the debsums
mismatch:
...
sed -e "s/IDENTIFIER/${IDENTIFIER}/; s/DRIVER/${DRIVER}/" << EOF >
"$TMPFILE"
Section "OutputClass"
Identifier "IDENTIFIER"
MatchDriver "DRIVER"
Driver "modesetting"
Option "PrimaryGPU" "true"
EndSection
EOF
mv "$TMPFILE" "/etc/X11/xorg.conf.d/99-v3d.conf"
...
I understand that this fix is done in every boot because we (users)
should use the same OS installed media with different Raspberry Pi
models.
Well... a possible solution is to change the package file to have two
spaces of indentation instead of a tabulator, or to change the script to
use a tabulator instead of two spaces. The objective is having both
files identical to avoid the debsums warning... But unfortunately this
"fix" only avoids the debsums warning for the systems that are not a
Raspberry Pi 5 because in that case the warning is unavoidable as the
result installed file will be always different from the one of the
package. So this isn't a perfect solution.
** Affects: ubuntu-raspi-settings (Ubuntu)
Importance: Undecided
Status: New
** Tags: 99-v3d.conf debsums noble pi raspberry
** Summary changed:
- debsums warning after upgrade to Ubuntu 22.04 (noble): changed file
/etc/X11/xorg.conf.d/99-v3d.conf (from ubuntu-raspi-settings-desktop package)
+ debsums warning after upgrade to Ubuntu 24.04 (noble): changed file
/etc/X11/xorg.conf.d/99-v3d.conf (from ubuntu-raspi-settings-desktop package)
** Description changed:
System: Raspberry Pi 4 Model B Rev 1.4
- After upgrade to Ubuntu 22.04 (noble) I'm getting this debsums warning:
+ After upgrade to Ubuntu 24.04 (noble) I'm getting this debsums warning:
# debsums -sa ubuntu-raspi-settings-desktop
debsums: changed file /etc/X11/xorg.conf.d/99-v3d.conf (from
ubuntu-raspi-settings-desktop package)
The difference between the file installed and the file from the ubuntu-
raspi-settings-desktop package is just the indentation:
- The file installed is indented with two spaces:
Section "OutputClass"
- Identifier "vc4"
- MatchDriver "vc4"
- Driver "modesetting"
- Option "PrimaryGPU" "true"
+ Identifier "vc4"
+ MatchDriver "vc4"
+ Driver "modesetting"
+ Option "PrimaryGPU" "true"
EndSection
- The file from the package is indented with one tabulator:
Section "OutputClass"
- Identifier "vc4"
- MatchDriver "vc4"
- Driver "modesetting"
- Option "PrimaryGPU" "true"
+ Identifier "vc4"
+ MatchDriver "vc4"
+ Driver "modesetting"
+ Option "PrimaryGPU" "true"
EndSection
If I replace the file installed with the one from the package in order
to avoid the debsums warning, the file is auto-replaced again during
boot by the systemd update-v3d-config.service.
This service runs the script /usr/bin/update-v3d-config; when the system
is a Raspberry Pi 5 this script replaces "Identify" and "MatchDriver"
but for the rest of Raspberry Pi models it should leave the file as
originally was. The problem is that the script always replaces the file
with two spaces indentation instead of one tabulator causing the debsums
mismatch:
...
- sed -e "s/IDENTIFIER/${IDENTIFIER}/; s/DRIVER/${DRIVER}/" << EOF >
"$TMPFILE"
+ sed -e "s/IDENTIFIER/${IDENTIFIER}/; s/DRIVER/${DRIVER}/" << EOF >
"$TMPFILE"
Section "OutputClass"
- Identifier "IDENTIFIER"
- MatchDriver "DRIVER"
- Driver "modesetting"
- Option "PrimaryGPU" "true"
+ Identifier "IDENTIFIER"
+ MatchDriver "DRIVER"
+ Driver "modesetting"
+ Option "PrimaryGPU" "true"
EndSection
EOF
- mv "$TMPFILE" "/etc/X11/xorg.conf.d/99-v3d.conf"
+ mv "$TMPFILE" "/etc/X11/xorg.conf.d/99-v3d.conf"
[Bug 2060919] Re: cifs: Copying file to same directory results in page fault
> If I upgrade to 24.04 which just came out today with the 6.8 kernel, would that also fix this? Seems that this kernel doesn't have this problem, so yes, it will fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: cifs: Copying file to same directory results in page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061211] Re: Invalid escape sequences in regexes when installing gedit
It can also be reproduced reinstalling gedit (in this example in aarch64
architecture):
# apt install --reinstall gedit
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias... Hecho
Leyendo la información de estado... Hecho
0 actualizados, 0 nuevos se instalarán, 1 reinstalados, 0 para eliminar y 0 no
actualizados.
Se necesita descargar 353 kB de archivos.
Se utilizarán 0 B de espacio de disco adicional después de esta operación.
Des:1 http://ports.ubuntu.com/ubuntu-ports noble/universe arm64 gedit arm64
46.2-2 [353 kB]
Descargados 353 kB en 0s (1.178 kB/s)
(Leyendo la base de datos ... 221724 ficheros o directorios instalados
actualmente.)
Preparando para desempaquetar .../gedit_46.2-2_arm64.deb ...
Desempaquetando gedit (46.2-2) sobre (46.2-2) ...
Configurando gedit (46.2-2) ...
/usr/lib/aarch64-linux-gnu/gedit/plugins/externaltools/library.py:212:
SyntaxWarning: invalid escape sequence '\-'
RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$')
/usr/lib/aarch64-linux-gnu/gedit/plugins/snippets/substitutionparser.py:162:
SyntaxWarning: invalid escape sequence '\s'
match = re.match('?%s\s*' % self.REG_GROUP, tokens)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061211
Title:
Invalid escape sequences in regexes when installing gedit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2061211/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2029480] Re: SyntaxWarnings with Python3.12
I'm sorry but the related fix seem to be not complete: during upgrade
from 23.10.1 mantic to 24.04 noble it updates hplip-data
3.23.12+dfsg0-0ubuntu5 from previous 3.22.10+dfsg0-2ubuntu1 and it
doesn't generate SyntaxWarnings... but a few moments later, then during
python3 (3.12.3-0ubuntu1) configuration:
Configurando python3 (3.12.3-0ubuntu1) ...
running python rtupdate hooks for python3.12...
...
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence
'\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence
'\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence
'\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d'
http_result_pat = re.compile(b"""HTTP/\d.\d\s(\d+)""", re.I)
...
running python post-rtupdate hooks for python3.12...
You can also reinstall hplip-data using apt and ending in the same
problem:
# apt install --reinstall hplip-data
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias... Hecho
Leyendo la información de estado... Hecho
0 actualizados, 0 nuevos se instalarán, 1 reinstalados, 0 para eliminar y 0 no
actualizados.
Se necesita descargar 6.467 kB de archivos.
Se utilizarán 0 B de espacio de disco adicional después de esta operación.
Des:1 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 hplip-data all
3.23.12+dfsg0-0ubuntu5 [6.467 kB]
Descargados 6.467 kB en 1s (8.035 kB/s)
(Leyendo la base de datos ... 221724 ficheros o directorios instalados
actualmente.)
Preparando para desempaquetar .../hplip-data_3.23.12+dfsg0-0ubuntu5_all.deb ...
Desempaquetando hplip-data (3.23.12+dfsg0-0ubuntu5) sobre
(3.23.12+dfsg0-0ubuntu5) ...
Configurando hplip-data (3.23.12+dfsg0-0ubuntu5) ...
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence
'\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence
'\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence
'\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d'
http_result_pat = re.compile(b"""HTTP/\d.\d\s(\d+)""", re.I)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2029480
Title:
SyntaxWarnings with Python3.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/2029480/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063833] [NEW] "SyntaxWarning: invalid escape sequence" during fail2ban install in Ubuntu 24.04
Public bug reported:
Configurando fail2ban (1.0.2-3) ...
...
/usr/lib/python3/dist-packages/fail2ban/tests/fail2banregextestcase.py:224:
SyntaxWarning: invalid escape sequence '\s'
"1490349000 test failed.dns.ch", "^\s*test \S+"
/usr/lib/python3/dist-packages/fail2ban/tests/fail2banregextestcase.py:435:
SyntaxWarning: invalid escape sequence '\S'
'^'+prefix+'User \S+ not allowed\n'
/usr/lib/python3/dist-packages/fail2ban/tests/fail2banregextestcase.py:443:
SyntaxWarning: invalid escape sequence '\S'
'^'+prefix+'User \S+ not allowed\n'
/usr/lib/python3/dist-packages/fail2ban/tests/fail2banregextestcase.py:444:
SyntaxWarning: invalid escape sequence '\d'
'^'+prefix+'Received disconnect from port \d+'
/usr/lib/python3/dist-packages/fail2ban/tests/fail2banregextestcase.py:451:
SyntaxWarning: invalid escape sequence '\s'
_test_variants('common', prefix="\s*\S+ sshd\[\d+\]:\s+")
/usr/lib/python3/dist-packages/fail2ban/tests/fail2banregextestcase.py:537:
SyntaxWarning: invalid escape sequence '\['
'common[prefregex="^svc\[\d+\] connect
.+$"'
/usr/lib/python3/dist-packages/fail2ban/tests/servertestcase.py:1375:
SyntaxWarning: invalid escape sequence '\s'
"`{ nft -a list chain inet f2b-table f2b-chain | grep -oP
'@addr-set-j-w-nft-mp\s+.*\s+\Khandle\s+(\d+)$'; } | while read -r hdl; do`",
/usr/lib/python3/dist-packages/fail2ban/tests/servertestcase.py:1378:
SyntaxWarning: invalid escape sequence '\s'
"`{ nft -a list chain inet f2b-table f2b-chain | grep -oP
'@addr6-set-j-w-nft-mp\s+.*\s+\Khandle\s+(\d+)$'; } | while read -r hdl; do`",
/usr/lib/python3/dist-packages/fail2ban/tests/servertestcase.py:1421:
SyntaxWarning: invalid escape sequence '\s'
"`{ nft -a list chain inet f2b-table f2b-chain | grep -oP
'@addr-set-j-w-nft-ap\s+.*\s+\Khandle\s+(\d+)$'; } | while read -r hdl; do`",
/usr/lib/python3/dist-packages/fail2ban/tests/servertestcase.py:1424:
SyntaxWarning: invalid escape sequence '\s'
"`{ nft -a list chain inet f2b-table f2b-chain | grep -oP
'@addr6-set-j-w-nft-ap\s+.*\s+\Khandle\s+(\d+)$'; } | while read -r hdl; do`",
In my case fail2ban isn't the only package with these kind of errors
during the upgrade from 23.10.1 to 24.04; I've also same errors in
gdebi-core, hplip, gedit-plugins... Probably it's related to the upgrade
of python 3.12 from 3.11.
** Affects: fail2ban (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/2063833
Title:
"SyntaxWarning: invalid escape sequence" during fail2ban install in
Ubuntu 24.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2063833/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060431] Re: error message during gdebi-core installation
Same problem here, during upgrade from mantic 23.10.1 to noble 24.04:
Configurando gdebi-core (0.9.5.7+nmu7) ...
/usr/share/gdebi/GDebi/GDebiCli.py:159: SyntaxWarning: invalid escape sequence
'\S'
c = findall("[[(](\S+)/\S+[])]", msg)[0].lower()
In my case gdebi-core isn't the only package with these kind of errors
during the upgrade; I've also same errors in fail2ban, hplip, gedit-
plugins... Probably it's related with the upgrade to python 3.12 from
3.11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060431
Title:
error message during gdebi-core installation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/2060431/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
@mruffell I've noticed that the users who have tested your kernel got something in common: the remote system mounted as cifs isn't in an Ubuntu server and it's kernel seems to be older than Ubuntu's client one... Maybe it's something that can help you to reproduce the problem yourself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
** Attachment added: "dmesg from the test" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+attachment/5768024/+files/dmesg_6.5.0-27-generic_%2328+TEST2060919v20240419b1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
Tested: # uname -rv 6.5.0-27-generic #28+TEST2060919v20240419b1-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 19 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic # cd /mnt/fpgnas/tmp /mnt/fpgnas/tmp# touch sample1.txt /mnt/fpgnas/tmp# cp sample1.txt sample2.txt Success! I've tested some other cases as well and CIFS works as expected for all of them. So I think you have find the culprit. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
>As promised, I uploaded test kernels to the below ppa: > >https://launchpad.net/~mruffell/+archive/ubuntu/lp2060919-test OK. I'll test once it's built ends. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
> I think this patch is probably not needed in 6.5, and causes the issue. How > about I build > you a test kernel with "cifs: fix flushing folio regression for 6.1 backport" > reverted, > and then we see if it fixes things? Yep, fantastic. I can reproduce this problem anytime so I can test it. > If you can help me make a reproducer, that would be great. I can test myself then. Here is some info from a faulty system. Hope it helps: * fstab mount: //192.168.1.10/FPGNAS /mnt/FPGNAS_CIFS cifs _netdev,x-systemd.requires=network-online.target,async,nosuid,nodev,noexec,iocharset=utf8,file_mode=0640,dir_mode=0750,uid=1026,gid=100,credentials=/etc/.cifspwd,rw 0 0 * mount info: //192.168.1.10/FPGNAS on /mnt/FPGNAS_CIFS type cifs (rw,nosuid,nodev,noexec,relatime,vers=3.1.1,cache=strict,username=fprietog,uid=1026,noforceuid,gid=100,noforcegid,addr=192.168.1.10,file_mode=0640,dir_mode=0750,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1,_netdev,x-systemd.requires=network-online.target) * cp from a file to a file both in same share: # cd /mnt/FPGNAS_CIFS/tmp /mnt/FPGNAS_CIFS/tmp# touch sample1.txt /mnt/FPGNAS_CIFS/tmp# cp sample1.txt sample2.txt Terminado (killed) After that error the CIFS mount become unusable as any operation just hangs. * The remote cifs server is a Synology DS213j NAS. Samba version is: # smbd -V Version 4.15.9 Synology Build 42934, Jul 5 2023 16:52:06 Please, let me know if I can give you any other info that helps to solve the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
Today's released kernels: - 6.5.0-28-generic (amd64) - 6.5.0-1015-raspi (arm64) Still have this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
> Same issue on kernel 6.5.0-27-generic #28~22.04.1-Ubuntu That kernel is from the "linux-hwe-6.5" package. I'll try to link this bug to that package to avoid duplication. ** Also affects: linux-hwe-6.5 (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/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu"
== Example for Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64) == # lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 # uname -a Linux fpgrpi 6.5.0-1014-raspi #17-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 21 11:24:03 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux # cat /proc/version_signature Ubuntu 6.5.0-1014.17-raspi 6.5.13 How to reproduce the problem For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: abr 11 09:11:02 fpgrpi kernel: Unable to handle kernel paging request at virtual address fffe abr 11 09:11:02 fpgrpi kernel: Mem abort info: abr 11 09:11:02 fpgrpi kernel: ESR = 0x9604 abr 11 09:11:02 fpgrpi kernel: EC = 0x25: DABT (current EL), IL = 32 bits abr 11 09:11:02 fpgrpi kernel: SET = 0, FnV = 0 abr 11 09:11:02 fpgrpi kernel: EA = 0, S1PTW = 0 abr 11 09:11:02 fpgrpi kernel: FSC = 0x04: level 0 translation fault abr 11 09:11:02 fpgrpi kernel: Data abort info: abr 11 09:11:02 fpgrpi kernel: ISV = 0, ISS = 0x0004, ISS2 = 0x abr 11 09:11:02 fpgrpi kernel: CM = 0, WnR = 0, TnD = 0, TagAccess = 0 abr 11 09:11:02 fpgrpi kernel: GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 abr 11 09:11:02 fpgrpi kernel: swapper pgtable: 4k pages, 48-bit VAs, pgdp=01498000 abr 11 09:11:02 fpgrpi kernel: [fffe] pgd=, p4d= abr 11 09:11:02 fpgrpi kernel: Internal error: Oops: 9604 [#1] PREEMPT SMP abr 11 09:11:02 fpgrpi kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs cmac algif_hash algif_skcipher af_alg bnep lz4 lz4_compress zram zsmalloc nft_chain_nat nf_nat sunrpc xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc nft_compat nf_tables nfnetlink brcmfmac_wcc btsdio brcmfmac vc4 brcmutil snd_soc_hdmi_codec hci_uart cfg80211 drm_display_helper btqca btrtl raspberrypi_hwmon cec drm_dma_helper btbcm btintel bluetooth raspberrypi_gpiomem drm_kms_helper ecdh_generic rfkill ecc snd_soc_core bcm2835_v4l2(CE) bcm2835_codec(CE) bcm2835_isp(CE) bcm2835_mmal_vchiq(CE) snd_compress ac97_bus snd_pcm_dmaengine rpivid_hevc(CE) vc_sm_cma(CE) snd_bcm2835(CE) v4l2_mem2mem videobuf2_vmalloc videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videodev videobuf2_common mc snd_pcm snd_timer joydev nvmem_rmem input_leds uio_pdrv_genirq uio tcp_bbr sch_fq ecryptfs parport_pc ppdev lp parport fuse abr 11 09:11:02 fpgrpi kernel: ip_tables x_tables autofs4 btrfs blake2b_generic raid10 hid_generic raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx usbhid xor xor_neon uas usb_storage raid6_pq libcrc32c raid1 raid0 multipath linear md_mod dm_mirror dm_region_hash dm_log dm_mod dax zstd z3fold spidev dwc2 v3d gpu_sched drm_shmem_helper drm roles crct10dif_ce drm_panel_orientation_quirks i2c_brcmstb udc_core i2c_bcm2835 xhci_pci xhci_pci_renesas spi_bcm2835 snd backlight phy_generic aes_arm64 abr 11 09:11:02 fpgrpi kernel: CPU: 3 PID: 79549 Comm: Thread (pooled) Tainted: G C E 6.5.0-1014-raspi #17-Ubuntu abr 11 09:11:02 fpgrpi kernel: Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) abr 11 09:11:02 fpgrpi kernel: pstate: 6045 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) abr 11 09:11:02 fpgrpi kernel: pc : cifs_flush_folio+0x5c/0x160 [cifs] abr 11 09:11:02 fpgrpi kernel: lr : cifs_flush_folio+0x50/0x160 [cifs] abr 11 09:11:02 fpgrpi kernel: sp : 80008d00bb30 abr 11 09:11:02 fpgrpi kernel: x29: 80008d00bb30 x28: x27: 6cb892a49000 abr 11 09:11:02 fpgrpi kernel: x26: 6cb88fff9200 x25: 6cb92bd1c350 x24: abr 11 09:11:02 fpgrpi kernel: x23: 0001 x22: 80008d00bba8 x21: 80008d00bbb0 abr 11 09:11:02 fpgrpi kernel: x20: x19: fffe x18: abr 11 09:11:02 fpgrpi kernel: x17: x16: b6bfe450e050 x15: abr 11 09:11:02 fpgrpi kernel: x14: x13: x12: abr 11 09:11:02 fpgrpi kernel: x11: x10: x9 : b6bfe450df28 abr 11 09:11:02 fpgrpi kernel: x8 : 80008d00bad8 x7 : x6 : 00023854 abr 11 09:11:02 fpgrpi kernel: x5 : 6cb887d82080 x4 : 1000 x3 : abr 11 09:11:02 fpgrpi kernel: x2 : x1 : 0001 x0 : fffe abr 11 09:11:02 fpgrpi kernel: Call trace: abr 11 09:11:02 fpgrpi kernel: cifs_flush_folio+0x5c/0x160 [cifs] abr 11 09:11:02 fpgrpi kernel:
[Bug 2060919] [NEW] Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu"
44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 abr 11 09:34:59 fpgmsi kernel: RSP: 002b:7bd4d59498a0 EFLAGS: 0246 ORIG_RAX: 0010 abr 11 09:34:59 fpgmsi kernel: RAX: ffda RBX: 0023 RCX: 7bd4ff12396f abr 11 09:34:59 fpgmsi kernel: RDX: 0023 RSI: 40049409 RDI: 002c abr 11 09:34:59 fpgmsi kernel: RBP: 002c R08: 7bd4c80008e0 R09: 0007 abr 11 09:34:59 fpgmsi kernel: R10: 7bd4c80026b0 R11: 0246 R12: 7bd4c8001380 abr 11 09:34:59 fpgmsi kernel: R13: 7bd4d5949a10 R14: 7bd4c8001e20 R15: 7bd4d5949a00 abr 11 09:34:59 fpgmsi kernel: abr 11 09:34:59 fpgmsi kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs cmac algif_hash algif_skcipher af_alg nft_chain_nat nvidia_uvm(POE) nf_nat bnep zram xt_tcpudp sunrpc xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables binfmt_misc nfnetlink nls_iso8859_1 intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common snd_sof_pci_intel_tgl nvidia_drm(POE) snd_sof_intel_hda_common nvidia_modeset(POE) soundwire_intel x86_pkg_temp_thermal intel_powerclamp snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_hda_codec_realtek snd_sof snd_hda_codec_generic ledtrig_audio snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation snd_hda_codec_hdmi soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core abr 11 09:34:59 fpgmsi kernel: snd_hwdep coretemp iwlmvm snd_pcm btusb btrtl kvm_intel btbcm snd_seq_midi snd_seq_midi_event btintel cmdlinepart mac80211 btmtk snd_rawmidi spi_nor nvidia(POE) libarc4 kvm bluetooth snd_seq mtd iwlwifi pmt_telemetry snd_seq_device pmt_class snd_timer irqbypass rapl ecdh_generic joydev intel_cstate input_leds wmi_bmof mxm_wmi ecc cfg80211 snd mei_me i2c_i801 spi_intel_pci soundcore mei spi_intel i2c_smbus intel_vsec serial_multi_instantiate acpi_pad acpi_tad mac_hid tcp_bbr sch_fq vmwgfx drm_ttm_helper ttm drm_kms_helper parport_pc ppdev lp parport drm efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log msr lz4 lz4_compress hid_generic usbhid hid crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 aesni_intel nvme crypto_simd cryptd nvme_core igc ahci xhci_pci libahci nvme_common abr 11 09:34:59 fpgmsi kernel: xhci_pci_renesas video wmi pinctrl_alderlake abr 11 09:34:59 fpgmsi kernel: CR2: fffe abr 11 09:34:59 fpgmsi kernel: ---[ end trace ]--- abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe RCX: abr 11 09:34:59 fpgmsi kernel: RDX: RSI: RDI: abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 R09: abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11: R12: abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0() GS:90753f80() knlGS: abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0: 80050033 abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 CR4: 00750ef0 abr 11 09:34:59 fpgmsi kernel: PKRU: 5554 abr 11 09:34:59 fpgmsi kernel: note: Thread (pooled)[28103] exited with irqs disabled After that error the CIFS filesystem just became unusable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-27-generic 6.5.0-27.28 ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: fprietog 11499 F wireplumber /dev/snd/controlC1: fprietog 11499 F wireplumber /dev/snd/seq:fprietog 11497 F
[Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
Just updated to these packages: - gnome-remote-desktop (42.1.1-0ubuntu1) - libfreerdp2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1) - libfreerdp-server2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1) - libfreerdp-client2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1) And VNC and RPD sharing are working now in arm64 (Raspberry Pi 4B). So bug seems to be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
As a temporary (or final) solution just use another VNC or RDP Server. You can do that only if you use X11 because apart from gnome-remote- desktop there are no working desktop sharing utilities for Wayland. You've more info here: https://help.ubuntu.com/community/VNC/Servers For instance, I'm using vino VNC server, the old-but-gold sharing server for Ubuntu. I'm not only using it to remotely access an started user session. I also use it to access gdm remotely so I can start users sessions remotely directly from the greeter. This is something that I haven't managed to do with genome-remote-session because of it's way of store/access credentials. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973387] Re: Application hangs when select "Document Properties" in an empty document
You're true, I just checked and the problem has gone... I've setup a VM to test what was changed that fixed the problem and found that was this update: libgtk-4-common (4.6.3+ds1-0ubuntu1) over (4.6.2+ds-1ubuntu3) ... libgtk-4-1 (4.6.3+ds1-0ubuntu1) over (4.6.2+ds-1ubuntu3) ... libgtk-4-bin (4.6.3+ds1-0ubuntu1) over (4.6.2+ds-1ubuntu3) ... Part of that update details are: gtk4 (4.6.3+ds1-0ubuntu1) jammy; urgency=medium - Work around infinite loop in box allocation (Closes: #1010547) Bug details: https://groups.google.com/g/linux.debian.bugs.dist/c/cqOEuWTYlAo?pli=1 https://gitlab.gnome.org/GNOME/gtk/-/issues/4517 So this bug can be closed. Thanks! ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4517 https://gitlab.gnome.org/GNOME/gtk/-/issues/4517 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973387 Title: Application hangs when select "Document Properties" in an empty document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1973387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976147] Re: [Kernel 5.15] System messages (kernel and systemd) are not shown during boot until it reach a late stage
** Description changed: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # uname -a Linux fpgrpi 5.15.0-1008-raspi #8-Ubuntu SMP PREEMPT Thu May 19 11:58:51 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Problem summary: System is a Raspberry Pi 4 Model B Rev 1.4. When you remove the 'quiet' and 'splash' options in file /boot/firmware/cmdline.txt in order to see "live" the kernel and systemd messages generated during boot these messages are not shown from the start of the boot process. It remains a blank screen until boot process reached a late stage (maybe the gpu driver init but I'm not sure). It works with previous kernels 5.13 from Impish (it show all messages from the boot start) but is broken in kernels 5.15 from jammy. What was expected: -- As in kernel 5.13 the boot will show 4 raspberries in the top of the screen and the kernel and systemd messages generated will be shown from the start of the boot process. How to reproduce: - - Remove the 'quiet' option in file /boot/firmware/cmdline.txt in order to see "live" the kernel and systemd messages generated during boot. With kernel 5.13 these messages are shown from the boot process start but with kernel 5.15 the screen remains blank until a late boot stage. + Remove the 'quiet' and 'splash' options in file /boot/firmware/cmdline.txt in order to see "live" the kernel and systemd messages generated during boot. With kernel 5.13 these messages are shown from the boot process start but with kernel 5.15 the screen remains blank until a late boot stage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976147 Title: [Kernel 5.15] System messages (kernel and systemd) are not shown during boot until it reach a late stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1976147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976147] [NEW] [Kernel 5.15] System messages (kernel and systemd) are not shown during boot until it reach a late stage
Public bug reported: # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 # uname -a Linux fpgrpi 5.15.0-1008-raspi #8-Ubuntu SMP PREEMPT Thu May 19 11:58:51 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Problem summary: System is a Raspberry Pi 4 Model B Rev 1.4. When you remove the 'quiet' and 'splash' options in file /boot/firmware/cmdline.txt in order to see "live" the kernel and systemd messages generated during boot these messages are not shown from the start of the boot process. It remains a blank screen until boot process reached a late stage (maybe the gpu driver init but I'm not sure). It works with previous kernels 5.13 from Impish (it show all messages from the boot start) but is broken in kernels 5.15 from jammy. What was expected: -- As in kernel 5.13 the boot will show 4 raspberries in the top of the screen and the kernel and systemd messages generated will be shown from the start of the boot process. How to reproduce: - Remove the 'quiet' option in file /boot/firmware/cmdline.txt in order to see "live" the kernel and systemd messages generated during boot. With kernel 5.13 these messages are shown from the boot process start but with kernel 5.15 the screen remains blank until a late boot stage. ** Affects: linux-raspi (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/1976147 Title: [Kernel 5.15] System messages (kernel and systemd) are not shown during boot until it reach a late stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1976147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973387] [NEW] Application hangs when select "Document Properties" in an empty document
Public bug reported: Problem summary: When you select "Document Properties" in an empty document the application hangs sending dozens of messages like this (can be seen with journalctl): gtk_widget_measure: assertion 'for_size >= -1' failed Steps to reproduce: --- - Open gnome-text-editor (a new document, so empty) - Select "Document Properties" in menu - Application hangs with these repeated messages: gtk_widget_measure: assertion 'for_size >= -1' failed Tested in amd64 and arm64. Aditional info: --- No apport info because it doesn't crash, just hangs. # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 # apt-cache policy gnome-text-editor gnome-text-editor: Instalados: 42.1-0ubuntu1 Candidato: 42.1-0ubuntu1 Tabla de versión: *** 42.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 100 /var/lib/dpkg/status 42.0-2 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages ** Affects: gnome-text-editor (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/1973387 Title: Application hangs when select "Document Properties" in an empty document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1973387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
This problem happens with transmission-gtk package. A workaround is to use transmission-qt package instead of transmission-gtk. With transmission-gtk, when you open the torrent's properties panel, apart from scramble the texts, buttons, etc, there are GTK related errors spammed every few milliseconds (can be seen with journalctl). This is an example of these errors: may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkLabel' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_label_get_text: assertion 'GTK_IS_LABEL (label)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_label_set_text: assertion 'GTK_IS_LABEL (label)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkTreeModel' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_tree_model_iter_nth_child: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_tree_model_iter_nth_child: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkToggleButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_block: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_unblock: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkToggleButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkSpinButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_spin_button_get_value_as_int: assertion 'GTK_IS_SPIN_BUTTON (spin_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_block: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_spin_button_set_value: assertion 'GTK_IS_SPIN_BUTTON (spin_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_unblock: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkToggleButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkSpinButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_spin_button_get_value_as_int: assertion 'GTK_IS_SPIN_BUTTON (spin_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_block: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_spin_button_set_value: assertion 'GTK_IS_SPIN_BUTTON (spin_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_unblock: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_block: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkComboBox' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_combo_box_get_model: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_combo_box_get_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_tree_model_iter_nth_child: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_unblock: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38
[Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
* How did you enable the sharing? Using the config page: see attached image. I'm using exactly the same configuration and OS in 3 computers: 2 amd64 and the arm64 Raspberry Pi. In the amd64 ones VNC works. It only fails in the arm64 Raspberry Pi. * The default protocol and suggested one is RDP, did you try if that works better? In my case RDP just doesn't work in any of my machines (neither amd64 nor arm64). The RDP server gives these errors when I try to connect: abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:631] [4496:5565] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [ERROR][com.winpr.sspi.NTLM] - Message Integrity Check (MIC) verification failed! abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [WARN][com.winpr.sspi] - CompleteAuthToken status SEC_E_MESSAGE_ALTERED [0x8009030F] abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [WARN][com.freerdp.core.nla] - CompleteAuthToken status SEC_E_MESSAGE_ALTERED [0x8009030F] abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [ERROR][com.freerdp.core.transport] - client authentication failure abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 abr 25 19:06:26 fpglinux gnome-remote-de[4496]: Unable to check file descriptor, closing connection These errors may be related to this problem that I think is not solved in the Ubuntu current freerdp version: https://github.com/FreeRDP/FreeRDP/issues/7722 ** Bug watch added: freerdp-issues #7722 https://github.com/FreeRDP/FreeRDP/issues/7722 ** Attachment added: "Remote Access config" https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+attachment/5583584/+files/Captura%20desde%202022-04-25%2019-31-43.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
I managed to get a crash file from apport. It's attached. ** Attachment added: "apport crash file" https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+attachment/5583259/+files/_usr_libexec_gnome-remote-desktop-daemon.1026.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970139] [NEW] VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
Public bug reported: # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop. abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libcuda.so.1 abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libnvidia-encode.so.1 abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: RDP server started abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: VNC server started ** Affects: gnome-remote-desktop (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/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563083] Re: Desktop file broken
Seem that this bug has been solved in 20210415-1 version for Jammy, so should be closed. Thanks and best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563083 Title: Desktop file broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gprename/+bug/1563083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923667] Re: Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B).
After a quite long time using the 5.13 kernel series that came with Ubuntu 21.10 I can tell that this problem is gone. In my opinion the bug can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923667 Title: Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1923667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
Tested: Linux fpgrpi 5.13.0-1010-raspi #11-Ubuntu SMP PREEMPT Thu Oct 28 08:32:52 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Environments tested: X11 and wayland Problem is solved! ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
@andrum99 Probably not related to the missing zfs module in the testing package but be warned that there is a warning for the current impish zfs kennel module: === Attention: ZFS kernel panic mitigation === "The version of the ZFS driver included in the 5.13.0-19 kernel contains a bug that can result in filesystem corruption. Users of ZFS are advised to wait until the first Stable Release Update of the kernel in 21.10 before upgrading." Trent Lloyd's long standing bug report of the ZFS kernel panic is mitigated with the 5.13.0-20 impish-proposed kernel. https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
@fossfreedom, apart from the wm used (you budgie-wm and me gnome-shell) I see that your HDMI devices are identified as brcm:soc while mines are identified as fef00700 and fef05700. Maybe we are using different eeprom version. I'm using latest stable from here: https://github.com/raspberrypi/rpi-eeprom root@fpgrpi:~# rpi-eeprom-update BOOTLOADER: up to date CURRENT: mar 06 jul 2021 10:44:53 UTC (1625568293) LATEST: jue 29 abr 2021 16:11:25 UTC (1619712685) RELEASE: stable (/lib/firmware/raspberrypi/bootloader/stable) Use raspi-config to change the release. VL805_FW: Using bootloader EEPROM VL805: up to date CURRENT: 000138a1 LATEST: 000138a1 Which one are you using? Maybe you can update it to the newest version just to try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
@fossfreedom sorry to read this. It's still working for me even triyng to force it dragging icons, playing video and doing gpu benchmarks... Please, publish here the result of inxi -Faz command in order to see if there is a difference between your and my graphics system: Wayland, inxi graphics section: --- Graphics: Device-1: bcm2711-hdmi0 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef00700 class-ID: hdmi Device-2: bcm2711-hdmi1 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef05700 class-ID: hdmi Device-3: bcm2711-vc5 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:gpu class-ID: gpu Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: modesetting unloaded: fbdev display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23") Monitor-1: XWAYLAND0 res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.6") diag: 551mm (21.7") OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.2.2 direct render: Yes X11, inxi graphics section: --- Graphics: Device-1: bcm2711-hdmi0 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef00700 class-ID: hdmi Device-2: bcm2711-hdmi1 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef05700 class-ID: hdmi Device-3: bcm2711-vc5 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:gpu class-ID: gpu Display: x11 server: X.Org 1.20.13 compositor: gnome-shell driver: loaded: modesetting unloaded: fbdev display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") Monitor-1: HDMI-1 res: 1920x1080 hz: 60 dpi: 102 size: 476x268mm (18.7x10.6") diag: 546mm (21.5") OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.2.2 direct render: Yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
Quick test done: root@fpgrpi:~# uname -a Linux fpgrpi 5.13.0-1008-raspi #9+20211014.git9545d93d SMP PREEMPT Thu Oct 14 09:46:28 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Tested dtoverlay=vc4-kms-v3d on both wayland and X11 with no HDMI freezes at all. I'll have it keep running (on wayland) to make sure, but this fix seems to be really promising. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947058] [NEW] Options missing in arm64 build compared to amd64 build
Public bug reported: There are some options missing in the arm64 built compared to the same amd64 build: the arm64 build misses the rightmost icon that includes the "Extensions", "About" and "Exit" options. Here are both screenshots from amd64 and arm64 builds, same gnome-todo version (3.28.1-6build2) and same Ubuntu version (21.10), where you can see the missing icon: This is the amd64 screenshot (OK): https://images2.imgbox.com/18/9c/E8pwQflW_o.png This is the arm64 screenshot (missing icon): https://images2.imgbox.com/7b/5b/atge11R3_o.png Details: arm64: -- root@fpgrpi:~# lsb_release -rd Description:Ubuntu 21.10 Release:21.10 root@fpgrpi:~# apt-cache policy gnome-todo gnome-todo: Instalados: 3.28.1-6build2 Candidato: 3.28.1-6build2 Tabla de versión: *** 3.28.1-6build2 500 500 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 Packages 100 /var/lib/dpkg/status amd64: -- root@fpglinux:~# lsb_release -rd Description:Ubuntu 21.10 Release:21.10 root@fpglinux:~# apt-cache policy gnome-todo gnome-todo: Instalados: 3.28.1-6build2 Candidato: 3.28.1-6build2 Tabla de versión: *** 3.28.1-6build2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-todo (Ubuntu) Importance: Undecided Status: New ** Description changed: There are some options missing in the arm64 built compared to the same amd64 build: the arm64 build misses the rightmost icon that includes the "Extensions", "About" and "Exit" options. Here are both screenshots from amd64 and arm64 builds, same gnome-todo version (3.28.1-6build2) and same Ubuntu version (21.10), where you can see the missing icon: This is the amd64 screenshot (OK): - https://images2.imgbox.com/9c/a9/3CiIanbc_o.png + https://images2.imgbox.com/18/9c/E8pwQflW_o.png This is the arm64 screenshot (missing icon): https://images2.imgbox.com/7b/5b/atge11R3_o.png Details: arm64: -- root@fpgrpi:~# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@fpgrpi:~# apt-cache policy gnome-todo gnome-todo: - Instalados: 3.28.1-6build2 - Candidato: 3.28.1-6build2 - Tabla de versión: - *** 3.28.1-6build2 500 - 500 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 Packages - 100 /var/lib/dpkg/status + Instalados: 3.28.1-6build2 + Candidato: 3.28.1-6build2 + Tabla de versión: + *** 3.28.1-6build2 500 + 500 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 Packages + 100 /var/lib/dpkg/status amd64: -- root@fpglinux:~# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@fpglinux:~# apt-cache policy gnome-todo gnome-todo: - Instalados: 3.28.1-6build2 - Candidato: 3.28.1-6build2 - Tabla de versión: - *** 3.28.1-6build2 500 - 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages - 100 /var/lib/dpkg/status + Instalados: 3.28.1-6build2 + Candidato: 3.28.1-6build2 + Tabla de versión: + *** 3.28.1-6build2 500 + 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947058 Title: Options missing in arm64 build compared to amd64 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-todo/+bug/1947058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
@fossfreedom Well, in fact the ubuntu-release-upgrader is doing just the the opposite that you want... In hirsute I was using "vc4-fkms-v3d" so I didn't suffer this problem. But during the upgrade to impish my config.txt file was automatically changed from this: dtoverlay=vc4-fkms-v3d To # changed by do-release-upgrade (LP: #1923673) dtoverlay=vc4-kms-v3d This is the related bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923673 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
In my case I use a 1920x1080@60 monitor: - Using wayland session if I just try to move an app in the apps drawer it hangs inmediately. - Using X11 session it takes more time to hang, but it's just a matter of time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
I can confirm this -nasty- bug. It happens in X11 and wayland sessions. The workaround of changing in /boot/firmware/config.txt: dtoverlay=vc4-kms-v3d To: dtoverlay=vc4-fkms-v3d Solves the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754393] Re: Graph is not updated realtime (Ubuntu 17.10)
Ubuntu 21.04: graph autorefresh is still not working in wayland. It only refresh if you manually interact with the graph (e.g. clicking inside the graph). ** Tags added: wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754393 Title: Graph is not updated realtime (Ubuntu 17.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1754393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Proposed fix tested in hirsute on a Raspberry Pi4 arm64 and on an PC
amd64.
Packages installed from hirsute-proposed:
libgjs0g (1.68.1-1~ubuntu0.21.04.1)
gjs (1.68.1-1~ubuntu0.21.04.1)
And, after reboot, do those tests:
1./ Test case:
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" && echo
GJS works
[object Promise]
GJS works
2./ The error shown in every boot is gone.
3./ The indicator-multiload app is working as expected
So the bug seem to be fixed. Thanks and best regards.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)
Proposed fix tested in hirsute on a Raspberry Pi4 arm64, kernel 5.11.0-1009-raspi Packages installed from hirsute-proposed: gnome-shell (3.38.4-1ubuntu3~21.04.1) gnome-shell-common (3.38.4-1ubuntu3~21.04.1) gnome-shell-extension-prefs (3.38.4-1ubuntu3~21.04.1) After reboot I've activated calendar sync with my google account and the reported problem is gone. I also check that the calendar sync worked as expected. So the bug seem to be fixed. Thanks and best regards. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915929 Title: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Finally will the fix be released for Hirsute? Seems that it has been moved form Hirsute (Proposed) to Impish. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Forget about the messages that I show in the previous post: it seems that this problem is also happening in Ubuntu 20.10 groovy and are unrelated to the original bug. I didn't realize these messages before because in groovy these messages are way less informative than in hirsute. In groovy it only show: abr 23 02:45:40 fpglinux gnome-shell[1730]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' abr 23 02:45:40 fpglinux gnome-shell[1730]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' abr 23 02:45:40 fpglinux gnome-shell[1730]: value "-inf" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat' abr 23 02:45:40 fpglinux gnome-shell[1730]: value "-inf" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat' So it's probably happening since ages... Thank you very much for the quick fix and happy releasing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
BTW: as I said the problem is solved with the proposed builds. So, the indicator-multiload app is working as expected. But I just realized that is throwing another messages at its start, messages that it's not throwing in Ubuntu 20.10 groovy. These are the messages: amd64: -- abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: JS ERROR: Exception in callback for signal: shown: Error: Wrong type number; float expected. But it's out of range: -Infinity _init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16 _easeActor@resource:///org/gnome/shell/ui/environment.js:155:15 init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19 _syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21 _init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _showDone@resource:///org/gnome/shell/ui/overview.js:604:14 onComplete@resource:///org/gnome/shell/ui/overview.js:589:36 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64 arm64: -- abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' abr 23 00:18:31 fpgrpi gnome-shell[1494]: JS ERROR: Exception in callback for signal: shown: Error: Wrong type number; float expected. But it's out of range: -Infinity _init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16 _easeActor@resource:///org/gnome/shell/ui/environment.js:155:15 init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19 _syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21 _init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _showDone@resource:///org/gnome/shell/ui/overview.js:604:14 onComplete@resource:///org/gnome/shell/ui/overview.js:589:36 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64 abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' abr 23 00:18:31 fpgrpi gnome-shell[1494]: JS ERROR: Error: Wrong type number; float expected. But it's out of range: -Infinity _init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16 _easeActor@resource:///org/gnome/shell/ui/environment.js:155:15 init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19 _syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21 _updateWorkspacesActualGeometry/this._syncActualGeometryLater<@resource:///org/gnome/shell/ui/workspacesView.js:716:22 But, as I said, I think these messages are not having impact in the execution of indicator-multiload app. At least I didn't notice any problem. Just wanted to comment it, just in case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Just tested amd64 packages with the same results than arm64: problem is solved. Thanks and best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923267 Title: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Hello Brian,
Just tested arm64 build; updated these packages:
- gjs_1.67.2-2ubuntu2_arm64.deb
fprietog@fpgrpi:~$ apt-cache policy gjs
gjs:
Instalados: 1.67.2-2ubuntu2
Candidato: 1.67.2-2ubuntu2
Tabla de versión:
*** 1.67.2-2ubuntu2 100
100 /var/lib/dpkg/status
1.67.2-2ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages
- libgjs0g_1.67.2-2ubuntu2_arm64.deb
fprietog@fpgrpi:~$ apt-cache policy libgjs0g
libgjs0g:
Instalados: 1.67.2-2ubuntu2
Candidato: 1.67.2-2ubuntu2
Tabla de versión:
*** 1.67.2-2ubuntu2 100
100 /var/lib/dpkg/status
1.67.2-2ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages
And, after reboot, the problem reported is solved:
1./ Test case:
fprietog@fpgrpi:~$ gjs -c
"imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype, 'delete_async',
'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" && echo
GJS works
[object Promise]
GJS works
2./ The error shown in every boot as also gone.
3./ The indicator-multiload app now is working as expected
I'll test amd64 build when available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923267] Re: indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1
Unfortunately I still got the same problem with gnome-shell-extension- appindicator 35-1 installed. I don't think that this will be related to gnome-shell-extension- appindicator because I'm also getting this error message every boot and it that seems to be the same problem in a different app and not related to indicators: abr 21 19:25:19 fprietog-VirtualBox gnome-shell[1361]: JS ERROR: TypeError: method Gio.File.delete_async: At least 3 arguments required, but only 2 passed _handleLockScreenWarning@resource:///org/gnome/shell/ui/main.js:323:24 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:303:13 _startupAnimationComplete@resource:///org/gnome/shell/ui/layout.js:733:14 onComplete@resource:///org/gnome/shell/ui/layout.js:711:36 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64 I can assure that with libglib2.0-0, libglib2.0-bin and libglib2.0-data version 2.67.5-2 it works, but with version to 2.68.0-1 it doesn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923267 Title: indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1923267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923667] Re: Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B).
The github issue you pointed shows the same problem I reported. In fact, I've made several searches for this problem and I've found that is a known issue for the kms driver as stated in this official Raspberry Pi forums post regarding "Moving Linux Kernel to 5.10": https://www.raspberrypi.org/forums/viewtopic.php?f=29=288234this post in Raspberry Pi official forum: "Known Issues: With kms driver, sometimes HDMI experiences a 1 pixel shift (rightmost pixels appear on leftmost side of display)." So I think this can be closed here since it should be fixed at driver level. Thanks you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923667 Title: Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1923667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923667] [NEW] Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B).
Public bug reported: - System: Raspberry Pi 4 Model B Rev 1.4 - O.S. Ubuntu 21.04 Desktop Beta arm64 - Kernel: Linux fpgrpi 5.11.0-1005-raspi #5-Ubuntu SMP PREEMPT Fri Apr 9 13:10:37 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux - Package version: linux-raspi 5.11.0.1005.3 - Desktop: GNOME 3.38.4 tk: GTK 3.24.25 wm: gnome-shell dm: GDM3 3.38.2.1 Distro: Ubuntu 21.04 (Hirsute Hippo) - Display: server: X.Org 1.20.10 compositor: gnome-shell driver: loaded: modesetting unloaded: fbdev display ID: :1 - OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.0.1 direct render: Yes Problem summary: Most of times, after boot, the desktop is shifted 1 pixel to the right when attached to an HDMI monitor. It means that the most right vertical line is shown at the left of the screen. It only happens using the full kms drivers vc4-kms-v3d and vc4-kms-v3d- pi4, and not always but most of times. It doesn't happen using the fake kms driver vc4-fkms-v3d. I'm using X.Org, not Wayland. I've checked dmesg and journalctl messages and didn't found any related error. I also tried a fresh install of Ubuntu 21.04 Beta and got the same problem. ** Affects: linux-raspi (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/1923667 Title: Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1923667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status
Same problem here in different architecture: O.S. Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8Gb). Fails during boot: # systemctl status systemd-rfkill.service ● systemd-rfkill.service - Load/Save RF Kill Switch Status Loaded: loaded (/lib/systemd/system/systemd-rfkill.service; static) Active: failed (Result: exit-code) since Sat 2021-04-10 09:19:40 CEST; 8min ago TriggeredBy: ● systemd-rfkill.socket Docs: man:systemd-rfkill.service(8) Process: 786 ExecStart=/lib/systemd/systemd-rfkill (code=exited, status=1/FAILURE) Main PID: 786 (code=exited, status=1/FAILURE) Error: 5 (Error de entrada/salida) abr 10 09:19:40 fpgrpi systemd[1]: Starting Load/Save RF Kill Switch Status... abr 10 09:19:40 fpgrpi systemd-rfkill[786]: Read event structure of invalid size. abr 10 09:19:40 fpgrpi systemd[1]: systemd-rfkill.service: Main process exited, code=exited, status=1/FAILURE abr 10 09:19:40 fpgrpi systemd[1]: systemd-rfkill.service: Failed with result 'exit-code'. abr 10 09:19:40 fpgrpi systemd[1]: Failed to start Load/Save RF Kill Switch Status. But after boot if it's started manually (systemctl start systemd- rfkill.service) it starts without errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921696 Title: Failed to start Load/Save RF Kill Switch Status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923267] [NEW] indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1
Public bug reported: Problem tested in two different environments: - Ubuntu 21.04 Beta amd64 - Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB) After upgrading these packages: libglib2.0-02.67.5-2 to 2.68.0-1 libglib2.0-bin 2.67.5-2 to 2.68.0-1 libglib2.0-data 2.67.5-2 to 2.68.0-1 The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only three dots (...) instead of the graphic expected. It's throwing error messages to the system journal every second or so (depends of the refresh interval selected in the app settings): abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]: multiload, Impossible to read image from path '/run/user/1026/multiload-icons- Wc8kck/icons/indicator-multiload-graphs-0.png': TypeError: method Gio.File.read_async: At least 3 arguments required, but only 2 passed Don't know if this is a documented change of that method and the bug should be open for the indicator-multiload app. Please, if that's the case just let me know to do it. Thanks and best reagrds ** Affects: glib2.0 (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/1923267 Title: indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1923267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900642] Re: sssd won't start
I may add something else. During sssd install there were several warning messages: Configurando sssd-common (2.3.1-3) ... Creating SSSD system user & group... adduser: Aviso: El directorio personal «/var/lib/sss» no pertenece al usuario que está creando. Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing complain mode Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd line 54): Caching disabled for: 'usr.sbin.sssd' due to force complain About the first warning "adduser: Aviso: El directorio personal «/var/lib/sss» no pertenece al usuario que está creando." (translation: adduser: Warning: The personal directory «/var/lib/sss» doesn't belong to the user that is being created). I can tell that it's true; the directory /var/lib/sss is owned by root instead of sssd. All the directories and files inside /var/lib/sss are owned by sssd user except /var/lib/sss/deskprofile directory that is also owned by root. Probably not a problem, but may be also patched. I can't tell about the warning messages related to apparmor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900642 Title: sssd won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1900642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867537] Re: 10-link-restrictions.conf missing - removed by postinst
Problem persist in Ubuntu 20.04 LTS stable release: root@fpglinux:/var/cache# lsb_release -d Description:Ubuntu 20.04 LTS root@fpglinux:/var/cache# apt policy procps procps: Instalados: 2:3.3.16-1ubuntu2 Candidato: 2:3.3.16-1ubuntu2 Tabla de versión: *** 2:3.3.16-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@fpglinux:/var/cache# debsums -ac procps debsums: missing file /etc/sysctl.d/10-link-restrictions.conf (from procps package) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867537 Title: 10-link-restrictions.conf missing - removed by postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1867537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724944] Re: gdm3 doesn't start with disable-user-list=true option enabled
And the 2nd point is also an "user" problem. When we use the dconf-editor GUI we are changing the dconf keys for the user that executes the command, usually your personal user. So changing it from there has no effect because the user that launches the greeter is different; 'gdm'. So the solution is change the dconf key for the user 'gdm'. I don't know how to do it from the dconf-editor GUI so I give the old fashion way: Using root: - Create a file named '/etc/dconf/profile/gdm' with this contents: user-db:user system-db:gdm - Create a file named '/etc/dconf/db/gdm.d/50-disable-user-list' with this content: [org/gnome/login-screen] disable-user-list=true - Execute the command 'sudo dconf update' And that's all. It changes the dconf setting for user 'gdm' and after reboot the greeter works as expected: asking for the user instead of showing the users list. And this solution works in both Ubuntu 17.10 and Ubuntu 18.04 Beta 2!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724944 Title: gdm3 doesn't start with disable-user-list=true option enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724944] Re: gdm3 doesn't start with disable-user-list=true option enabled
BTW: as Joris Le Blansch wrote, using dconf-editor GUI to set /org/gnome /login-screen/disable-user-list to ON has no effect and after reboot userlist is shown as before. So, at this point: 1. Manually changing the file '/etc/gdm3/greeter.dconf-defaults' uncommenting the lines: #[org/gnome/login-screen] and # disable-user-list=true Work in Ubuntu 18.04 Beta 2 but doesn't work in Ubuntu 17.10. 2. Using dconf-editor GUI to set '/org/gnome/login-screen/disable-user- list' to ON just doesn't work... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724944 Title: gdm3 doesn't start with disable-user-list=true option enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724944] Re: gdm3 doesn't start with disable-user-list=true option enabled
I managed to get some journalctl entries related with the gdm starting error: abr 09 20:54:01 testuser-VirtualBox generate-config[699]: warning: Failed to read keyfile '/usr/share/gdm/dconf/90-debian-settings': Key file does not start with a group abr 09 20:54:01 testuser-VirtualBox systemd[1]: gdm.service: Control process exited, code=exited status=1 abr 09 20:54:01 testuser-VirtualBox systemd[1]: gdm.service: Failed with result 'exit-code'. abr 09 20:54:01 testuser-VirtualBox systemd[1]: Failed to start GNOME Display Manager. The file '/usr/share/gdm/dconf/90-debian-settings' is an softlink to the file '/etc/gdm3/greeter.dconf-defaults' and suddenly I realized that this is not a bug: it's my fault from the beginning!!! :( There is another line that must be also uncommented in order to get it to run, the previous 'group one': #[org/gnome/login-screen] and # disable-user-list=true After uncommented both lines the greeter works as expected in Ubuntu 18.04 beta 2: asking for the user instead of showing a list. But in Ubuntu 17.10 it's still showing the users list. So I think it's fixed in Ubuntu 18.04 Beta 2. Sorry for the inconveniences. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724944 Title: gdm3 doesn't start with disable-user-list=true option enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720219] Re: Repeated keys stop after a few characters (^@ character spam every second)
Just want to thank all people involved in the solution of this bug. I just upgraded to Ubuntu 17.10 and I almost get mad with these ^@^@^@^@^@^@^@^@^@^@^@^@ that makes impossible to login in a tty. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720219 Title: Repeated keys stop after a few characters (^@ character spam every second) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724944] [NEW] gdm3 doesn't start with disable-user-list=true option enabled
Public bug reported: Ubuntu 17.10 final gdm3 package version is 3.26.1-3ubuntu2 Problem details: The file /etc/gdm3/greeter.dconf-defaults got this option commented by default: # disable-user-list=true I've used this option with Ubuntu 17.04 (GNOME session) in order to not show any profile in greeter, as a security measure. But with Ubuntu 17.10, if you uncomment that line Ubuntu will not boot (really will not start gdm3, so no greeter is shown). How to reproduce the problem: - Fresh install Ubuntu 17.10 desktop (for instance, in a virtual machine). - Uncomment the line "# disable-user-list=true" in file "/etc/gdm3/greeter.dconf-defaults". - Reboot... ** Affects: gdm3 (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/1724944 Title: gdm3 doesn't start with disable-user-list=true option enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580537] Re: LibreOffice with ambiance theme and breeze icon style is unusable
@Björn Michaelsen; the fixed pic you posted looks very nice. Hope the fix reach the repo soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580537 Title: LibreOffice with ambiance theme and breeze icon style is unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1580537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589210] Re: snap remove failed ubuntu-core snap package
Well, with newest snapd 2.11 version there is a way to remove ubuntu- core snap package. If you try: $sudo snap remove ubuntu-core You get the "snap "ubuntu-core" is not removable" error as expected. But you can disable it with the command: $sudo snap disable ubuntu-core And, once disabled, it can be effectively removed using again: $sudo snap remove ubuntu-core -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589210 Title: snap remove failed ubuntu-core snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1589210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589210] Re: snap remove failed ubuntu-core snap package
That's the description: Name Version Developer Notes Summary base 16.04+20160525.05-00 canonical - Base content for snapd It's contents are very similar to "ubuntu-core" package": base: - -rw-r--r-- 1 root root0 may 25 20:55 base_16.04+20160525.05-00_amd64.snap drwxr-xr-x 2 root root 1739 may 25 06:59 bin/ drwxr-xr-x 5 root root 109 may 25 06:59 boot/ drwxr-xr-x 4 root root 1597 may 25 06:58 dev/ drwxr-xr-x 77 root root 2367 may 25 06:59 etc/ drwxr-xr-x 3 root root 29 may 25 06:59 home/ drwxr-xr-x 18 root root 379 may 25 06:59 lib/ drwxr-xr-x 2 root root 43 may 25 06:57 lib64/ drwxr-xr-x 2 root root3 may 25 06:57 media/ drwxr-xr-x 2 root root 32 may 25 20:55 meta/ drwxr-xr-x 2 root root3 may 25 06:57 mnt/ drwxr-xr-x 2 root root3 may 25 06:57 opt/ drwxr-xr-x 2 root root3 abr 12 22:14 proc/ drwx-- 2 root root 46 may 25 06:59 root/ drwxr-xr-x 8 root root 115 may 25 06:58 run/ drwxr-xr-x 2 root root 2267 may 25 06:59 sbin/ drwxr-xr-x 2 root root3 may 19 23:33 snap/ drwxr-xr-x 2 root root3 may 25 06:57 srv/ drwxr-xr-x 2 root root3 feb 5 10:48 sys/ drwxrwxrwt 2 root root3 may 25 06:59 tmp/ drwxr-xr-x 11 root root 151 may 25 06:58 usr/ drwxr-xr-x 12 root root 160 may 25 06:59 var/ drwxr-xr-x 2 root root3 may 25 06:59 writable/ ubuntu-core: -rw-r--r-- 1 root root0 may 25 20:55 base_16.04+20160525.05-00_amd64.snap drwxr-xr-x 2 root root 1739 may 25 06:59 bin/ drwxr-xr-x 5 root root 109 may 25 06:59 boot/ drwxr-xr-x 4 root root 1597 may 25 06:58 dev/ drwxr-xr-x 77 root root 2367 may 25 06:59 etc/ drwxr-xr-x 3 root root 29 may 25 06:59 home/ drwxr-xr-x 18 root root 379 may 25 06:59 lib/ drwxr-xr-x 2 root root 43 may 25 06:57 lib64/ drwxr-xr-x 2 root root3 may 25 06:57 media/ drwxr-xr-x 2 root root 32 may 25 20:55 meta/ drwxr-xr-x 2 root root3 may 25 06:57 mnt/ drwxr-xr-x 2 root root3 may 25 06:57 opt/ drwxr-xr-x 2 root root3 abr 12 22:14 proc/ drwx-- 2 root root 46 may 25 06:59 root/ drwxr-xr-x 8 root root 115 may 25 06:58 run/ drwxr-xr-x 2 root root 2267 may 25 06:59 sbin/ drwxr-xr-x 2 root root3 may 19 23:33 snap/ drwxr-xr-x 2 root root3 may 25 06:57 srv/ drwxr-xr-x 2 root root3 feb 5 10:48 sys/ drwxrwxrwt 2 root root3 may 25 06:59 tmp/ drwxr-xr-x 11 root root 151 may 25 06:58 usr/ drwxr-xr-x 12 root root 160 may 25 06:59 var/ drwxr-xr-x 2 root root3 may 25 06:59 writable/ Dunno why I've it installed. I tested several packages and then removed them, but this one and ubuntu-core remains unremovables. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589210 Title: snap remove failed ubuntu-core snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1589210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589210] Re: snap remove failed ubuntu-core snap package
Error in previous post, I've duplicated "base" contents listing. This is "ubuntu-core" listing: ubuntu-core: drwxr-xr-x 24 root root 309 may 31 13:56 ./ drwxr-xr-x 4 root root 4096 jul 22 21:27 ../ drwxr-xr-x 2 root root 1739 may 31 13:54 bin/ drwxr-xr-x 5 root root 109 may 31 13:54 boot/ drwxr-xr-x 4 root root 1597 may 31 13:53 dev/ drwxr-xr-x 77 root root 2367 may 31 13:55 etc/ drwxr-xr-x 3 root root 29 may 31 13:54 home/ drwxr-xr-x 18 root root 379 may 31 13:54 lib/ drwxr-xr-x 2 root root 43 may 31 13:51 lib64/ drwxr-xr-x 2 root root3 may 31 13:51 media/ drwxr-xr-x 2 root root 32 may 31 13:56 meta/ drwxr-xr-x 2 root root3 may 31 13:51 mnt/ drwxr-xr-x 2 root root3 may 31 13:51 opt/ drwxr-xr-x 2 root root3 abr 12 22:14 proc/ drwx-- 2 root root 46 may 31 13:54 root/ drwxr-xr-x 8 root root 115 may 31 13:53 run/ drwxr-xr-x 2 root root 2267 may 31 13:54 sbin/ drwxr-xr-x 2 root root3 may 19 23:33 snap/ drwxr-xr-x 2 root root3 may 31 13:51 srv/ drwxr-xr-x 2 root root3 feb 5 10:48 sys/ drwxrwxrwt 2 root root3 may 31 13:55 tmp/ drwxr-xr-x 11 root root 151 may 31 13:53 usr/ drwxr-xr-x 12 root root 160 may 31 13:54 var/ drwxr-xr-x 2 root root3 may 31 13:54 writable/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589210 Title: snap remove failed ubuntu-core snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1589210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589210] Re: snap remove failed ubuntu-core snap package
"Base" snap package has the same problem: # snap remove base error: cannot remove "base": snap "base" is not removable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589210 Title: snap remove failed ubuntu-core snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1589210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563083] Re: Desktop file broken
The desktop file "/usr/share/applications/gprename.desktop" is missing in package "gprename_20140325-1_all.deb" Workaround while waiting for a fix: use the desktop file "/usr/share/applications/gprename.desktop" from previous package "gprename_2.6.6-1_all.deb" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563083 Title: Desktop file broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gprename/+bug/1563083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573758] Re: Desktop file for gprename is missing in package gprename_20140325-1_all.deb
*** This bug is a duplicate of bug 1563083 *** https://bugs.launchpad.net/bugs/1563083 ** This bug has been marked a duplicate of bug 1563083 Desktop file broken -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573758 Title: Desktop file for gprename is missing in package gprename_20140325-1_all.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gprename/+bug/1573758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573758] [NEW] Desktop file for gprename is missing in package gprename_20140325-1_all.deb
Public bug reported: The desktop file /usr/share/applications/gprename.desktop is missing in package gprename_20140325-1_all.deb It causes that gprename isn't shown in dash and cannot be launched from it. Workaround: just use the desktop file /usr/share/applications/gprename.desktop from previous package gprename_2.6.6-1_all.deb ** Affects: gprename (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/1573758 Title: Desktop file for gprename is missing in package gprename_20140325-1_all.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gprename/+bug/1573758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445595] Re: Empty trash from Launcher results in Nautilus window opening
Amr Ibrahim (amribrahim1987) wrote on 2015-08-26: Is this related? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1040158 --- It's related but not the same. The report you pointed seems to be quite old and states that nautilus takes focus only when it's open and the trash is emptied. Now it's worse because even if nautilus is closed (I mean, no nautilus windows are currently opened) and you empty trash, nautilus is opened and focused. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty trash from Launcher results in Nautilus window opening To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445595] Re: Empty Trash Results in File Windows Opening
IMHO this is an important bug; well, it doesn't break any important OS feature but it affects the general image of Unity Ubuntu the users should have because it happens with a usually frequent task execution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty Trash Results in File Windows Opening To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449748] Re: gedit can't run in root terminal
BTW, using Phil Wolff's workaround solved another problem I had trying to open android SDK from root's command line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449748 Title: gedit can't run in root terminal To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1449748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449748] Re: gedit can't run in root terminal
Thanks Phil Wolff, Your workaround works like a charm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449748 Title: gedit can't run in root terminal To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1449748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449748] Re: gedit can't run in root terminal
Is there a workaround for this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449748 Title: gedit can't run in root terminal To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1449748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457697] Re: [Vivid] kernel 3.19.0-17 fails to find HDMI sound output
BTW: there are several similar bug reports... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457369 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457446 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458196 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457697 Title: [Vivid] kernel 3.19.0-17 fails to find HDMI sound output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457697] Re: [Vivid] kernel 3.19.0-17 fails to find HDMI sound output
I have the same problem. I'm using Ubuntu 15.04 64 bits (Desktop Edition). CPU Intel Core i7-4790, GPU Intel HD4600. Using latest BIOS and microcode. There is no HDMI out sound with latest kernel 3.19.0-18-generic. When I boot with previous kernel (3.19.0-16-generic) the HDMI sound works. Here is an screenshot of the sound config under 3.19.0-16-generic. It shows the HDMI device, and it works: http://rt002nf0.eresmas.net/Temp/FPGLINUX%203.19.0-16-generic_01.jpg Here is the same screenshot under the newest kernel 3.19.0-18-generic. No HDMI driver shown: http://rt002nf0.eresmas.net/Temp/FPGLINUX%203.19.0-18-generic_01.jpg If I can help in any way, please, don't hesitate to ask. Thanks and best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457697 Title: [Vivid] kernel 3.19.0-17 fails to find HDMI sound output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
