@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
** 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
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
>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.
osuid,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
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
> 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
==
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
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 wir
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).
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
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
** 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
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
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:
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
* 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,
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
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
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
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.
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
@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
@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:
@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
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
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
@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
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,
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
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.
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
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
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
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
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 'gfl
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
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
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/sh
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":
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
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)
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
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
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
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
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:
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]:
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
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
@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
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
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
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
"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
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
*** 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.
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
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
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
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
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:
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:
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
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
65 matches
Mail list logo
