> However, I don't see how we can argue that dropping FAN support is
> *not* a regression, even if the kernel we ship does not support it.
I understand.
I guess the situation is a bit particular here. If the official kernel
doesn't support it -- something Ubuntu-specific, not upstreamed -- it
> I don't think we can justify dropping FAN support in an SRU, so let's
add that port back in.
Even if it will not be used in Ubuntu 24.04, and dropping these patches
would stop the diversion with Debian?
> @matttbe - is there any documentation about upstream compatibility guarantees
> and
Hi Dann,
Thank you for doing that!
Is there something I can do to help?
Note that I published the modifications I did [1] in a dedicated PPA
[2]. This was a merge with Debian.
If it is no longer needed to support Ubuntu FAN -- see my comment in #3
-- all Ubuntu-specific patches can be removed,
Hello,
I was quickly checking if I could help preparing the upgrade of IPRoute2
packages for Noble (before the final freeze).
In short, IPRoute2 has Ubuntu specific modifications. The merge was not
difficult, the code is there:
** Summary changed:
- Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable
(main)
+ Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable
(main)
** Description changed:
A few versions have been released and Ubuntu Noble still has the 6.1
I hope that's OK if I put the 24.04's feature freeze as milestone.
** Changed in: iproute2 (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
** Description changed:
A few versions have been released and Ubuntu Noble still has the 6.1
version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
import the latest version from Debian unstable fixing a bunch of issues
and supporting features from more recent kernels?
Public bug reported:
A few versions have been released and Ubuntu Noble still has the 6.1
version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
import the latest version from Debian unstable fixing a bunch of issues
and supporting features from more recent kernels?
Please note that
Hi Sebastien,
Thank you for the link. Good to know this list is closely monitored by
the Desktop team.
(Also "funny" that for "network-manager" package, the last stable
upstream version is not reported: an issue with the "watch" file?)
I guess for Git, I will need to continue pinging someone on
Hi Sebastien,
Sorry I didn't know your team was already tracking that.
I opened this issue because I was trying to find the root cause of
random disconnections when using Ubuntu Jammy: is it NM/iwd/kernel?
I'm using 'iwd' and I noticed it was outdated: 1.15 while the latest
version is 1.21 and
Public bug reported:
There are some differences between versions from Debian and Ubuntu. A
new version has been released a week ago.
Debian Changelog:
network-manager (1.34.0-2) unstable; urgency=medium
* Demote wpasupplicant to Recommends.
There are enough use cases for network-manager
Hello!
Regarding the comment #8, I didn't get the same positive experience on
my side. It was more closer to what is described in comment #9. See bug
1889479 for more details.
I would suggest switching back to powersave/ondemand either with a new
service or the kernel config. Having a dedicated
*** This bug is a duplicate of bug 1885730 ***
https://bugs.launchpad.net/bugs/1885730
Hi Dan,
Oh yes indeed, sorry I looked for issues in systemd and I missed it!
I'm fine with the "duplicate" status.
Cheers,
Matt
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
Hello,
TL;DR the default cpufreq governor is now "performance" instead of
"powersave" since ondemand service is no longer shipped with systemd.
+ First, thank you for maintaining systemd in Ubuntu!
- First, thank you for maintaining systemd in Ubuntu?
+ I am
Public bug reported:
Hello,
TL;DR the default cpufreq governor is now "performance" instead of
"powersave" since ondemand service is no longer shipped with systemd.
First, thank you for maintaining systemd in Ubuntu?
I am using Ubuntu Devel on my daily laptop. For a few weeks now, I
noticed
Hi Gunnar,
It would make the file not being loaded in case of a syntax error, and
an entry printed to ~/.xsession-errors.
I don't know if it's better to ignore this file in case of syntax errors
or to refuse to start a new session but for me, the most interesting
thing is to notify the user
Hello,
I also confirm that this bug can still be annoying with the latest versions of
GDM and LightDM :-)
And it can be an easy way to make some jokes just by modifying the .profile!
Then it will be hard for the user to understand why he can no longer start a
new session.
Is it maybe possible
cairo-dock-plug-ins: needs rebuilding
** Changed in: cairo-dock-plug-ins (Ubuntu)
Status: Fix Released = Fix Committed
** Changed in: cairo-dock-plug-ins (Ubuntu)
Assignee: (unassigned) = Matthieu Baerts (matttbe)
--
You received this bug notification because you are a member
I'm not so sure that this crash is due to the dock.
@fabounet and Mesa devs: any idea?
#3 0x7fcb610bd5e6 in malloc_printerr (ptr=optimized out,
str=0x7fcb611bfd48 free(): invalid next size (fast), action=1) at
malloc.c:4996
buf = 02a15c60
cp = optimized out
#4
Added DockbarX and Plank projects to this bug report with 'Invalid'
status: It seems this bug affects DockbarX and Plank users.
** Branch unlinked: lp:ubuntu/cairo-dock
** Description changed:
- Using latest stable release (3.3.1). Just upgraded to Saucy Salamander
- in Ubuntu. When cairo dock
** Summary changed:
- Shutdown/restart dialogue is not working if Cairo-Dock and its logout applet
are running
+ Shutdown/restart dialogue is not working if Cairo-Dock and its
Launcher-API-Deamon are running or if another app is registered to
LauncherEntry interface of Unity DBus
--
You
21 matches
Mail list logo
