Public bug reported:
when dlmopen glib2.0 and the program is linked with pthread, glib2.0 crashed in
g_variant_lookup_value when dlmopen with
LM_ID_NEWLM
following is the poc:
#define _GNU_SOURCE
#include
#include
#include
#include
int main(int argc, char*argv[])
{
char buf[4096] = {0}
** Tags added: originate-from-2063092
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1977986
Title:
UPower and battery indicator show update in 2 minutes when connecting
I checked the source code, it should be from console-setup which is
installed by ubiquity, it will load the Keyboard/ckb/rules/base.xml,
currently it will select the first one after choosing country or
timezone. Maybe we could set 'thinkpad' if we could detect the type of
laptop.
Public bug reported:
We found this issue on several ThinkPad. The upower will change
'pending-charge' to 'charging' after 2 minutes later, but the
/sys/class/power_supply/BAT0/status changes to 'Charging' immediately
when connecting the power cable.
$ upower -i /org/freedesktop/UPower/devices/bat
** Tags added: oem-priority originate-from-1975803 sutton
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1977986
Title:
UPower and battery indicator show update in 2 minute
Public bug reported:
[Impact]
On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly.
With the new rules, the modem devices could be recognized correctly. And also
could avoid wrong command for other protocols, like set 'AT' to wwan0mbim.
[Where problems could occur]
It's
And I knew there is a plan to upgrade MM to 1.18.6[1], and it's proposed
channel, but it has been hold more than one month because of some risks.
Is it possible that we merge this fix[2] into 1.16.6 first.
[1] https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1965901
[2]
https://gitlab
** Patch added: "udev-Match-WWAN-type-attribute-instead-of-device-nam.patch"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+attachment/5595791/+files/udev-Match-WWAN-type-attribute-instead-of-device-nam.patch
** Description changed:
[Impact]
On 20.04.4, with modemman
@seb128,
Thanks for your feedback, I prefer to update to 1.18 than this fix, and
as I know Stephane.Verdy has pushed 1.18 for long time to support more
modem devices, so let's wait for the 1.18.
IF the 1.18 was dropped in proposed, we could reconsider this fix.
Thanks!
--
You received this bu
With Danilo comment #4, it works fine if we could remove the comment.
u@oak2-10:~$ nmcli connection add type dummy ifname d0
Connection 'dummy-d0' (2364f50d-72d5-4849-804d-f6d28467bf93) successfully added.
u@oak2-10:~$ sudo cat /lib/netplan/00-network-manager-all.yaml·
# Let NetworkManager manage
8fd08
--- /dev/null
+++ b/data/ubuntu/00-network-manager-all.yaml
@@ -0,0 +1,4 @@
+# Let NetworkManager manage all devices on this system
+network:
+ version: 2
+ renderer: NetworkManager
** Changed in: oem-priority
Assignee: (unassigned) => Bin Li (binli)
** Changed in: oem-priority
@mdmower,
Yes, the patch for pipewire is not enough, the deep copy need another 2
packages, gstreamer1.0 and gst-plugins-base1.0. I built the deb packages
in my ppa. The screencast works fine with below packages.
https://launchpad.net/~binli/+archive/ubuntu/gnome/
gstreamer1.0 - 1.20.3-0ubuntu
This patch could help set the initial status correctly.
commit 792fc7bb1bd4c7bf4b779106329aa4487bfa0386
Author: Benjamin Berg
Date: Thu Jun 2 18:29:50 2022 +0200
supply: Consistently use 90% threshold to consider a battery full
** Patch added:
"0001-supply-Consistently-use-90-threshold-
** Patch added: "gstreamer1.0_1.20.3-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638524/+files/gstreamer1.0_1.20.3-0ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
** Patch added: "gst-plugins-base1.0_1.20.1-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638525/+files/gst-plugins-base1.0_1.20.1-2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
@mdmower,
What's the version of pipewire in your side?
This issue is caused by new patches in 0.3.48-1ubuntu2 which is fixed
lp:1985057 .
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
- Camera
** Patch added: "pipewire_0.3.48-1ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638528/+files/pipewire_0.3.48-1ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Description changed:
- When recording a screencast with gnome on kinetic the resulting video
- will play for one second and then freeze. It looks like the same bug was
- discussed upstream at https://gitlab.gnome.org/GNOME/gnome-
- shell/-/issues/5585
+ [Impact]
+ When recording a screencast wi
@seb128,
Could you help review and sponsor the 3 debdiff when you are available?
Thanks!
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/comments/27
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/comments/28
https://bugs.launchpad.net/ubuntu/+source/gnome-s
@mdmower,
Thanks, in your comment this issue could be fixed with gstreamer's
patch, so the root cause is from gstreamer.
I prefer to add the pipewire's patch, cause it's also from James
Hilliard, it might help avoid the potential issue without deepcopy.
Could you help upgrade the new pipewire f
@seb128,
The situation is a bit unclear there, the pipewire SRU got superseeded by a
revert right, does that resolve the issue?
-> Yes, the revert one the pipewrie(0.3.48-1ubuntu3) could resolve this issue.
Or is the request still trying to address the initially problem?
-> Yes, our OEM project
Public bug reported:
'Kernel Livepatch' should be displayed an enabled from below bug. But
the check button is in 'Disabled' status with gray color.
https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/2003527
** Affects: software-properties (Ubuntu)
Importance: Undecided
** Attachment added: "ubuntupro.png"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2007564/+attachment/5647768/+files/ubuntupro.png
** Tags added: originate-from-2007068
** Tags added: sutton
--
You received this bug notification because you are a member of Ubuntu
Touch
** Package changed: compiz-plugins-main (Ubuntu) => modemmanager
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1997532
Title:
Traffic leaks from the cellula
@seb128,
I went through this issue again.
On 22.04.2, it works fine. With pipewire 0.3.48-1ubuntu3, because it
revert the patches for Bug #1985057 , so currently we don't need to do
SRU for this issue.
To make this issue clear, let's focus on the SRU process on Bug
#1985057.
--
You received th
ress => Fix Released
** Changed in: oem-priority
Assignee: Bin Li (binli) => (unassigned)
** No longer affects: gst-plugins-base1.0 (Ubuntu)
** No longer affects: gst-plugins-base1.0 (Ubuntu Jammy)
** No longer affects: gstreamer1.0 (Ubuntu Jammy)
** No longer affects: gstreamer1.0 (Ubuntu
The below two patches in Description could cause the screencast
regression, so they were reverted, if we want add them again we need two
gstreamer's patches in comment #51.
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
d/p/0002-gst-dequeue-a-shared-buffer-instead-of-ori
After enabled the proposed, updated the mesa packages, it works
perfectly on ThinkPad MTL platforms. Thanks!
Before:
$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits)
OpenGL version string: 4.5 (Compatibility Profile) Mesa 2
** Tags added: originate-from-2046930
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604
Title:
Backport packages for 22.04.4 HWE stack
Status in directx-headers package
Public bug reported:
On ubuntu 20.04, with latest kernel and systemd, it will show error on
ThinkPad X1.
sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy
systemd 245.4-4ubuntu3.6
kernel: 5.8.0-53
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
https://github.com/systemd/systemd/issues/14981
** Tags added: oem-priority originate-from-1927884 sutton
** Bug watch added: github.com/systemd/systemd/issues #14981
https://github.com/systemd/systemd/issues/14981
--
You received this bug notification because you are a member of Ubuntu
Touc
Tried to back-port 4 patches from #2, it didn't work for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1928200
Title:
Prompt error message "Failed to unmount /oldroot
No such file or directory
The login package stopped packaging this file:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
and now forcibly removes the file:
https://paste.ubuntu.com/p/myh9cGWrHD/
However, the pam package's pam_unix.so module has not yet been adapted to
ignor
Hi seb128,
Currently we met issue for Fibocom L860-GL-16(8086:7560) could cause the
ACPI reporting huge interrupts when modemmanager(1.16.6-2~20.04.1) was
started. After upgrade to 1.18.6 from https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/transitions/ , this issue is gone, although this
t
Public bug reported:
On ThinkPad, when I select 'Portuguese(Brazil)', it will use
'Portuguese(Brazil)' on second column, but the default value should be
'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'.
** Affects: console-setup (Ubuntu)
Importance: Undecided
Status: New
This is a general issue on 20.04 and 22.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1970190
Title:
Wrong default vaule for Brazil Keyboard layout on ThinkPad
Here is the screenshot.
** Attachment added: "877976752.jpg"
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1970190/+attachment/5583454/+files/877976752.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to co
Fibocom L860-GL-16(8086:7560) could cause the ACPI reporting huge
interrupts when modemmanager(1.16.6-2~20.04.1) was started at ThinkPad
X1 Carbon and X13 Yoga. After upgrade to 1.18.6 from proposed channel,
this issue is gone, although this type modem was not supported yet.
** Tags removed: verif
** Summary changed:
- Wrong default vaule for Brazil Keyboard layout on ThinkPad
+ [Feature]Wrong default vaule for Brazil Keyboard layout on ThinkPad
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
h
** Summary changed:
- [Feature]Wrong default vaule for Brazil Keyboard layout on ThinkPad
+ [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in
adm --wait-clean
--scan".
$ cat ./debian/mdadm.finalrd
#!/bin/sh
# SPDX-License-Identifier: GPL-3.0-only
set -e
if [ "$1" = "setup" ]
then
. /usr/share/initramfs-tools/hook-functions
copy_exec /sbin/mdadm
copy_exec /sbin/mdmon
exit 0
fi
mdmon --all --tak
act]
root fs is not cleanly unmounted on shutdown
[test case]
create a file in /etc/binfmt.d/TestFormat.conf with the following
content:
:TestFormat:M::XX::/bin/true:F
reboot the system, and then shutdown or reboot again, and watch the
serial console for the error message:
: High
Assignee: Bin Li (binli)
Status: Confirmed
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-priority originate-from-1950402 sutton
** Tags added: oem-priority originate-from-1950402 sutton
--
You received this bug notification because
in: oem-priority
Assignee: (unassigned) => Bin Li (binli)
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bug
** Tags added: originate-from-1989447
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1977986
Title:
UPower and battery indicator show update in 2 minutes when connecting
** Tags added: originate-from-1991377
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1977986
Title:
UPower and battery indicator show update in 2 minutes when connecting
Public bug reported:
[Summary]
For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.
[Steps to reproduce]
1. Install the 22.04
2. Boot and login
3. Open a folder
4. Drag-n-drop the folder with finger touch
5. Drag-n-drop the folder with the Wacom Pen
[Expected result]
Both fi
Switch to wayland, this issue is gone.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1994027
Title:
Can't move window by drag and drop by using touch screen
Status in OEM P
The touch screen works fine on 20.04 image.
** Description changed:
[Summary]
For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.
[Steps to reproduce]
1. Install the 22.04
2. Boot and login
3. Open a folder
4. Drag-n-drop the folder with finger touch
5. Dr
It looks like related to mutter and gtk3.
https://gitlab.gnome.org/GNOME/mutter/-/issues/2057
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2057
https://gitlab.gnome.org/GNOME/mutter/-/issues/2057
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
** Description changed:
[Summary]
For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.
[Steps to reproduce]
1. Install the 22.04
2. Boot and login
3. Open a folder
- 4. Drag-n-drop the folder with finger touch
- 5. Drag-n-drop the folder with the Wacom Pen
+ 4.
** No longer affects: gtk+3.0 (Ubuntu)
** Changed in: oem-priority
Status: New => In Progress
** Changed in: oem-priority
Assignee: (unassigned) => Bin Li (binli)
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1255
https://gitlab.freedesktop.org/xorg/x
** Description changed:
- [Summary]
- For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.
+ [Impact]
+ Users using touch screen could not move windows with 'Drag-n-drop'.
+ This SRU fixes the issue.
- [Steps to reproduce]
+ [Test Plan]
1. Install the 22.04
2. Boot and
Here is the patch from upstream.
** Patch added: "dix-Don-t-send-touch-end-to-clients-that-do-async-grab.patch"
https://bugs.launchpad.net/xserver/+bug/1994027/+attachment/5631766/+files/dix-Don-t-send-touch-end-to-clients-that-do-async-grab.patch
--
You received this bug notification becaus
** Patch added: "xorg-server_21.1.3-2ubuntu2.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1994027/+attachment/5631780/+files/xorg-server_21.1.3-2ubuntu2.3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Built a new packages for testing in my ppa. This issue is fixed with
xserver-xorg-core 2:21.1.3-2ubuntu2.2binli1.
https://launchpad.net/~binli/+archive/ubuntu/gnome/
** Changed in: oem-priority
Status: In Progress => Triaged
--
You received this bug notification because you are a member
Our OEM project would like this to be included in -proposed before this
weekend(2022-11-25).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1994027
Title:
Can't move window b
** Changed in: oem-priority
Assignee: (unassigned) => Bin Li (binli)
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Checked the proposed channel, the 3.8 was not ready yet, will check it
later.
** Changed in: oem-priority
Assignee: (unassigned) => Bin Li (binli)
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Status: New => Confirmed
--
You rece
[test case]
create a file in /etc/binfmt.d/TestFormat.conf with the following
content:
:TestFormat:M::XX::/bin/true:F
reboot the system, and then shutdown or reboot again, and watch the
serial console for the error message:
sd-umount[1334]: Failed to unmount /oldroot: Device or res
** Tags added: originate-from-1935587
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1937988
Title:
The image is distorted while use iGPU rendering and output via AMD GPU
St
After upgraded to latest mesa, this issue is fixed. Now it works fine on
5.10.0-oem or 5.13.0-oem kernel. Thanks!
$ DRI_PRIME=1 glxgears -info
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
GL_RENDERER = Mesa Intel(R) Gr
Installed 21.04 on P348 and reproduced this issue, after upgraded to proposed
packages, this issue is fixed.
$ DRI_PRIME=1 glxgears -info
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
GL_RENDERER = Mesa Intel(R) Graphic
]
create a file in /etc/binfmt.d/TestFormat.conf with the following
content:
:TestFormat:M::XX::/bin/true:F
reboot the system, and then shutdown or reboot again, and watch the
serial console for the error message:
sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy
20)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType
- Release amd64 (20180522)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.l
Public bug reported:
We found the login console, like tty1, can't show up when we did below
command in 18.04.1.
$ sudo systemctl isolate multi-user.target
or
$ sudo init 3
After above command, it will show a cursor with black screen.
I could switch to tty1 with 'Ctrl+Alt+F1', and login into sy
https://ubuntuforums.org/showthread.php?t=2330707
Here is the similar issue on 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1811204
Title:
login console don't sh
Hi Daniel,
Thanks for your review. I'm OoO and can't get it now. Will provide to
you later. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780076
Title:
18.04 logi
running time directory from /run/gdm
to /run/gdm3.
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="/bin/sh -c '/bin/mkdir
/run/gdm3 ; /usr/bin/printf \"[daemon]\nWaylandEnable=false\&q
Daniel,
Thanks a lot! I will ask someone to help it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780076
Title:
18.04 login screen is skewed/distorted (incorrect stride)
Here is the log from Huawei arm server. Thanks!
** Attachment added: "lspci-k.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5161325/+files/lspci-k.log
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because y
Daniel,
Thanks for your help, I've report a new one.
https://gitlab.gnome.org/GNOME/mutter/issues/219
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780076
Title:
18.04 l
Talked with Jonas Ådahl, he suggest we try below patch, I will try it
when back office.
https://gitlab.gnome.org/GNOME/mutter/merge_requests/155
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.lau
@Daniel,
Now this issue in my side is not related to
https://gitlab.gnome.org/GNOME/mutter/merge_requests/160, I've updated
the latest mutter(3.28.3-2~ubuntu18.04.1), this issue is still exist,
and I tried to make it with small patch, but I'm failed.
So could we used the patch in comment #7?
@Daniel,
Got it, and the issue 412 was fixed. I will work on the patch today.
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780076
Title:
18.04 login screen
For 18.10, I made a patch for it.
* Disable wayland for Huawei Hi1710. (LP: #1780076)
+ Add ubuntu_disable_wayland_huawei_chipsets.patch
+ gdm3.install: Fix udev path from /usr/lib/udev to lib/udev.
And I my code is based on cosmic-devel.
https://code.launchpad.net/~binli/ubuntu/+source
@ubuntu-sponsors,
Could you helped reviewed the 0001-Disable-wayland-for-Huawei-
Hi1710-LP-1780076.patch for 18.10? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780
I made two patches for upstream. Now the !35 was accepted, just wait for
!38.
https://gitlab.gnome.org/GNOME/gdm/merge_requests/35
https://gitlab.gnome.org/GNOME/gdm/merge_requests/38
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Now the !38 was accepted too.
https://gitlab.gnome.org/GNOME/gdm/merge_requests/38
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780076
Title:
18.04 login screen is skewed
@seb128,
Fine, let met try, could you tell me which one is used for packaging
branch. Thanks!
remotes/origin/ubuntu/cosmic
remotes/origin/ubuntu/cosmic-devel
remotes/origin/ubuntu/cosmic-proposed
remotes/origin/applied/ubuntu/cosmic
remotes/origin/applied/ubuntu/cosmic-devel
remotes/origin/appl
Here is the patch for
https://gitlab.gnome.org/GNOME/gdm/merge_requests/38
** Patch added: "0003-data-61-gdm.rules.in.patch"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5182209/+files/0003-data-61-gdm.rules.in.patch
** Patch removed: "disable-wayland-bydefault.pat
Here is the patch for upstream, we need merge it into 3.29.91.
https://gitlab.gnome.org/GNOME/gdm/merge_requests/35
** Patch added: "0002-data-Makefile.am.patch"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5182208/+files/0002-data-Makefile.am.patch
--
You receiv
@seb128,
Could you help check if this debdiff is ok? Thanks!
** Attachment added: "gdm3_3.29.91-1ubuntu2_3.29.91-1ubuntu3.diff.gz"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5182212/+files/gdm3_3.29.91-1ubuntu2_3.29.91-1ubuntu3.diff.gz
--
You received this bug
I made a merge request on packaging tree, is it ok? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780076
Title:
18.04 login screen is skewed/distorted (incorrect st
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Bin Li (binli)
** Changed in: gdm3 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
The !35 has some side effect for other distribution, after discuss, I
made a new patch !44, it was accepted by upstream.
https://gitlab.gnome.org/GNOME/gdm/merge_requests/35
https://gitlab.gnome.org/GNOME/gdm/merge_requests/44
--
You received this bug notification because you are a member of Ub
:04 2018 +0200
install udev rules in the correct folder
* debian/gdm3.install:
- install udev rules in the correct folder (following upstream build
fixes)
commit e7c108779b23f10da71953fefa2ba5eacc76fac1
Author: Bin Li
Date: Wed Aug 29 16:47:46 2018 +0800
data: 61
Potential]
+
+ * It's just a kind of workaround, we add one the udev rule to skip
+ Huawei's chipset, which won't affects other platform.
+
+ [Other Info]
+
+ * Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219
** Changed in: gdm3 (Ubuntu)
Assignee: Bin Li (
@Ara,
Could we let the modemmanager fixes in trusty in #65? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for De
@arges, @$4,
Fine, I will help it for vivid. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded modems
S
@arges, @$4,
I have finished the backport for vivid.
@Brian,
Great news, thanks a lot! Currently I don't have the device on hand. We
need $4 help to verify it. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-ma
$4,
I took annual leave yesterday, so now it looks the upstream one works
fine for the master version, I don't know why there are no default
gateway, you add one with ifconfig, after that check if it could browse
the website. :)
--
You received this bug notification because you are a member o
4$,
Yes, I thought we need push the network-manager patch separately. I
will open another bug to trace it.
And I found there are patch in 0.9.9.1, we need cherry pick into
0.9.8.8.
commit 19089fb9609c5a62a3cfe5ff81e3d3d93beabeb3
Author: Dan Williams
Date: Tue Feb 18 13:51:03 2014 -0600
I just found the networkmanager project was affected in this bug, so we
don't need to open another one, :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Tit
Now Shih-Yuan helped to debug more about it, I thought he will debug
more for EM7305 and EM7455.
** Changed in: modemmanager (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: modemmanager (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve prob
Mathieu,
Shih-Yuan already helped to verify in trusty it works fine for EM7305
and EM7455,, and all the patches are almost same with trusty, just some
data structure is changed for wily, I just find another Sierra device,
although it's not use this Dell plugin, I will tested the wily package
for
I installed the new package in wily, looks this device can't work, it
can't recognize the SIM card. We had two devices, same type from Lenovo,
just one of them works for trusty which I tested them last year, but I
can't find another device now. :)
So now ModemManager could finish the device detect
@Shih-Yuan,
I have updated the status to 'Confirmed".:)
** Changed in: modemmanager (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.l
1 - 100 of 160 matches
Mail list logo
